• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 252 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.

AWR1642: AWR1642ABIGABLRQ1

JANGWON HONG
Prodigy 10 points
Part Number: AWR1642

Hello 

I have 2 questions about failures with watchdog.

- During the analysis of awr1642 NG sample with the vehicle, error flags occured

* at 5th byte, 0x90 is normal boot, 0xA1 is 'watchdog reset'

  1. 'BSS fault' occured after digital watchdog

    5th byte, 0xA1 means 'watchdog reset' is activated and 2nd byte, 0x10 means' BSS fault' occured.

  Usually when 'BSS fault' error flag occured, 'watchdog reset' function is used for reset of 'BSS fault' error flag.

But above captured fig. means 'watchdog reset' function was activated but 'BSS fault' remained uninitialized.

  1) which type of 'BSS fault' do not reset by 'watchdog reset' function ?

  2) which cause ?

  3) how to handle this situation ? 

2. 'Initialize fault' occured after digital watchdog

 

 1) which type of 'initialize fault' with DSS fault do not reset by 'watchdog reset' function?

  2) which cause ? 

  3) how to handle this situation ?  

  • 0
    TI__Guru 69960 points

    Hi,

    Please help me to understand the whole scenario here.

    This is AWR1642 device which you have mounted on the vehicle and during the execution over the CAN you see this issue (based on byte interpretation).

    1. What is RadarSS patch version?

    2. What is actual circumstance (temperature, environment around the sensor and vehicle) under which this BSS CPU Fault occurred?

    3. How frequent does this happen? Is it reproducible? How long does it take to reproduce?

    4. Is this happened on any specific Sample or on different device sample?

    5. Please provide BSS CPU fault payload detail so we can analyze and find out the cause of this from RadarSS end.

    For the second snapshot:

    1. I don't see RadarSS CPU fault here (2nd byte is zeo) but WDT reset byte is set to 0xA1.

    2. I am not able to conclude the error here. Is that WDT reset is due to RadarSS? 

    Looks like in your application, some of the flow is causing this reset, please check.

    .

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 10 points

    Hi,

    I reply below questions.

    Please check

    1. What is RadarSS patch version?

     -> DFP package version 1.2.5.1

    2. What is actual circumstance (temperature, environment around the sensor and vehicle) under which this BSS CPU Fault occurred?

     -> Fault did not occur by the specific conditions. As NG IC mounted to the vehicle, fault<->normal situation continuously repeated.

    3. How frequent does this happen? Is it reproducible? How long does it take to reproduce?

     -> Reproducibility is very high. The fault did not recover even after sleep mode at least 30min.

    4. Is this happened on any specific Sample or on different device sample?

     -> 1 specific sample

    5. Please provide BSS CPU fault payload detail so we can analyze and find out the cause of this from RadarSS end.

     -> I did not get a BSS CPU fault guide from TI.

        Please give a guide for checking the BSS CPU fault to me.

       ex) Which of CPU fault payload is needed for analyzing?

  • 0 in reply to JANGWON HONG
    TI__Guru 69960 points

    Hi,

    for 5th point: 

    In the application asyncEventHandler is registered with mmWaveLink which gets the BSS Fault async-event message from Radar(BSS).

    This function receives the Async-event payload data as an argument

    (rlUInt16_t deviceMap, rlUInt16_t cmdCode, rlUInt16_t ackCode, rlInt32_t status, rlUInt8_t *data)

    under             case RL_RF_AE_CPUFAULT_SB:   you can store this data in buffer and share with us.

    Regards,

    Jitendra