• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 29 subscribers
  • Views 116 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.

AM2432: ■SORTE_G, IN packet is not sent from device

hiroyasu-shimizu
Intellectual 490 points
Part Number: AM2432

■SORTE_G, デバイスからINパケットが送信されない
　INパケット送信中（IOEX_TTS_COMPLETE_CHECK_TXFIFOLEVEL）に「IOEX_TTS_RECONFIGURE_MIIRT」へジャンプ
　しています。

　※何回かループしてから「IOEX_TTS_RECONFIGURE_MIIRT」へジャンプしてます。
　※「IOEX_TTS_RECONFIGURE_MIIRT」へジャンプした時のレジスタは以下通り

　「IOEX_TTS_RECONFIGURE_MIIRT」へジャンプする原因を教えてください。
　注記：
　　サンプルプログラムのオリジナルでも発生します（発生率：100%）。

[English]
Jumping to "IOEX_TTS_RECONFIGURE_MIIRT" while transmitting an IN packet (IOEX_TTS_COMPLETE_CHECK_TXFIFOLEVEL).

*After looping several times, it jumps to "IOEX_TTS_RECONFIGURE_MIIRT".
*The registers when jumping to “IOEX_TTS_RECONFIGURE_MIIRT” are as follows.

Please tell me the reason for jumping to "IOEX_TTS_RECONFIGURE_MIIRT".
Note:
This issue also occurs in the original sample program (occurrence rate: 100%).

  • 0
    TI__Expert 5230 points

    Hi Shimizu-san,

    How do you reproduce this failing scenario? You should not set any breakpoint in the real-time flow as this will corrupt the packet transmission.

    One method to confirm is to add a debug counter. Whenever the TXFIFO overflow occurs on the location you pointed out, it will increment the counter. I created some example code attached to this e2e forum post, that you can use to validate.

    I just checked it out in our setup, but I don't see the behavior that you describe. I.e. the debug counter does not increment.

    Please try out the example code attached to this e2e and observer on ICSS shared memory offset 0x10048 if this increments.

    Regards,

     Thomas

    5430.ioex_g.asm