Part Number: AM4376
we are using the EtherNet/IP adapter v126.96.36.199 on out AM4376 device. When the device is operating in a DLR netword with an active ring supervisor, the active supervisor address (MAC and IP address) is provided by at the following register offests within the ICSS shared data RAM:
DLR_ACTIVE_SUP_MAC_0123 = 0x154
DLR_ACTIVE_SUP_IP_OFFSET = 0x164
The MAC address of the active ring supervisor is always provides at offset DLR_ACTIVE_SUP_MAC_0123, but the IP address of the ring supervisor only sometimes contains the right value. In all other cases, the IP address is 0.
What could be the reason why the IP address of the active ring supervisor is provided with 0?
Let me check internally to see if this is a known issue. I don't have a setup to replicate the issue at this special moment.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Garrett Ding:
The MAC address and IP address are updated at different places in the receive flow. This is not a known issue and we will have to reproduce at our side. Is there any specific scenario where the issue is seen. Also capture during the issue will help.
Please note, we may need more time to get this issue reproduced during the the COVID-19 period.
thank you for your reply. I have seen the issue a couple of times but was not able reproduce it afterwards.
I will check, if I can reproduce it in a stable way and make a capture.
In reply to Stefan Pape:
I can reproduce the issue every time I startup the DLR network from power-on reset.
I am using the following network setup:
L27ERM [PORT1] <==> TAP <==> [PORT1] DUT [PORT2] <==> [PORT2] L27ERM
When the DLR ring is up and the control application is running, I read out the supervisor address information from the ICSS shared data RAM. The MAC address is equal to the MAC address of the supervisor, the IP address is 0.
The IP address sometimes contains the correct value, when I remove and re-attach both Ethernet cables from the DUT. But In most cases the IP address remains 0.
I attatched a Wireshark capture file that is made in error case (ring_normal_suv_ip_0.pcapng). I am not sure if you can reproduce the issue but maybe the Wireshark capture contains some more information. If not, are there some indicators in your receive flow that could give a hint what may go wrong?
It seemed you forgot to attach the capture?
sorry, here it comes.
I would like to ask if you had the opportunity for further investigations?
Thank you and best regards
I could confirm your observation from the capture - the Beacon frame source IP is always 0.0.0.0 including the frame #209 neighbor check request (but #210 is neighbor check response frame). The lockdown impacts us to reproduce the issue. I have been trying to get more input from team...will get back to you on this.
did you receive any further input from your team?
This is still in our list, we are going to update you as soon as possible.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.