Busy configuring the ethernet to the jetson. In editing this, I came onto the following error:
dump(3).txt (26.5 KB)
The changes I’ve made that have brought me to this error were the following:
-
Enabling ethernet by making ODMDATA=“gbe-uphy-config-22,nvhs-uphy-config-0,hsio-uphy-config-0,gbe0-enable-10g,hsstp-lane-map-3”;
-
Changed PINMUX to match whats expected for RGMI
I saw in a previous forum that this error was indeed caused by I2C, but I’ve checked all I2C pins, and none have pull ups/downs. Furthermore, i saw it was solved through correcting a faulty ethernet port, is there any more info on that?
*** Please note that this reply is generated by LLM automatically ***
The error you’re encountering is related to the configuration of the Ethernet interface on the Jetson AGX Orin module. The changes you’ve made, specifically enabling Ethernet and modifying the PINMUX configuration to match the expected settings for RGMII, are likely contributing factors.
The error dump you’ve shared suggests that there’s an issue with the I2C communication, which is used to configure the Ethernet PHY (Physical Layer) device. Although you’ve checked the I2C pins and found no pull-ups or pull-downs, it’s possible that there’s still an issue with the I2C communication.
Comparing your situation to the previous forum discussion you mentioned, it’s likely that the issue is indeed related to the Ethernet port configuration. Here are a few potential causes and solutions to consider:
- Faulty Ethernet port: As mentioned in the previous forum discussion, a faulty Ethernet port can cause issues with the I2C communication. Try using a different Ethernet port or replacing the Ethernet cable to rule out any hardware issues.
- PINMUX configuration: Double-check your PINMUX configuration to ensure that it matches the expected settings for RGMII. You can refer to the Jetson AGX Orin documentation or the NVIDIA developer forum for guidance on configuring the PINMUX.
- I2C communication: Although you’ve checked the I2C pins, it’s possible that there’s still an issue with the I2C communication. Try using a logic analyzer or an oscilloscope to monitor the I2C signals and ensure that they’re correct.
- Ethernet PHY configuration: The Ethernet PHY device may require specific configuration settings to function correctly. Check the documentation for your Ethernet PHY device to ensure that you’re using the correct configuration settings.
To troubleshoot the issue further, you can try the following:
- Check the kernel logs: Look for any error messages related to the Ethernet interface or I2C communication in the kernel logs.
- Use the
ethtool command: Run the ethtool command to check the status of the Ethernet interface and ensure that it’s configured correctly.
- Try a different Ethernet configuration: Try using a different Ethernet configuration, such as a different PHY device or a different cable, to rule out any issues with the current configuration.
By comparing your situation to the previous forum discussion and trying the suggested troubleshooting steps, you should be able to identify and resolve the issue with the Ethernet interface on your Jetson AGX Orin module.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
A reminder. If no EEPROM is on the carrier board, then need to set this . Though I feel it is from something else.
Just another question.
Actually you already passed all these items previously before. It seems you are making a regression error here.
What did you change to create this?
I feel this is more related to pinmux change but nothing related to Ethernet.
You should try to change one item at once but not all of them at once. You won’t know what item is causing the regression error if doing all those things altogether.