Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When using jetpack 6.1 with jetson-gpio, the message "Could not determine Jetson model" appears? #116

Closed
EESN-W opened this issue Dec 20, 2024 · 10 comments

Comments

@EESN-W
Copy link

EESN-W commented Dec 20, 2024

I upgraded the Jetson Orin Nano Developer Kit to Super (jetpack 6.1). How long will it take to get the GPIO control function?

@EESN-W
Copy link
Author

EESN-W commented Dec 20, 2024

Image

@EESN-W
Copy link
Author

EESN-W commented Dec 20, 2024

Image

@meetwudi
Copy link

export JETSON_MODEL_NAME=JETSON_NANO temporarily works around this. Turns out this environment variable is no longer set in 6.1 rev.1.

@EESN-W
Copy link
Author

EESN-W commented Dec 23, 2024

export JETSON_MODEL_NAME=JETSON_NANO temporarily works around this. Turns out this environment variable is no longer set in 6.1 rev.1.

Thank you for your reply. I can successfully read the pin level by setting export JETSON_MODEL_NAME=JETSON_ORIN_NANO.

@dakejahl
Copy link

Tested on a Jetson Orin Nano with Jetpack 6.2 (r36.4.3) and the issue still persists. Setting this solves it

export JETSON_MODEL_NAME=JETSON_ORIN_NANO

@anhmiuhv
Copy link
Collaborator

anhmiuhv commented Feb 6, 2025

The latest Jetson.GPIO version 2.1.8 should be supporting Jetson Orin Nano Super. If you still have a problem, please refer to this

The library determines the jetson model by checking `/proc/device-tree/compatible` and `/proc/device-tree/chosen` by default.

for how the Jetson.GPIO detects the hardware it is running on.

Setting the environment variable like this is a way to support unsupported hardware
export JETSON_MODEL_NAME=JETSON_ORIN_NANO

@anhmiuhv anhmiuhv closed this as completed Feb 6, 2025
@dakejahl
Copy link

dakejahl commented Feb 6, 2025

@anhmiuhv I just tried 2.1.8 and it's the same issue. Looking at /proc/device-tree I see that my board is correctly identified as a Jetson Orin Nano Super

jetson@jetson:~$ cat /proc/device-tree/compatible
nvidia,p3768-0000+p3767-0004-supernvidia,p3767-0004nvidia,tegra234

@anhmiuhv
Copy link
Collaborator

anhmiuhv commented Feb 7, 2025

Let me take a look again

@anhmiuhv anhmiuhv reopened this Feb 7, 2025
@anhmiuhv
Copy link
Collaborator

anhmiuhv commented Feb 7, 2025

@anhmiuhv I just tried 2.1.8 and it's the same issue. Looking at /proc/device-tree I see that my board is correctly identified as a Jetson Orin Nano Super

jetson@jetson:~$ cat /proc/device-tree/compatible
nvidia,p3768-0000+p3767-0004-supernvidia,p3767-0004nvidia,tegra234

Can you take a look again?

@dakejahl
Copy link

dakejahl commented Feb 7, 2025

@anhmiuhv 2.1.9 fixes the issue. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants