• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 338 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.

LP-AM243: The green data LEDs on both ethercat sockets go off and communication is no longer possible on ethercat after System_init(); function

coderAkdr
Prodigy 210 points

Part Number: LP-AM243
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

I am developing a two core project. While the ethercat slave application is running on core 0-0, the motor control application is running on core 1-0. I start the debug process for core 0-0 and pass. There is no problem with ethercat communication here. However, when I start debugging the core 1-0 project, as soon as I pass the System_init(); function, the green data LEDs on both ethercat sockets go off and communication is no longer possible on ethercat. 

What effect might the system init process I performed here have on my ethercat sockets?  When I call System_init(); by adding an empty task on another core, I don't have any problems. The source of the problem must be in core 0-0.

I am using motor control sdk 9.2.0.9. And Mcu plus SDK is "MCU+ SDK 09.02.00"

Regards

Kadir

  • 0
    Prodigy 210 points

    The reason for the problem of the green LEDs on the sockets turning off is related to another issue. I observe that the ethercat function does not work properly as soon as I start the motor application that is in core 1-0. I have a SDFM definition in sysconfig. On the core 0-0 (ethercat app) the system is initialized using the ESL_OS_init() method. Is there any harm in creating the SDFM in sysconfig? Could it be related to the PRU configuration?

  • 0 in reply to coderAkdr
    TI__Mastermind 29244 points

    Hi

    What is the PRU-ICSSG0 and PRU-ICSSG1 frequency being used in your application? It should be being configured in SysConfig.

    Regards

    Dhaval