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.

TMDSCNCD28388D: CM Core Echoback Fails after Power Cycle (FLASH Boot)

Part Number: TMDSCNCD28388D
Other Parts Discussed in Thread: C2000WARE

I'm testing EtherCAT on the TI F28388D evaluation module (EVM) using the provided examples:

  1. c2000/C2000Ware_5_05_00_00/libraries/communications/Ethercat/f2838x/examples/f2838x_cm_echoback_solution

  2. c2000/C2000Ware_5_05_00_00/libraries/communications/Ethercat/f2838x/examples/f2838x_cpu1_echoback_solution

Both projects are programmed to FLASH.

Observation:

  • After programming and running via the debugger, both examples communicate successfully with TwinCAT.

  • However, after a power cycle (without reprogramming):

    • The CPU1 echoback example () continues to work correctly - TwinCAT can connect.f2838x_cpu1_echoback_solution

    • The CM core echoback example () fails:f2838x_cm_echoback_solution

      • TwinCAT cannot scan/find the device.

      • LEDs D1 and D2 are blinking.

Question:
Why does the CM core application fail to start EtherCAT communication after a power cycle when booting from FLASH, while the CPU1 application works? Could this issue be related to the boot sequence, specifically whether the CPU1 core application needs to be executed before the CM core application for a successful FLASH boot?