• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1026 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.

RTOS/AM3357: EtherCAT Slave issue

Jian Zhou
Intellectual 1930 points
Part Number: AM3357
Other Parts Discussed in Thread: AM3359, TLK110

Tool/software: TI-RTOS

Hi EtherCAT slave expert:

My customer use AM3357 for EtherCAT slave product, now they find that AM3357 should have EtherCAT initialization failure issue in terms of device power up sequence, both in line topology and circle topology, please see the below description by picture.

Could you please test it by AM3359 ICE board?

  • 0
    TI__Guru**** 393215 points
    The RTOS team have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    TI__Mastermind 43296 points
    Jian,

    We can set up the topology and run the test on AM3359 ICE v2 board. In the meantime, can you elaborate the ' EtherCAT initialization failure issue'? Is the TwinCAT not able to detect all the slave boards? And does it fail intermittently or always? And when it fails, which status is the EtherCAT slave in?

    Regards,
    Garrett
  • 0 in reply to Garrett Ding
    TI__Intellectual 1930 points

    Garrett,

    Thanks for your support!

    TwinCAT can detect all the slave boards in the failure case, in the power up sequence which lead to failure, the error will occur every time.

    The failure status has 2 situation, one is CRC error on port B, another is no data communication on port B. 

  • 0 in reply to Jian Zhou
    TI__Mastermind 43296 points
    Hi Jian,

    Do you check the CRC error from EtherCAT Rx error counter register 0x300-0x307 and data communication from DL status register 0x110-0x111? Given the CRC error, it's more likely a hardware issue on the custom AM3357 boards. The test result on AM3359 ICE board may not be meaningful but I have requested testing team to provide for confirmation. Some additional info may help:

    1. Software version
    2. PHY part number
    3. Wireshark logs / Bus traces if possible
    4. UART logs

    Regards,
    Garrett
  • 0 in reply to Garrett Ding
    TI__Intellectual 1930 points

    Garrett,

    Please see my answer:

    1. Software version: old Industry IDK, EtherCAT  stack 5.10 
    2. PHY part number: TLK110
    3. Wireshark logs / Bus traces if possible:see attachmenthttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/Err.7z
    4. UART logs: no log

    Bellow picture is register:

  • 0 in reply to Jian Zhou
    TI__Mastermind 43296 points
    Jian,

    As you may know, the old industrial SDK is no longer supported, see the notice here - e2e.ti.com/.../580869

    The PRU-ICSS industrial testing team is just moving lab, so not able to test the setup yet on AM3359 ICEv2. Again, due to the hardware/software difference, I am not sure how the testing result will help.

    It would be more productive if the customer can move to the latest PRU-ICSS EtherCAT 1.0.5 release.

    Regards,
    Garrett