• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 571 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/AWR1843: query about 1843

HAVI HOUSTON
Intellectual 605 points
Part Number: AWR1843

Tool/software: Code Composer Studio

hi

i got little question about using of 1843 as below:

1) how can i change the parameter in profileCfg when the 1843 is runing, or how can  i dynamic configurate the parameter of profile

2)what is the formost short time to sensor stop and sensor start the 1843;

br

havi

  • 0
    TI__Guru 69960 points

    Hi Havi,

    1. You can invoke profileConfig API with new config parameters (but set pfCalLutUpdate=0x3: to avoid updating LUT). There are few precautions you need to take while updating the profiles.

    - When you are invoking profileConfig API, make sure that at that time instance any chirps of the current running frame is not using that profileID.

    - If at next frame you need this new profile config to be used then it must be called before the current frame is over and around 500usec before frame-end boundary.

    2. Another option is to do the sensor-stop, profileConfig update and then sensor-start.

      -   If the application invokes sensor-stop API then RadarSS returns with ACK at the same time but physical sensor-stop happens at the current frame-end boundary only. In other word, if RadarSS gets the sensor-stop command in the middle of any running frame then a max time of actual stop can be one full frame-duration.

      -  Due to this reason only, you must need to wait for sensor-stop async event message from RadarSS and then only invoke sensor-start to re-trigger the frame.

    Regards,

    Jitendra