Difference between p3701-0000 and p3701-0005 SOM Board

CrazyCatt · July 9, 2026, 2:53pm

Hi,

I’m trying to understand the difference between the P3701-0000 and P3701-0005 Jetson AGX Orin SOM variants.

I’m using a Jetson AGX Orin 64GB Developer Kit and have flashed several different JetPack versions using SDK Manager over time, so I’ve lost track of which DTB file was originally shipped with the factory image. On my current installation, the device is using the following DTB:

kernel_tegra234-p3701-0005-p3737-0000.dtb

However, in most documentation, examples, and forum posts I’ve found online, the DTB referenced for the AGX Orin Developer Kit is:

kernel_tegra234-p3701-0000-p3737-0000.dtb

Could someone help me understand:

What is the difference between the P3701-0000 and P3701-0005 SOMs?
Are there any hardware differences that require different DTBs?
Did NVIDIA change the SOM identifier in newer JetPack releases, or would the SDK Manager automatically selecting a DTB based on the installed module revision?

Thanks!

carolyuu · July 9, 2026, 3:02pm

— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —

The difference between the P3701-0000 and P3701-0005 SOMs is not explicitly stated in the provided context. However, based on the information available, it appears that both P3701-0000 and P3701-0005 are SOM variants for the Jetson AGX Orin module.

In the context of device tree files, the naming conventions for the Jetson AGX Orin module are mentioned. The device tree files are named as follows:

tegra234-p3701-0000-p3737-0000.dts
tegra234-p3701-0008-p3737-0000.dts
tegra234-p3701-0000-as-pxxxx-p3737-0000.dts

According to the accepted solution in Topic #274673, P3701-0000 is the Orin AGX devkit module, and P3701-0008 is the Orin AGX industrial module.

However, there is no explicit information available in the provided context about the P3701-0005 SOM variant. It is possible that the P3701-0005 SOM variant is a newer or updated version of the P3701-0000 SOM variant, but without further information, it is difficult to determine the exact differences between the two.

Regarding the DTB files, the provided context does not explicitly state why the SDK Manager would select a different DTB file based on the installed module revision. However, it is possible that the SDK Manager selects the DTB file based on the SOM variant and the installed JetPack version.

In summary, while the provided context does not explicitly state the differences between the P3701-0000 and P3701-0005 SOM variants, it appears that both variants are used for the Jetson AGX Orin module, and the SDK Manager may select a different DTB file based on the installed module revision and JetPack version.

It is recommended to consult the official NVIDIA documentation or contact NVIDIA support for further clarification on the differences between the P3701-0000 and P3701-0005 SOM variants and the selection of DTB files by the SDK Manager.

— We support team will also look into your issue to have further suggestions soon. please stay tuned. —

KevinFFF · July 13, 2026, 1:14am

Hi CrazyCatt,

What’s the Jetpack version in use?

They are SKU0 and SKU5 AGX Orin module.
SKU0 is the module coming with the AGX Orin developer kit.
SKU5 is the commercial module used for the custom carrier board.
You can simply run cat /etc/nv_boot_control.conf to check.

Please refer to https://docs.nvidia.com/jetson/archives/r36.5/DeveloperGuide/index.html#devices-supported-by-this-document for details.

WayneWWW · July 13, 2026, 7:06am

also the sku5 is 64GB DRAM SOM.

CrazyCatt · July 13, 2026, 3:09pm

Hi KevinFFF,

I’m using JetPack 5.1.2 (L4T R35.4.1):

$ cat /etc/nv_tegra_release
# R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug  1 19:57:35 UTC 2023

My boot control information is:

$ cat /etc/nv_boot_control.conf
TNSPEC 3701-501-0005-G.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

The board is a Jetson AGX Orin 64GB Developer Kit. Based on suggestions from an AI tool, I also checked a few additional items:

$ cat /proc/device-tree/compatible
nvidia,p3737-0000+p3701-0005nvidia,p3701-0005nvidia,tegra234nvidia,tegra23x

/* EEPROM contents from I2C address 0x50 */
$ sudo i2cdump -f -y 0 0x50
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 00 00 00 00 00    ?.?.............
10: 00 00 00 0a 36 39 39 2d 31 33 37 30 31 2d 30 30    ...?699-13701-00
20: 30 35 2d 35 30 31 20 47 2e 30 00 00 00 00 00 00    05-501 G.0......
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 00 00 00 30 de b2 e2 3a ac 31 37 39 31 30 32    ....0???:?179102
50: 36 30 34 31 35 31 37 00 00 00 00 00 00 00 00 00    6041517.........
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 00 4d 31 00 00    ......NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 30 de b2 e2    ............0???
b0: 3a ac 0a 00 00 00 00 00 00 00 00 00 00 00 00 00    :??.............
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 b5    ...............?

