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

AM2432: Porting guide and references for porting TCP/IP and Ethernet/IP

Moonil Heo
Intellectual 680 points

Part Number: AM2432

Hi Expert,

We are considering porting another 3rd party Ethernet/IP solution using Cesium Net(TCP/IP stack) on AM2432. Our product will be connected to a network with a daisy chain. So, it will have one IP and 2 physical ethernet ports. 2 ports will work as packet switching ports for another device on the network.

Q1) I can see three choices in SDK for driver ends as follow. Which one do we have to choose for porting 3rd party solution?

  1. ICSS_EMAC
  2. Enet(CPSW)
  3. Enet(ICSS)

Q2) In my understanding, Ethernet/IP is working on standard TCP/IP. So I think only TCP/IP stack is ported on top of one of them(ICSS-EMAC/Enet) but not sure. Please share your experience and knowledge on this.

Q3) For a new TCP/IP stack porting, could you please share a porting guide and any references?

Regards

Moonil

  • 0
    TI__Guru 57015 points

    Hi Moonil,

    I have forwarded your request to our software team. I will get back to you as soon as I hear anything from them.

    Best regards,

    Ming

  • +1 in reply to Ming Wei
    TI__Guru 57015 points

    Hi Moonil,

    Here are the answers from our software team:

    Q1. All 3 options are viable but if there is multi protocol support requirements for the product 1.ICSS_EMAC and 3. Enet(ICSS) is preferred
    Q2. If you require features like PTP, DLR and ACD support, it is not that straightforward and ICSS_EMAC based option might be better. Unfortunately TI integrated stack does not allow customizing OS and network stack. They might need to work with a 3P like TMG or Port or Kunbus
    Q3. This is a stack customization request and better to work with 3P directly. For network stack porting, they can refer to source\networking\enet\core\lwipif

    Best regards

    Ming

  • 0 in reply to Ming Wei
    Intellectual 680 points

    Hi Ming

    Thank you for your answer.

    I have two more questions as below,

    Q1) According to SDK doc above, (1)path seems possible, but your team said it is only possible in the May release. Please confirm again whether or not the application can commonly use the Lwip used by Kunbus Ethernet/IP in the current SDK.

    Ming Wei said:
    If you require features like PTP, DLR and ACD support, it is not that straightforward and ICSS_EMAC based option might be better.

    Q2) According to SDK doc, PRU Firmware supports PTP, DLR as you mentioned. So I think Enet(ICSS) is (2) but not (3) in the picture above. Is it correct? Can I ask you to provide Lwip examples for (3)?

    Regards

    Moonil

  • +1 in reply to Moonil Heo
    TI__Mastermind 27743 points

    Hi Moonil,

    We updated the stack diagram to explicitly call out what TI offers and what customers can add.

    As discussed in the call, LwIP stack integration is already available and you can use it in SDK8.2.

    Regards,

    Prasad