• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 233 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.

AM6442: Porting EtherNet/IP Adapter Demo to Custom Board with AM64x (Features ”E”)

Hiroki Hoshina
Prodigy 50 points
Part Number: AM6442


Tool/software:

I would like to ask for guidance as we attempt to port the EtherNet/IP Adapter Demo to our custom board, which uses an AM64x processor with Features marked as “E”.

This is part of our effort to prepare for integrating a third-party EtherNet/IP stack, and we would like to begin by verifying the demo on our hardware.

Here is the setup we are working with:

  • SDK: AM64x Industrial Communications SDK v11.00.00
  • Sample: EtherNet/IP Adapter Demo
  • Target Board Processor: A processor that, according to section 9.1.2 of the Device Naming Convention for JAJSL34G, has Features marked as ”E”
    • (i.e., supports features of D, plus EtherCAT HW Accelerator and CAN-FD are enabled)
  • Stack: We plan to use a third-party EtherNet/IP stack on the target board instead of the one provided in the SDK

We have confirmed that the EtherNet/IP Adapter Demo runs successfully on the AM64x-EVM.
As a first step toward integrating the third-party stack, we would like to port and run the EtherNet/IP Adapter Demo on our custom board to verify basic functionality and ensure the environment is correctly set up.

Could you please help us clarify the following points:

  1. Is it possible to port the EtherNet/IP Adapter Demo to our custom board (with Features "E") by modifying the configuration accordingly?
  2. If porting to a processor with Features "E" is not supported, would using a processor with Features "F"—same as the one on the AM64x-EVM—make it feasible?
  3. Are the PRU-ICSS firmware files used in the EtherNet/IP Adapter FWHAL and those used in the EtherNet/IP Adapter Demo the same, or are they different?
  4. Besides the following documentation, are there any other resources or references that would be helpful when integrating a third-party EtherNet/IP stack using the demo as a base?

Any advice or pointers would be greatly appreciated.

Thank you.

  • +1
    TI__Expert 3300 points

    Hi

    The answers to your questions are attached below.

    Hiroki Hoshina said:
    Is it possible to port the EtherNet/IP Adapter Demo to our custom board (with Features "E") by modifying the configuration accordingly?

    The EthernetIP Stack from TI only supports Part E of the AM64x. However, if you're planning to use a third-party stack, you can run EthernetIP demo on your custom board (with Part E). 

    Hiroki Hoshina said:
    • If porting to a processor with Features "E" is not supported, would using a processor with Features "F"—same as the one on the AM64x-EVM—make it feasible?

    Summarizing the previous answer - if you're planning to use the TI Stack, you have to use the Part F. If you're planning to use a third-party stack, you can use the Part E.

    Hiroki Hoshina said:
    Are the PRU-ICSS firmware files used in the EtherNet/IP Adapter FWHAL and those used in the EtherNet/IP Adapter Demo the same, or are they different?

    The PRU-ICSS firmware header files used in the EthernetIP Adapter FWHAL are the same ones being used in the the out-of-box EthernetIP Adapter Demo from the Industrial Comms SDK (integrated with TI EIP Stack). 

    You can use the EthernetIP Adapter FWHAL with your third-party stack as well, if you're planning to use PRU-ICSS as the Ethernet Switch.

    Hiroki Hoshina said:
    Besides the following documentation, are there any other resources or references that would be helpful when integrating a third-party EtherNet/IP stack using the demo as a base?

    I'd highly recommend going through the Profinet and Ethernet_IP Initialization Guide.pdf . This goes through the ICSS EMAC (Ethernet Driver) and the EthernetIP Driver Initialization - sections 1 and 3 would be relevant for you.

    Please note - if you're planning to use Precision Time Protocol (PTP), the Tx and Rx PHY latencies have to be programmed accordingly during the TimeSync initialization. Make relevant changes in the following lines of code in the Section "3.5 TimeSync Handle Initialization" of the shared document.

    timeSyncHandle->timeSyncConfig.rxPhyLatency = 220;
timeSyncHandle->timeSyncConfig.txPhyLatency = 64;

    Regards
    Archit

  • 0 in reply to Archit Dev
    Prodigy 50 points

    Hi

    Thank you for your helpful response.

    I just wanted to double-check one point to be sure.

    In your message,

    The EthernetIP Stack from TI only supports Part E of the AM64x.

    However, according to section 9.1.2 of the Device Naming Convention for JAJSL34G, Part ”F” is described as:
    "Features supported by E, plus Pre-integrated Stacks are enabled."

    Based on this, I understand that the EtherNet/IP stack from TI is only supported on Part F, not Part E.
    Could you please confirm if this understanding is correct, just to be sure?

    Also, I really appreciate your clarification regarding the PRU-ICSS firmware.

    It was very helpful to know that the PRU-ICSS firmware used in the EtherNet/IP Adapter FWHAL(for Third-party stack) is the same as the one used in the ”EtherNet/IP Adapter Demo”.

    That was one of the points I wanted to confirm as well.

    Best regards,

    Hiroki 

  • 0 in reply to Hiroki Hoshina
    TI__Expert 3300 points

    Hi,

    This was a typing mistake from my side.
    Correction: The EthernetIP Stack from TI only supports Part F of the AM64x.

    Apologies for the confusion.

    Regards
    Archit 

  • 0 in reply to Archit Dev
    Prodigy 50 points

    Hi,

    Thank you very much for the clarification.

    No worries at all — I really appreciate your support.

    Best regards,
    Hiroki