I also checked with a colleague who has a Jetson AGX Orin 64GB Developer Kit that has never been reflashed using SDK Manager. Comparing the two systems, the main difference appears to be the output of cat /proc/device-tree/compatible:

$ cat /proc/device-tree/compatible
nvidia,p3737-0000+p3701-0000nvidia,p3701-0000nvidia,tegra234nvidia,tegra23x

$ sudo i2cdump -f -y 0 0x50
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 00 00 00 00 00    ?.?.............
10: 00 00 00 0a 36 39 39 2d 31 33 37 30 31 2d 30 30    ...?699-13701-00
20: 30 35 2d 35 30 31 20 47 2e 30 00 00 00 00 00 00    05-501 G.0......
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 00 00 00 93 d1 a3 47 bb 4c 31 37 39 34 32 32    ....???G?L179422
50: 35 31 30 36 32 38 39 00 00 00 00 00 00 00 00 00    5106289.........
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 00 4d 31 00 00    ......NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 93 d1 a3 47    ............???G
b0: bb 4c 0a 00 00 00 00 00 00 00 00 00 00 00 00 00    ?L?.............
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 20    ...............

$ cat /etc/nv_boot_control.conf
TNSPEC 3701-501-0005-G.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

Based on your previous explanation, my understanding is that since this is a developer kit, it should be using SKU0 rather than SKU5. However, even after reflashing the board multiple times with the JetPack 5.1.2 image for the 64GB Developer Kit through SDK Manager, the system always comes back using the 0005 DTB after reboot.

For flashing, I’m using the SDK Manager Docker image, since I don’t have an Ubuntu 18.04 or 20.04 host available. The Docker container is running on an Ubuntu 24.04 machine. The flashing process completes successfully, and I don’t see any errors during the reflash.

Could you help clarify whether seeing p3701-0005 on a Jetson AGX Orin 64GB Developer Kit is expected, or if there is something unusual about my board identification or flashing process? And how can I flash it back to use the correct configurations?

Thanks.

CrazyCatt · July 13, 2026, 3:12pm

Hi WayneWWW:

My machine is a Jetson AGX Orin 64GB Developer Kit:

$ free
              total        used        free      shared  buff/cache   available
Mem:       64309792     1219548    62351272       21016      738972    62490380
Swap:      32154880           0    32154880

According to KevinFFF:

SKU0 is the module coming with the AGX Orin developer kit.
SKU5 is the commercial module used for the custom carrier board.

Should Jetson AGX Orin 64GB Developer Kit be SKU0 or SKU5 or another SKU version?

WayneWWW · July 14, 2026, 3:54am

I remember that the SOM on Orin AGX devkit has been changed to the 64GB SOM for a while.

The EEPROM won’t be wrong.

Topic		Replies	Views
EEPROM Layout for Orin Production Modules and devkits Jetson AGX Orin documentation	5	1227	November 9, 2022
How to get critical parameters, such as fab, board id, sku, etc, for orin series products Jetson Orin NX boot , reflash , nvbugs	18	3083	June 26, 2023
Device Tree Mods upgrading from AGX Xavier to AGX Orin Jetson AGX Orin device-tree	35	1317	March 1, 2024
Need Board ID and Board SKU Jetson Orin NX kernel , board-design , nvbugs	10	3470	April 25, 2023
Jetson AGX Orin board ID, SKU, FAB Jetson AGX Orin reflash	14	2089	January 16, 2024
Error: missing dtbfile Jetson AGX Orin boot , kernel , ubuntu	35	3685	September 8, 2022
SDKMagager1.9.0 flash Jetson AGX Orin completed But the screen is black Jetson AGX Orin sdkm	24	1936	December 12, 2022
What is the difference between P3701-0000 and P3701-0004? Jetson AGX Orin hw	5	1524	March 28, 2024
NVIDIA Jetson Linux 35.4.1 Customization failure Jetson AGX Orin	23	2290	September 13, 2023
Flashing R35.4.1 to AGX Orin Crashes Jetson AGX Orin flash , jetson-orin	10	265	November 21, 2025

Difference between p3701-0000 and p3701-0005 SOM Board

Related topics