• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 138 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.

Original question:

AM6442: AM64 PROFITNET

AM6442: Profitnet ip configuration question

Will Tsai
Prodigy 370 points

Part Number: AM6442

Hi

 

In our am64 profitnet example can we do same ip and same mac address under a core and r core? when tunneling example

 

Below is customer use-case

  1. Control & Application Layer
    CPSW EtherCAT Master: Integration of an EtherCAT Master stack utilizing the CPSW (Common Platform Ethernet Switch) hardware peripheral for high-speed industrial automation control.
    Linux-based Web Server: A dedicated web server hosted on the Linux (A53/A72) cores to provide a graphical user interface (GUI) for remote monitoring, configuration, and data visualization.
  2. Real-Time Communication Layer
    R5F Core-based PROFINET Stack: The PROFINET protocol stack is offloaded to the ARM Cortex-R5F cores to ensure deterministic, real-time response times independent of the main OS load.
    ICSSG Ingress/Egress Management: Deployment of the ICSSG (Industrial Communication Subsystem - Gigabit) firmware to handle the high-speed processing of standard Ethernet frame ingress and egress.
  3. Networking & Protocol Handling
    Dual-Protocol Concurrent Processing: The system architecture supports simultaneous handling of both PROFINET cyclic data and Standard Ethernet (TCP/IP) packets without cross-interference.
    Unified MAC Address: Implementation of a Single MAC Address shared across the interface, simplifying network node identification and ensuring seamless integration into existing IT/OT environments.
  4. Dual-Port Port Configuration (PROFINET)
    The device utilizes a dual-port physical interface with functional separation:
    Primary Port (Real-Time): Dedicated strictly to PROFINET cyclic traffic for mission-critical industrial control.
    Secondary Port (Diagnostics/Access): Configured for Information Access, allowing for diagnostic data retrieval, monitoring, and standard network communication.

so they are wondering if two different mac and ip why they need lwip bridge

  • 0
    TI__Prodigy 560 points

    Hi Will,

    As per customer use-case there is a lot to unpack here. But I will keep my answer specific to your last question about mac and ip address. 

    The Lwip Bridge is a component inside the LwIP module that allows for rerouting packets based on MAC address. 
    So it’s important to understand that the lwip bridge is not a direct substitute for IPC.

    Tunneling is a feature enabled by lwip bridge to allow Linux to communicate over the same port that the protocol stack on R5 is communicating on. It emulates two devices with distinct MAC and IP addresses being connected over the same ethernet channel accessible through the ICSSG Ethernet Port. So long story short, it is a 2 MAC, 2 IP address solution. 

    Now if your customer has a hard requirement for a "single MAC, single IP" solution - this is not readily available in our SDK. 
    But as per my understanding, there are two ways this could be implemented.

    1. The tunnel does help us send and receive data from A53 <-> R5 as if they are connected together via a standard Ethernet channel.
      Your customer can use this to create a socket forwarding application. i.e, essentially send all packets to Profinet stack (R5) and have a dedicated TCP/UDP socket in the R5 application that will handle all data needed at Linux (A53) by forwarding it to another socket which will send the packets to Linux via the ICVE. This way, the eth1 ICVE interface on the Linux can be reused. 
    2. Another way would be to create a custom IPC (for example, using a ring buffer) to facilitate packet transfer between R5 and A53 at the application layer. 

    From our previous discussions, I understand your customers want to use the eth1 (ICVE) interface on Linux for the IP packets. So option1 (socket forwarding) might be more suited for you. Unfortunately, we do not have an example for this in the industrial comms SDK. Any support for this would be considered custom and would require premium contract.

    Regards,
    Bharath

  • 0 in reply to Bharath Kartha A
    TI__Prodigy 370 points

    Hi Bharath,

    Can customer use ti emac usecase on pru, use the same application modified to forward the Ethernet stack?

    The function itself do look like same.

    Will that be work?

    Thx

    Will

  • 0 in reply to Will Tsai
    TI__Prodigy 560 points

    Hi Will, 

    Can you please provide a bit more information ? What do you mean by "ti emac usecase on pru" ?

    Regards,
    Bharath