Hardware differences between Orin AGXs

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

OK, so I have purchased two Orin AGXs, but there was quite a bit of time difference in when I purchased them. I had come across an issue where my software would error out (error code 161) on one of them.

So, just to make sure that I’m comparing apples to apples, I reflashed both of these Orin AGXs with Jetpack 5.1. sdkmanager seemed to run into an issue when trying to flash them, so I just used the ./flash.sh script (running the command ‘./flash.sh jetson-agx-orin-devkit mmcblk0p1’).

Even after reflashing both of these Orin AGXs, my software would still error out (with error code 161) on just one of the AGXs… (the same one, of course.)

I noticed that the one that’s giving me issues has a Wifi adapter on it, whereas the one that works does not. I’m guessing this must indicate that there’s at least a slight hardware difference between the two Orin AGXs. Is there a quick way for me to find out what Hardware Revisions I’m running on my two AGXs, (and possibly find out what those differences are?)

4

Hi,
Please try

Jetson AGX Orin FAQ
Q: How to know if I use Orin developer kit or Orin 32GB module?

to identify whether the two modules are identical or different.

5

I assume you’re referring to " Q: How to know if I use Orin developer kit or Orin 32GB module?"

For my ‘working’ one:

$ cat /etc/nv_boot_control.conf
TNSPEC 3701-500-0005-R.0-1-1-jetson-agx-orin-devkit-
COMPATIBLE_SPEC 3701–0005–1–jetson-agx-orin-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

For my ‘non-working’ one:

$ cat /etc/nv_boot_control.conf
TNSPEC 3701-500-0005-R.0-1-1-jetson-agx-orin-devkit-
COMPATIBLE_SPEC 3701–0005–1–jetson-agx-orin-devkit-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

For good measure, my ‘working’ one:

$ cat /etc/nv_tegra_release

R35 (release), REVISION: 2.1, GCID: 32413640, BOARD: t186ref, EABI: aarch64, DATE: Tue Jan 24 23:38:33 UTC 2023

For my ‘non-working’ one:

$ cat /etc/nv_tegra_release

R35 (release), REVISION: 2.1, GCID: 32413640, BOARD: t186ref, EABI: aarch64, DATE: Tue Jan 24 23:38:33 UTC 2023

6

By the way… I had misspoke… Both Orin AGXs did have a Wifi module. On the ‘working’ one, it was disconnected and removed. So… I may not have a hardware difference at all…

7

Hi,
Both are AGX Orin 32GB modules. So modules are identical. It may be other deviation. Please remove the wifi module on both platforms and see if the behavior is identical.

8

Hi,

We did try removing the Wifi modules, and the behavior was the same.

After further investigation, we traced it back to an NV100 module that we had installed on the AGX’s. The problem was the result of one particular NV100 module that was causing our issue. Thanks for the tips, it looks like the Orin AGXs weren’t the problem at all.

1 Like
10

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