Jetson Orin Nano Super Dev Kit validation

I recently bought a Jetson Orin Nano super dev kit 8 GB from a local vendor, but I doubt that they gave me Orin NX instead of Orin Nano, because when I was re-flashing with SDK Manager, it found it as Orin NX not Orin Nano, so it there any way to validate that the module mounted on the dev kit carrier board is actually Orin Nano not Orin NX ?

Thanks in advance

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

To validate whether the module mounted on the dev kit carrier board is actually Jetson Orin Nano or Jetson Orin NX, you can follow these steps:

  1. Check the Module Part Number: The part number of the module is usually printed on the module itself. For Jetson Orin Nano, the part numbers are:

    • P3767-0003 for Jetson Orin Nano 8GB module
    • P3767-0004 for Jetson Orin Nano 4GB module
    • P3767-0005 for Jetson Orin Nano developer kit module with SD Card
      For Jetson Orin NX, the part numbers are:
    • P3767-0000 for Jetson Orin NX 16GB module
    • P3767-0001 for Jetson Orin NX 8GB module
      Compare the part number on the module with the above list to determine whether it’s Orin Nano or Orin NX.
  2. Check the EEPROM: The EEPROM on the module contains information about the module, including its type and part number. You can use the lspci command to read the EEPROM data. The output should indicate whether the module is Orin Nano or Orin NX.

  3. Check the Module ID: The module ID is a unique identifier for each module. For Jetson Orin Nano, the module ID is 2888, while for Jetson Orin NX, the module ID is also 2888. However, the SKU (Stock Keeping Unit) is different for each module. For Jetson Orin Nano, the SKU is 0003 or 0005, while for Jetson Orin NX, the SKU is 0000 or 0001.

  4. Compare the Physical Characteristics: Jetson Orin Nano and Jetson Orin NX modules have different physical characteristics, such as the size and shape of the module, the location of the connectors, and the type of memory used. Compare the physical characteristics of the module on your dev kit with the specifications for Jetson Orin Nano and Jetson Orin NX to determine whether it matches one or the other.

  5. Check the SDK Manager Output: The SDK Manager output you mentioned earlier indicates that the module is detected as Orin NX. However, this may not be conclusive, as the SDK Manager may not always correctly identify the module type.

By following these steps, you should be able to determine whether the module mounted on your dev kit carrier board is actually Jetson Orin Nano or Jetson Orin NX.

Comparison of Jetson Orin Nano and Jetson Orin NX

Here’s a summary of the key differences between Jetson Orin Nano and Jetson Orin NX:

  • Part Number: Jetson Orin Nano has part numbers P3767-0003, P3767-0004, and P3767-0005, while Jetson Orin NX has part numbers P3767-0000 and P3767-0001.
  • Module ID: Both Jetson Orin Nano and Jetson Orin NX have the same module ID (2888), but the SKU is different.
  • Physical Characteristics: Jetson Orin Nano and Jetson Orin NX modules have different physical characteristics, such as size, shape, and connector locations.
  • Memory: Jetson Orin Nano has 4GB or 8GB of memory, while Jetson Orin NX has 8GB or 16GB of memory.
  • Performance: Jetson Orin NX has higher performance than Jetson Orin Nano due to its more powerful GPU and CPU.

I hope this helps you determine whether your module is actually Jetson Orin Nano or Jetson Orin NX.

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

How to read EEPROM data without using the lspci command ?

Did sdkmanager finish flashing ?

I didn’t flash it as it came pre-flashed with jetpack 6.2, but I tried the sdkmanager flashing procedure without flashing it as it was my first time and I wanted to learn how to use it.

So are you able to operate your Jetson in any way now?

Yes, I’m working on it

sudo i2cdump -f -y 0 0x50 shall give you the EEPROM content.

This is the output :

No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 ff 00 00 00 00 ?.?..
10: 00 01 00 01 36 39 39 2d 31 33 37 36 37 2d 30 30 .?.?699-13767-00
20: 30 31 2d 35 30 30 00 00 00 00 00 00 00 00 00 00 01-500…
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
40: b0 48 00 00 14 a2 f7 2d b0 48 31 36 31 34 31 32 ?H..???-?H161412
50: 33 35 32 30 33 33 39 00 00 00 00 00 00 00 00 00 3520339…
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
90: 00 00 00 00 00 00 4e 56 43 42 00 ff 4d 31 00 00 …NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 14 a2 f7 2d …???-
b0: b0 48 01 00 00 00 00 00 00 00 00 00 00 00 00 00 ?H?..
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 db …?

This is 3767-0001 which is Orin NX 8GB.

But, yesterday I tried one of the models from the llms catalog Models - NVIDIA Jetson AI Lab to run in a docker container.

The output logs shows that the identified jetson is Jetson Orin Nano 8GB, I became confused again :D

Not sure what “logs” is that. The module is decided by the EEPROM.

Always use the EEPROM content to tell what you are using there.

1 Like

So, my last question, is there’s a possibility to modify the EEPROM content when flashing to identify the module version other than the actual module version, like to identify a jetson orin nano as jetson orin nx , is that possible ??

It would have problem and make your board not able to get flashed or boot anymore.

And you will have no chance to modify the EEPROM back to default value again because the board is not able to get operated anymore.

1 Like

Okay, I understand.

Thanks for you help @WayneWWW

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