*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing issues with configuring GPIO pins on the Jetson AGX Orin developer kit. Specifically, you have configured pins E7 and E6 to GPIO mode, but when measuring the voltage using a multimeter, you are reading a low value (0V) on pins TP52 and TP53.
To troubleshoot this issue, let’s break down the possible causes:
Software configuration: You have mentioned that you have configured the pins to GPIO mode, but it’s essential to ensure that the configuration is correct. Double-check that you have properly set the pin modes using the jetson-io tool or by modifying the device tree.
Hardware connections: Verify that the connections between the Jetson module and the external circuitry are correct. Ensure that the pins are properly connected to the desired external components, and there are no shorts or open circuits.
Pin multiplexing: The Jetson AGX Orin module has multiple functions assigned to each pin. It’s possible that the pins you are trying to use are multiplexed with other functions. Check the Jetson AGX Orin datasheet or the device tree to ensure that the pins are not multiplexed with other functions that might be interfering with your GPIO configuration.
Power management: The Jetson AGX Orin module has power management features that might be affecting the pin behavior. Check the power management settings to ensure that the pins are not being powered down or put into a low-power state.
Comparing your issue with other related topics:
The topic “Issue with GPIO Pin Configuration Using Jetson-IO on Jetson AGX Xavier” (June 4, 2025) mentions a similar issue with GPIO pin configuration on the Jetson AGX Xavier. However, the solution provided in that topic is specific to the Xavier module and might not be directly applicable to the AGX Orin.
The topic “CAN configuration and suspension issues” (June 4, 2025) discusses CAN bus configuration issues on the Jetson TX2, which is a different module. However, it highlights the importance of proper device tree configuration, which might be relevant to your issue.
To further troubleshoot your issue, you can try the following:
Use the jetson-io tool to verify that the pin configuration is correct.
Check the device tree to ensure that the pins are not multiplexed with other functions.
Use a logic analyzer or an oscilloscope to monitor the pin activity and verify that the signals are being generated correctly.
Consult the Jetson AGX Orin datasheet and the device tree documentation to ensure that you are using the correct pin configurations and settings.
If you are still experiencing issues, it might be helpful to provide more details about your setup, including the exact pin configurations, device tree modifications, and any relevant code snippets.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Have you tried toggling the GPIO? Or a GPIO external loopback from one to the other, set one GPIO (MDIO) as output and the other GPIO (MDC) as input, toggle the GPIO set as output and see if you can readback same value on the other GPIO (MDC) set as input.
But I double check the related gpio register 0x22158a0 and 0x2215880 which is 0x00000003
which means the pins are all gpio enable and output mode
and register 0x22158b0 and 0x2215890 value will change while the gpioset command trigger
for example: gpioset PF.05 = 1 will trigger 0x22158b0 value to 1 which is as expected. but using multimeter show zero voltage or using oscilloscope show no waveform
I try to use these two pin to simulate I2C signal, but see no wavefrom ( toggle gpio)
Any reason you need to simulate I2C signal on these GPIOs? We have multiple I2c busses available on the module. I2C is open drain signals and need external pull up to see the high logic level. The pins should be configured as bidirectional if want to simulate I2C signals and with external pull up resistors to see the high and low levels.
Do you mean those 2 pins are always LOW after you’ve configured them at Output/Drive 1 in pinmux spreadsheet?
If so, could you share the detailed steps how do you apply the change?
Yes , those two pins are all low, I apply the change as the online wiki says, modify the spreadsheet and burn dtb to flash, nothing special else
It seems to be hardware issue, I found on module side, the MDIO pin short to the ground, but MDC not short to the ground, I am about to send the module back to vendor to repair
and I will try to deploy all my setup on a new 32G module to test
