• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 306 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.

IWR6843: Radar heatmap crash issue.

Jesse Wang
Intellectual 1795 points
Part Number: IWR6843
Other Parts Discussed in Thread: AWR1642,

Hi TI expert,

 My customer had some problem about the heatmap crash issue, and would like to consult the debugging opinions.

 When the RADAR system operates for a while, randomly, the heatmap suddenly turns to all red color (all high peak values) and loss the normal detect ability randomly. When this symptom happens, it will need to reset the chip for recovery. BTW, The normal heatmap figure is with blue color in background.

 We think this issue should happened before "FFT block" , something wrong in "Mixer" or "ADC" part . Please see the video as attach in Google Drive below:

https://drive.google.com/file/d/1ZEB0WEy4ntwcvNNbh_RUxCVNgBzooy9r/view 


Is this kind of chip crash?

Which part should I debug for?

Chirp parameters?

EDMA?


PS: The lab code is based on "ti\mmwave_automotive_toolbox_2_9_1\labs\lab0002_short_range_radar".

 

  • 0
    TI__Mastermind 23570 points

    Hello

     Can you please help us understand if you are using the right device and lab combination.

    The mentioned automotive lab is for AWR1642 device however your question is for IWR6843.

    Thank you,
    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    TI__Intellectual 1795 points

    Hi Vaibhav,

     The project was developed 2 years ago, so we took the automotive toolbox code for migration into IWR6843. Currently, the hardware is IWR6843.

     We are still debugging what could be possible reason to make such crash, and suspect if the EDMA data moving by 2 sub frames in one time will be not enough when there are more data, thus we try to modify it to move 3 sub frames in one time for EDMA.

     We found the "srr_config_consts.h" has definition of EDMA PING/PONG table (see below picture).

        

    We tried to modify it to be 3 sub frame, and found the "sys_common_xwr68xx.h" has definition of EDMA_TPCC1_REQ_FREE parameter, but it is up to only "EDMA_TPCC1_REQ_FREE_23". (see below picture)

     Is this correct?

     Do you have comment on right debugging direction?

  • +1 in reply to Jesse Wang
    TI__Mastermind 23570 points

    Hello

    Debugging such customization are outside of the forum support.

    It unclear from the explanation which of the following is the area of debug:

    A.

    Jesse Wang said:
    heatmap suddenly turns to all red color (all high peak values) and loss the normal detect ability

     Does  RF data shows undesired result ---> Debug RAW data

    B.  Code is crashing --->

    Jesse Wang said:
    what could be possible reason to make such crash, and suspect if the EDMA data moving by 2 sub frames in one time will be not enough when there are more data, thus we try to modify it to move 3 sub frames in one time for EDMA.

    Does the post processing show Run time failures  --> Debug the post processing chain

    We recommend the following:

    1. Debug Raw Data:

    Check the RF end is giving good data for the exact configuration by checking same Chirp configuration's RAW data.

    --> See RAW data capture via DAC10000  or  use OOB demo with same chirp to confirm consistent good point cloud

    2. Post processing debug:

    2.1 What delta is introduced in the code?

    2.2 Is the chirp change accommodated in the post processing side. Cube size, #chirps, sample size, data structure modification

    2.3 Implement and flush the desired processing changed on  RAW data  - offline processing and then port them to the C code on the device.

    2.4 Please compare expected vs observed result at the end of each post processing step.

    Hope this get you started in the right direction of debug.

    Alternately you may use one of the many XWR6843 based demo examples that may already be doing what you are trying to implement.

    Please take a look at the industrial toolbox  :

    Thank you,
    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    TI__Intellectual 1795 points

    Hi Vaibhav,

     Thanks for the advice.