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.

  • TI Thinks Resolved

CCS/PRU-ICSS-INDUSTRIAL-SW: EtherCAT PRU Firmware does not run on user specific hardware

Intellectual 380 points

Replies: 5

Views: 204

Part Number: PRU-ICSS-INDUSTRIAL-SW

Tool/software: Code Composer Studio

Hello,

I'm working on an user specific hardware similar to the ICEv2 design. The goal is to run EtherCAT on it. So I started porting the slave example project from PRU ICSS EtherCAT Release 01.00.07.02 to our custom board. The original demo is running on this board but I cannot use both ports. It seems to be that only the ECAT host Interface binary is working. In debug mode I see on PRU Counter incrementing while the other one is frozen after five or six counting steps. On the ICEv2 board the EtherCAT slave demo runs without this limitation.

Other protocol applications like PROFINET and EtherNet/IP are working fine on both ports. So there shouldn't be any problem relating to our hardware design.

Does anybody know how to solve this Problem? Thank you.

Regards, Marc

Release 01.00.07

  • Marc,

    Do you run the EtherCAT on your board from CCS or after it's flashed?

    Have you tried to communicate with EtherCAT master through the ports?

    Can you post the snapshot of PRU frame handler program memory when the PRU counter is frozen?

    Regards,
    Garrett
  • In reply to Garrett Ding:

    Garrett,

    thank you for your reply.

    I run EtherCAT from CCS with a Segger J-Link and I also tried to run the application with a Lauterbach debugger. There is no difference.

    Of course I connected my board to a master. We have different systems.

    Where can I find this memory view?

    Regards, Marc 

  • In reply to Marc W.:

    Marc,

    You can try to halt ARM/PRU core, and then connect to PRU core and step into, you should be able to see which instructions the PRU program executes and check if it's really frozen. It's unlikely the PRU firmware crashes.

    Regards,
    Garrett
  • In reply to Garrett Ding:

    Hi Garrett,

    thanks for your help so far. We finally found the problem - it was due to a wrong PHY config.
    This question can be closed.

    reagrds
  • In reply to Marc W.:

    Marc,

    Thanks for the update, good to know the issue is resolved.

    Regards,
    Garrett

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.