Jetson AGX Orin board ID, SKU, FAB

Hi,

We are facing issue with different mix of BOARDID, BOARDSKU, FAB and BOARDREV (for single board).

Some of them are listed in README_initrd_flash.txt

Environment variables value table:

#
#                                       BOARDID  BOARDSKU  FAB  BOARDREV
#    ----------------------------------+--------+---------+----+---------
#    jetson-agx-xavier-industrial         2888     0008      600  A.0
#    clara-agx-xavier-devkit              3900     0000      001  C.0
#    jetson-xavier-nx-devkit              3668     0000      100  N/A
#    jetson-xavier-nx-devkit-emmc         3668     0001      100  N/A
#    jetson-xavier-nx-devkit-emmc         3668     0003      N/A  N/A
#    jetson-agx-xavier-devkit (16GB)      2888     0001      400  H.0
#    jetson-agx-xavier-devkit (32GB)      2888     0004      400  K.0
# >> jetson-agx-orin-devkit               3701     0001      TS1  C.2
# >> jetson-agx-orin-devkit               3701     0000      TS4  A.0
#    jetson-agx-xavier-devkit (64GB)      2888     0005      402  B.0
#    holoscan-devkit                      3701     0002      TS1  A.0
# >> jetson-agx-orin-devkit               3701     0004      TS4  A.0
# >> jetson-agx-orin-devkit (64GB)        3701     0005      500
#    jetson-orin-nano-devkit (NX 16GB)    3767     0000      300
#    jetson-orin-nano-devkit (NX 8GB)     3767     0001      300
#    jetson-orin-nano-devkit (Nano 4GB)   3767     0004      300
#    jetson-orin-nano-devkit (Nano 8GB)   3767     0003      300
#    jetson-orin-nano-devkit (Nano 8GB)   3767     0005      300
#    ----------------------------------+--------+---------+----+---------

AGX Orin 32GB

Board ID(3701) version(500) sku(0000) revision(M.0)
Chip SKU(00:00:00:D0) ramcode(00:00:00:00) fuselevel(fuselevel_production) board_FAB(500)

AGX Orin 32GB

Board ID(3701) version(500) sku(0000) revision(L.0)
Chip SKU(00:00:00:D0) ramcode(00:00:00:00) fuselevel(fuselevel_production) board_FAB(500)

For 32GB version is FAB=500 and this is missing from table


AGX Orin 64GB

Board ID(3701) version(500) sku(0005) revision(R.0)
Chip SKU(00:00:00:D0) ramcode(00:00:00:03) fuselevel(fuselevel_production) board_FAB(500)

Revision M.0 , R.0 , L.0 are missing from table

Could somebody explain differences in between them
For example BOARDSKU 0000, 0001, 0004 for 3701 (AGX Orin devkit 32GB model)

Which are universal values for flashing 32GB model

BOARDID=3701
BOARDSKU=
FAB=
BOARDREV=

What is your purpose to know the detail here?

The flash process will read the info from your module EEPROM so you don’t need to manually write it for flash.sh.

If your module is production module, then it will definitely be p3701-0004.

If your module is from devkit, then it will be p3701-0000.
There won’t be 0001 for any 32GB module for Jetson.

We are producing and using Mass flash images , so flash.sh is not option. In case we use flash.sh we need to carry whole Linux_for_Tegra content which is huge.

You can just pick one of the module info and write it into massflash.

If there is any problem, we can discuss it later.

Just a reminder, you cannot use same massflash image for both Orin 32GB and 64GB. It must regenerate.

If your module is production module, then it will definitely be p3701-0004.

If your module is from devkit, then it will be p3701-0000.
There won’t be 0001 for any 32GB module for Jetson.

So we could say :

  • For Jetson AGX Orin Devkit - 32GB
BOARDID=3701
BOARDSKU=0000
FAB=<not important>
BOARDREV=<not important>

important

  • For Jetson AGX Orin Devkit - 64GB
BOARDID=3701
BOARDSKU=0005
FAB=<not important>
BOARDREV=<not important>

MFI images created with those values will be capable of flashing :

  • MFI for 3701-0000 all Jetson AGX Orin devkits with 32GB
  • MFI for 3701-0005 all Jetson AGX Orin devkits with 64GB

Hi,

There is a minor mistake. The sku for 32GB is 0004 but not 0000. 0000 is devkit module. You are not using a devkit module to make your own product.

The FAB is also important but the BOARDREV does not.

Just a reminder, you cannot use same massflash image for both Orin 32GB and 64GB. It must regenerate.

That part is clear.

We were looking for some kind of hybrid solution to be able to flash all Jetson AGX Orin devkits (32GB/64GB) with single MFI image.

But maybe this is not yet supported

Sorry, that is not supported.

There is a minor mistake. The sku for 32GB is 0004 but not 0000. 0000 is devkit module. You are not using a devkit module to make your own product.

Devkits are used for development not a product. So for dev kit 0000 is right , based on your comments.

The FAB is also important but the BOARDREV does not.

So in that case I assume we should use only ?

FAB=TS4

Hi,

If you are talking about you want to massflash devkit modules, then use 0000.
If you are talking about you want to massflash production modules, then use 0004.

My point is you won’t put a devkit module on your product. That’s all.

The module info should be checked from the EEPROM.

FAB=TS4

Your previous eeprom said you are using FAB=500. So please just use 500 for your FAB

Yes mine is FAB=500 and I will stick to that, but my board combination is not listed in the table.
Can you elaborate please , what exactly is the difference between different FABs.

There is nothing to clarify. Your module FAB 500 will be stick for production module.

Some of the modules on the list are out of date. We may try to update the table.

I suppose next table will be with next official JetPack 6 ?
If you have more recent one at you disposal, could you share it ?

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