Issue with GPIO Pin Configuration Using Jetson-IO on Jetson AGX Xavier

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
,
1

Claro! Aqui está a tradução para o inglês:

Issue with GPIO Pin Configuration Using Jetson-IO on Jetson AGX Xavier

During a recent test with my Jetson AGX Xavier, I used the jetson-io.py utility located at /opt/nvidia/jetson-io/ to reconfigure pins 29 and 31. After making the changes and rebooting the device, the Jetson-IO tool stopped functioning properly.

When I try to launch it again using sudo /opt/nvidia/jetson-io/jetson-io.py, the interface briefly flashes on the screen and then immediately closes without displaying any error messages or logs.

I would really like to avoid reflashing the device, as the system is already heavily customized. Is there a way to revert the pin configuration changes or restore the Jetson-IO tool’s functionality without performing a full reflash?

Any guidance would be greatly appreciated.

3

Hi thailon.oliveira,

Are you using the devkit or custom board for AGX Xavier?
What’s the Jetpack version in use?

Please share the detailed steps how did you use jetson-io to reproduce the issue.
We would like to verify and debug it locally.

5

Hello, I’m using a devkit with JetPack version 5.0.2. Fortunately, I was able to resolve the issue this morning. The problem occurred when using a terminal with screen—the Jetson froze when running jetson-io.py and showed an error indicating that /mnt/APP was not mounted.

It turns out that every time the Jetson restarted, it automatically recreated the problematic file. To work around this, I created a systemd service that automatically deletes the file right after it is created. This allowed the code to run without issues.

Thank you for your attention. If anyone needs the exact commands I used, I’d be happy to share them!

1 Like
6

Hi thailon.oliveira,

Good to hear that :)

Which file do you mean?
Could you share the command you used in this topic to help others with similar issues?

8

I encountered the error:

Mountpoint /mnt/APP already exists!

To investigate, I ran:

mount | grep /mnt/APP

This returned no output, suggesting that nothing was actually mounted there. So I removed the directory using:

sudo rm -r /mnt/APP

After that, I was able to successfully run:

sudo /opt/nvidia/jetson-io/jetson-io.py

However, the problem was that the /mnt/APP directory kept getting recreated automatically after each reboot. To handle this, I created a cleanup script:

Script: /usr/local/bin/remove-mnt-app.sh

#!/bin/bash
rm -rf /mnt/APP

I made it executable:

sudo chmod +x /usr/local/bin/remove-mnt-app.sh

Then, I created a systemd service to run this script at boot:

Service: /etc/systemd/system/remove-mnt-app.service

[Unit]
Description=Remove /mnt/APP on boot
After=local-fs.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/remove-mnt-app.sh
RemainAfterExit=true

[Install]
WantedBy=multi-user.target

I reloaded systemd and enabled the service with:

sudo systemctl daemon-reexec
sudo systemctl enable remove-mnt-app.service

This setup now automatically removes /mnt/APP at boot, preventing conflicts when using jetson-io.py.

1 Like