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

[EESN-W]

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]

[EESN-W]

[meetwudi]

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]

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]

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]

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

jetson-gpio/README.md

Line 453 in fe01769

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

[dakejahl]

@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]

Let me take a look again

[anhmiuhv]

@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]

@anhmiuhv 2.1.9 fixes the issue. Thank you!