Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 897 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/IWR6843: freqSlopeConst setting issue ( profilecfg)

Agate
Expert 1275 points
Part Number: IWR6843

Tool/software: Code Composer Studio

Dear TI 

               we have observe freqSlopeConst setting > 40 ~ 50  when we reset IC and resend configuration will unstable to success , setting >  50 ~ 71 when we reset and reboot and resend cfg it always fail . 

               and we double check at  40 > it always normal operation when we reset or reboot then send configuration . It's IC bug or firmware part of RF need to update ? 

BR

  • 0
    TI__Guru 50240 points

    Hi Agate,

    Will you please post the full chirp configuration for both the working and non-working cases?

    Regards,

    AG

  • 0 in reply to Akash Gondalia
    Expert 1275 points

    Dear TI 

    Below is default cfg for HVAC lab of 6843 , we  tuning parameter 8 (freqSlopeConst) of  profileCfg as below table , 

    you can try by yourself . When we only tuning P8 > 40  the IC have some function NG , you can try it . 

    I don't know it is setting issue or IC bug. 

    dfeDataOutputMode 1

    channelCfg 15 5 0

    adcCfg 2 1

    adcbufCfg 0 1 1 1

    profileCfg 0 60 30 10 69.72 0 0 28.42 1 128 2180 0 0 24

    chirpCfg 0 0 0 0 0 0 0 1

    chirpCfg 1 1 0 0 0 0 0 4

    frameCfg 0 1 128 0 50 1 0

    lowPower 0 0

    guiMonitor 1 1 1 1

    cfarCfg 6 4 4 4 4 8 12 4 8 50 63 0

    doaCfg 600 666 30 1 1 1 300 4 2

    AllocationParam 300 800 0.1 30 0.5 20

    GatingParam 3 1.5 1.5 0

    StateParam 3 3 10 40 5 600

    SceneryParam -5 5 0.25 10

    FilterParam 2.0 0.5 1.5

    trackingCfg 1 2 300 15 67 105 50 90

    classifierCfg 1 1 3 500 0.8 1.0 0.95 10

    sensorStart

  • Former Member
    0 Former Member in reply to Agate

    Hello,

    When the cfg fails you can check the reason why it fails by decoding the error that is given (using CCS debug mode).

    You cannot just change the slope and assume that it is a valid config. You need to make sure that the config is valid by checking that BW, timing, and memory limitations aren't exceeded.

    For example 70 is not valid because this results in a BW of 4.8 GHz which exceed's the device's capabilities of 4GHz bandwidth.

    You should also make sure that you are resetting the device between each config as this demo doesn't support sending new config without resetting. This would likely explain the unstable behaviors.

    Amanda

  • 0 in reply to Former Member
    Expert 1275 points

    Dear Amanda 

                              Your answer is very good . We just for TI reference only . Bandwidth checking is easy but timing, and memory limitations is very hard  to check at application level. 

                              If have more tools for application level or application tuning tool the mmwave IC will design very fast. 

                              mmwave is now sensor if have tool can shorten the research period . 

    BR