DRIVE OS Version: DRIVE OS version:7.0.3
Issue Description:
We are currently working with a sensor that outputs UDP data using jumbo frames at approximately 2.5 Gbit/s.
Setup Details:
-
The sensor is connected via HMTD (Automotive Ethernet) to the J4 MGBE0 (10G) port.
-
The sensor operates in Slave mode
-
On the receiving interface:
image675×236 70.5 KB
Issue:
Despite the above configuration, we are unable to receive any data on the J4 MGBE0 interface.
Validation:
To verify the sensor output, we tested the same setup using a media converter, connecting the sensor to the Orin 10G Standard Ethernet interface:
- Using identical IP and MTU settings, we are able to successfully receive the UDP data in this configuration.
Questions:
-
Are there any specific VLAN tagging requirements for the J4 MGBE0 automotive Ethernet interface that we need to configure?
-
Are there any additional driver, PHY, or interface settings required to handle high-throughput jumbo UDP frames on this port?
-
Is there any known limitation or special configuration needed for HMTD-based automotive Ethernet connections on this interface?
Attached the log file for additional information
Mgbe0_Log.txt (8.1 KB)
This issue is currently blocking our integration and validation activities, and we would greatly appreciate an urgent response or guidance to help us progress.
Dear @Adas.Engineer ,
Which sensor is connected to mgbe0 port?
Is it possible to connect mgbe0 port to a host and try ping/sending packets to confirm if they are receiving fine. From the log I see mgbe0 IP is changed and MTU is set to 8966.
We have connected the radar sensor to the MGBE0 port and configured the IP address and MTU (8966) as per the sensor requirements.
With the same configuration, we are able to successfully receive the radar sensor data on the Orin 10G interface when using a 10G media converter, which confirms that the sensor setup is working as expected. However, we would like to avoid having the media converter in the loop, and our goal is to directly connect the sensor to the master automotive Ethernet port on Thor (MGBE0).
Regarding your suggestion to validate the interface, we would like to confirm our understanding:
Do you mean that we should connect the MGBE0 port to a host system (Ubuntu PC) using 1G NIC adapter, and then perform ping or packet transmission tests to verify connectivity? Can I use 1G NIC for verifying the 10G mgbe0 port?
Also, according to documentation it says the 1G NIC adapter only works with one particular port, can still use this to validate the mgbe0 interface ?
Tried connecting both a 1G NIC and a 10G media converter to the J4 MGBE0 port, but I am unable to ping the interface in either setup from the host PC. Is there any additional configuration or steps required to enable or bring up this port?
Both host and target are in same network? If so, ping should work.
Dear @Adas.Engineer ,
When using 10G adapter on orin, you are getting jumbo packets and failed to get in Thor with 10G adapter? Is it the case?
Yes, they are in same network.
Dear @Adas.Engineer ,
Could you check setting static IP like in Ethernet setup Drive AGX Thor devkit SKU10 - #12 by andreas.westhues helps to make ping works ?
Please confirm if orin can receive jumbo packets from sensors when connected via 10GB adapter. If so, please check if the same behaviour can be observed on Thor devkit as well.
Could you please provide any update for this topic?
We are still facing issues receiving jumbo packets on the Thor unit. Further investigation and discussion are currently ongoing via private messages.
Could you please confirm whether the 10G interfaces (configured via XFI) support auto-negotiation to lower multi‑gigabit speeds such as 2.5 Gbps or 5 Gbps? Or are these interfaces strictly limited to a fixed 10 Gbps line rate unless used with a specific external PHY or manually reconfigured?
Additionally, the network diagram indicates the presence of a 2.5G interface. Could you clarify how this interface can be accessed and which physical and mgbe interface should be used to operate at 2.5 Gbps?
Finally, could you also advise if any switch firmware updates are required on our side to enable or properly support 2.5 Gbps operation?
@carolyuu @SivaRamaKrishnaNV - could you please clarify the details related to the questions posted above
Dear @Adas.Engineer ,
My apologies, I missed your last update in PM.
I don’t see the picture in last post. Is it about configuring P8 in condor switch 2 from
P3960 Network Topology — NVIDIA DriveOS 7.0.3 Linux SDK Developer Guide ?
Yes, I am referring to P8 in condor switch 2
@carolyuu @SivaRamaKrishnaNV Could you please provide more details on the 2.5G interface support? Specifically, how can 2.5G be enabled on port P8 of Condor2, and which mgbe interface should be used for this configuration?
Dear @Adas.Engineer ,
I am yet to get an update engineering team. I will post here once I have an update.
Dear @Adas.Engineer ,
The condor 2 port 8 is not used in TS3. You can refer to P3960-TS3 Topology picture (P3960 Network Topology — NVIDIA DriveOS 7.0.3 Linux SDK Developer Guide)
The sensor is connected via HMTD (Automotive Ethernet) to the J4 MGBE0 (10G) port.
From private message,
I was able to successfully ping the mgbe0_0 interface from the target system when both sides were configured in the same subnet and the media converter speed was set to 10 Gbit/s. However, communication failed when the media converter was configured to 2.5 Gbit/s
Now you can configure host side networking settings using netplan and able to establish connection between host and target. why can’t you use the converter at 10Gbps ?
Meanwhile, could you use media converter with10Gbps setting and check sending packets from host(instead of sensor) using iperf application with 2.5G and verify if there is any issue. Ideally, if MAC/UPHY/PHY/HMTD Dongle configured at same speed (10G). I expect there should not be any issue transmitting the data with 2.5Gbps.
Now you can configure host side networking settings using netplan and able to establish connection between host and target. why can’t you use the converter at 10Gbps ?
→ This test was conducted to verify communication with the interface at 2.5G. However, it was unsuccessful, as the link is currently being established only at 10G. We need to ensure that the link can be properly established at 2.5G, since our sensor operates at a maximum data rate of 2.5 Gbps.
Meanwhile, could you use media converter with10Gbps setting and check sending packets from host(instead of sensor) using iperf application with 2.5G and verify if there is any issue. Ideally, if MAC/UPHY/PHY/HMTD Dongle configured at same speed (10G). I expect there should not be any issue transmitting the data with 2.5Gbps.
→ I tried using the iPerf application at 2.5G, and it only worked when the initial link with the media converter was first established at 10G. Based on these observations, it appears that the 10G port does not establish a link unless the connected device is also operating at 10G.
Since our sensor transmits at 2.5 Gbps, it is unlikely that it will successfully bring up a link on a 10G-only port. This suggests that the PHYs on the 10G ports may be configured to support only 10G operation, without compatibility for intermediate speeds such as 2.5G or 5G.
Could you please confirm if the 10G PHYs are limited to 10G-only operation? If so, would you recommend a PHY firmware update or any configuration changes to enable support for 2.5G speed?
Dear @Adas.Engineer ,
The 10G interface can get packets from sensor at 2.5Gbps. But
From first shared logs Mgbe0_Log.txt when sensor is connected to target, I see ifconfig output shows flags=4099<UP,BROADCAST,MULTICAST> for mgbe0_0 interface. I don’t see RUNNING in the flag for ping to work. Does this radar has any link configured at 2.5G (As you said earlier that you configured dongle at 2.5G to test if it can receive data ).
How are the flags when target is connected to a host directly in your previous test?
Could you share below observations when sensor is connected and sending data when using default MTU and MTU=9k
on target
tcpdump -i mgbe0_0
ethtool -S mgbe0_0
dmesg log
On docker
ethernet server logs of target(run tcu_muxer -d /dev/ttyACM0 -m T264 -b 15 -g 16 -s /home/nvidia/ and share the logs in /home/nvidia/)
The radar is able to establish a link with the Technica media converter when it is configured at 2.5G speed. When the target is connected directly to the host, the interface consistently shows the RUNNING flag.
However, when the sensor is connected, the behavior becomes inconsistent — the interface sometimes shows RUNNING and sometimes does not. Additionally, even in cases where the interface shows RUNNING with the sensor connected, no UDP data is observed on the interface.
The requested logs have been shared via private message for further analysis.
