• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 263 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: AM64 PROFITNET

Will Tsai
Prodigy 370 points

Part Number: AM6442

Hi Bharath,



Below, we would like to clarify of the detail.

1.For ARP,IP routing those two function will works on which core?

2.As we know in the profitnet tunneling demo, we will have two MAC address and two IP in one pair.

1 phsical Mac and 1 ip on the R5 core and 1 vertural  Mac and 1 ip on the A core.

Can we make those 2 ip as the same and use different  Mac to decide if the normal ethernet stack send to a and if the profitnet stack stay in R core? this structure will similar to switch
Hi Bharath,



Below, we would like to clarify of the detail.

1.For ARP,IP routing those two function will works on which core?

2.As we know in the profitnet tunneling demo, we will have two MAC address and two IP in one pair.

1 Phsical Mac and 1 ip on the R5 core and 1 vertural  Mac and 1 ip on the A core.

Can we make those 2 ip as the same and use different  Mac to decide if the normal ethernet stack send to a and if the profitnet stack stay in R core? This structure will similar to switch
  • 0
    TI__Prodigy 560 points

    Hi Will,

    Will Tsai said:
    Can we make those 2 ip as the same and use different  Mac to decide if the normal ethernet stack send to a and if the profitnet stack stay in R core? This structure will similar to switch

    ARP is handled independently by R5 core (by LwIP in Profinet stack) and A53 core (by the Linux kernel). 
    Not sure what you mean by IP routing here. If you are talking about routing the ethernet packets to R5 or to A53 core, then that is done by the LwIP stack in R5 core itself.
    And this routing is done based on MAC address not based on IP address.

    Will Tsai said:
    Can we make those 2 ip as the same and use different  Mac to decide if the normal ethernet stack send to a and if the profitnet stack stay in R core? This structure will similar to switch

    If you keep the same IP for A53 ICVE and Profinet Stack , then you could encounter issues with ARP requests and other multicast/broadcast frames.
    For example: If both cores have the same IP, you would get ARP response from both A53 and R5 identifying themself at different MAC addresses. This would cause issues with both Standard IP traffic as well as Profinet relevant packets. 

    Regards,
    Bharath

  • 0 in reply to Bharath Kartha A
    TI__Prodigy 370 points

    Thanks for your information.

    So, how do customer use proneta to connect to R5 and send it to linux?  

    Could you give me specific reply.

    THX

    Will

  • 0 in reply to Will Tsai
    TI__Prodigy 370 points

    Follow up the above question, How to ping linux ip and r5 ip?

  • 0 in reply to Will Tsai
    TI__Prodigy 560 points

    Hi Will, 

    Will Tsai said:
    how do customer use proneta to connect to R5 and send it to linux?

    Proneta connects to the Profinet device stack running on R5 core. It cannot connect to Linux which is on the A53 core.

    Both A53 core and R5 core share the same RJ45 ethernet port.
    In order to connect to Linux over this port, a normal TCP or UDP based connection can be made. It is up to the customers to define these connections in the Linux application. 

    Will Tsai said:
    How to ping linux ip and r5 ip?

    After connecting the ICSS port to a Test PC (or any external device) simply sending a ping command "ping <Linux_IP>" from the Test PC should start the Ping. 

    To ping to the R5 core you must first apply the necessary LwIP patch mentioned here.
    The Profinet R5 IP should now be pingable. 

    Regards,
    Bharath