Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 115 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TMS320F28377D: TMSF28377D：the AL status code is '0x001b' - sync manager watchdog

?? Wu
Prodigy 10 points
Part Number: TMS320F28377D

Tool/software:

Hi Support

Master stack: twincat3

Slave stack:F28377D and LAN9252

Initially, I used the F28335 to implement EtherCAT communication. Then, I ported the F28335 code to the F28377D, only modifying the SPI, IRQ, SYNC0, and SYNC1 code, along with some template changes. Finally, I used the F28377D for EtherCAT communication. However, during communication, EtherCAT always reports an error 0x1b: Sync Manager Watchdog. I checked CPUTIMER0 with an oscilloscope, and the time interval is 1ms, as set. The IRQ interrupt also triggers correctly, and I captured some IRQ waveforms. The first image shows the EtherCAT error, and the second image shows the IRQ waveform.

  • 0
    TI__Mastermind 41365 points

    Hi,

    I suppose Sync manager timeout is occurring and causing OP --> Safe_OP state change. I reviewed some of Beckhoff / ETGs documents and found this error code but not a very helpful description for this error.

    You are using Active / Run mode in TwinCAT currently? As a debug step, can you try with Free Run mode and see that communications work properly?

    Best,

    Kevin

  • +1 in reply to Kevin Allen18
    Prodigy 10 points

    Hi,

    This error occurs in Free Run mode and TwinCAT cannot enter Run mode. I have tried extending the watchdog timer and increasing the master station's clock cycle, but the error still occurs. During a brief OP (Operational) process, I attempted to send and receive data using TwinCAT, and CCS can read the data sent by TwinCAT. The code I had previously was able to run on the F28335, but it does not work on the F28377, and I suspect that some low-level configurations may not have been properly set up, but I cannot pinpoint which ones.

    Thanks