Jetson AGX orin 40 pin

Hi

I’m doing some testing for 40 pins GPIO function

I configured all pins to GPIO with output direction and drive1 from pinmux and flash the device

here is the result

green pins worked all fine, and I can control it by using Jetson GPIO python tools

pink pins led lights up, but I can’t control it with GPIO tools, both gpioset & python

orange pins just not working, LED lights down, and I can’t control

I’ve checked the Python code and noticed that these 6 pins are not defined.

Can anyone tell me why?

and does that mean I can’t configure these 6 pins as GPIO usage?

Thanks

Kevin

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I’ll try to help you understand why some of your GPIO pins are not working as expected.

Firstly, it’s great that you’ve configured all pins to GPIO with output direction and drive1 from pinmux and flashed the device image. However, it seems like there are some issues with certain pins.

Let’s break down the issues you’re facing:

  1. Green pins: These pins are working fine, and you can control them using Jetson GPIO python tools. This suggests that the configuration and setup for these pins are correct.
  2. Pink pins: These pins have LED lights up, but you can’t control them with GPIO tools. This indicates that the pins are being driven by something else, possibly by the MB1 BCT (Boot and Control Tree) configuration. Since the pins are not defined in the Python code, it’s likely that they are not configured as GPIO pins in the pinmux spreadsheet.
  3. Orange pins: These pins are not working at all, and the LED lights are down. This could be due to several reasons:
    • The pins might not be configured as GPIO pins in the pinmux spreadsheet.
    • The pins might be configured as SFIO pins by the MB1 BCT, which would prevent them from being used as GPIO pins.
    • The pins might not be part of the 40-pin header, which is required for dynamic pin setting changes using GPIO tools.

To resolve these issues, I recommend the following steps:

  1. Verify pinmux configuration: Double-check the pinmux spreadsheet to ensure that all pins are configured as GPIO pins with the correct direction (output) and drive strength (drive1).
  2. Check MB1 BCT configuration: Verify that the MB1 BCT configuration is not overriding the pinmux settings for the pink and orange pins. You can use the tegraflash tool to dump the MB1 BCT configuration and check the pin settings.
  3. Update Python code: Add the missing pin definitions to the Python code to ensure that all pins are properly configured and can be controlled using the GPIO tools.
  4. Reflash the device: Reflash the device with the updated pinmux configuration and MB1 BCT settings to ensure that all changes take effect.

By following these steps, you should be able to resolve the issues with the pink and orange pins and get all GPIO pins working as expected.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Hi,

I think I’ve double check the pinmux setting

Take these pins as example , I only change these three rows and generate gpio & pinmux file

Kevin

Hi kevintseng83,

It seems you are using AGX Orin devkit.
What’s the Jetpack version in use?

Are you verifying with Jetson.GPIO?

If so, have you tried to add them into the table and check if they could work?

Please confirm those 6 pins are not used by any driver in device tree before use.

Hi

I’m using Jetpack 6.2

image

I’m using both gpioset cmd and Jetson.GPIO

Jetson GPIO will block from code(USING PR.03 UART1_RX)

and gpioset cmd just show nothing and not working

image

Yes, I’ve checked all these pins are unused

Kevin

Have you confirmed they are applied correctly?
You can simply check the flash log to know if the new pinmux dtsi has been used for pinmux_config.

For JP6.x, please apply the patch from 40hdr - SPI1 gpio padctl register bit[10] effect by gpiod tools in JP6 - #20 by KevinFFF to verify.

I would suggest using the following command instead.

# gpioset --mode=wait `gpiofind "PR.03"`=0
# gpioset --mode=wait `gpiofind "PR.03"`=1

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.