• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 341 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.

AWR6443: Front end calibration errors

Tarek KASMIEH
Prodigy 185 points
Part Number: AWR6443

Hello TI,

I would like to know after how many times of the RSS calibration error occurrence we should consider the part as defective?

We need to use this information to log a DTC (Data Trouble Code)

Regards

  • 0
    TI__Genius 10550 points

    Hi, 

    We will check and get back to you. 

    Regards, 

    Sudarshan K N

  • 0 in reply to Sudharshan KN
    TI__Genius 10550 points

    Hi, 

    Is the calibration performed periodically and monitored for failure or is it at the time of production? 

    In general the DTC can be generated for the following cases. 

    1. Any mmWaveLink API failure (return error code from RadarSS/BSS)
    2. Immediate report failure types based on async-event from BSS
      1. CPU, ESM, Analog Fault (AWR_AE_RF_CPUFAULT_SB, AWR_AE_RF_ESMFAULT_SB, AWR_ANALOGFAULT_AE_SB)
      2. Boot time calibration failure (based on AWR_AE_RF_INITCALIBSTATUS_SB)
    3. RF Digital Latent Fault (AWR_MONITOR_RF_DIG_LATENTFAULT_REPORT_AE_SB) : [This needs to be done just after bootup]
    4. AWR_CAL_MON_TIMING_FAIL_REPORT_AE_SB
    5. One time or periodic runtime calibration failure: AWR_RUN_TIME_CALIB_SYMMARY_REPORT_AE_SB
    1. For monitor failure (based on specific monitor type async-event report message), it can be checked for multiple of back to back failure ( based on Monitor async-event report at FTTI interval) before setting it to DTC

    Regards, 

    Sudharshan K N