• State
  • Replies 4 replies
  • Subscribers 32 subscribers
  • Views 88 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AWRL6432: When ADC is saturated(due to strong reflection), can it cause system fault?

Victor Park
Intellectual 2790 points
Part Number: AWRL6432


Hello team,

Customer has been testing several modules at a time with close distance. They don't know exact reason but sometimes AWRL6432 system gets in stuck. They guess maybe too strong signal reflection might cause this system fail. Could you please comment on this?

.

Also, when system gets in stuck during test, what would be good approach for further debug? Your comments would be appreciated.

 

Regards,

Victor Park

  • 0
    TI__Intellectual 2820 points

    Hi Victor, 

    Thank you for reaching out. Could you provide more details about the following:

    1. Are they using our EVM and are they running their own demo?
    2. When the system fails, what is the fail signature? Are they able to connect to the XDS and check what the last call stack was?
    3. How consistently are they able to re-create this issue? And is it definitely caused by an object being too close?

    The best approach for further debug is to connect to the device and check the call stack. What the last task being executed can tell us a lot about why it may be failing. In the past, I do not think we have seen L6432 fail due to ADC saturation but I will double check.

    Best,
    Vignesh K.

  • 0 in reply to Vignesh Kondapally
    TI__Intellectual 2790 points

    Hello Vignesh,

    Thanks for quick reply!

    1. They are using their own board

    2. To follow your guidance, does customer need to attach XDS for all the boards at the same time? As they are testing many boards at a time, it is not easy to connect XDS for all the boards. If it is the only approach, customer will follow this.

    3. Actually customer thinks that signal from other board's TX could cause RX ADC signal saturation, not the reflected signal from object.

    .

    Regards,

    Victor Park

  • 0 in reply to Victor Park
    TI__Intellectual 2820 points

    Hi Victor,

    I understand the issue better now. This is more hardware related than software so I am going to loop in a HW expert. Since they are using their own board, debugging may be more difficult but we can provide some guidance. The debugger we recommend and support is the XDS110. Are they cascading the device?

    Best,

    Vignesh K.

  • 0 in reply to Vignesh Kondapally
    TI__Intellectual 2790 points

    Hello Vignesh,

    Thanks for reply! Let me check which debugger they use. Their board is not cascaded. They just placed 8~10 modules with close distance and run test with few hours. Once a day, one random module stops and gets in stuck. Not sure if it is hardware based system fault or software based system fault.

    .

    Regards,

    Victor Park