Part number confusion with Jetson Nano and

I’m writing a script to help customise nano system images, and I want to make sure I’m getting the part numbers correct so it runs with the correct parameters.

SDKM lists “P3448-0000” for my development board. I assume “P3448-0020” is the production module based on the SDKM dropdown. My question is how these map to the parameters “” expects. That script has this:

case "${rev}" in
		usage "Incorrect Revision - Supported revisions - 100, 200, 300"

I assume 100 (a01) and 200 (a02) map to P3448-0000 and 300 (b00) maps to P3448-0020, however later on in the script, the value for dtb_id is hard-coded, overriding this choice.

line 246:


Is this a mistake or do I simply not need to worry about what value is specified since a02 will always work, on both development and production modules? I’ve used a02 in the past to make sd card images that work on my board but don’t have a production module to test with. Are SD card images always compatible?

Lastly, I’m a bit confused as to what these part numbers mean since they don’t seem to be used anywhere else but are referred to as a “complete list of part numbers” on this page. Do Jetsons have two sets of part numbers, and if so, is there a mapping somewhere between them?


Sorry for late reply.

B0x images will work on A02 boards without issue. There are some pinmux differences between the two hardware revisions, but the B0x pinmux settings will work fine on an A02 board.

However, A0x pinmux (dtb) does not work on B0x board.

Thanks for the reply,

If I understand you correctly, cannot be used to create images for the production module? I should use instead?

Yes, production module does not have a sdcard slot so that it is pointless to use sdcard image on it.

I see. Thank you for the clarification. I was confused because the “b00” dtb id was in the SD card script’s options. I don’t have a production module and assumed it did have a card slot by the content of the script and some of the functions (signed image support, comments, etc.). I will ignore production module support for what I am developing until I read more about its flashing procedure. I assume it’s closer to flashing a Xavier, which I have and will be the next for support.

mdegans, Wayne answered your exact question about sd card image creation script and production module… but note a future revision of the developer kit will ship with a module having PCB revision B01. So, it is relevant for sd card image creation script to generate B0x sd card images. In fact, the sd card image we host for download is already a B01 sd card image, and everyone is using it in their devkits wit A02 module.

Does that clarify things? The production module has had PCB revision B01 from the beginning, and the devkit will move to using that same module PCB revision in the future (while still having microSD card instead of eMMC, etc.)

Basically, everyone should be using B0x options for everything, since it works with A02 modules and of course will work for any B0x modules.

Mostly. I apologise if I have been unclear. Anyway it is not very important. I have figured out what P344* model number maps to which appropriate options and will pass them in anyway. I have what I need for the utility i’m working on.

Hi Wayne
If I think properly, the 260 pin definition in A02 board is different with B01?
I design my own carrier board referred to Jetson_Nano_Product_Design_Guide, it works well if I insert B01 into it and works bad if A02 inserted?

Yes, they’re different, the board design file is for B01 module, it’s not compatible with A02 module.

In terms of the A02 and B01 carrier board, what I found from the following links, the SODIMM pinout for the A02 and B01 Jetson Nano modules look the same. Posted 06/13/2019 03:50 AM

Jetson Download Center | NVIDIA Developer Jetson Nano Module Data Sheet 1.0 2020/02/12

Except from the second camera CSI-2 connector and several other connectors placement changes, I can’t really tell what’s the key differents from the two modules.

Thanks in advance.

more specific :

Not sure about this carrier board version, only one camera connector, assuming it is A02

B02 carrier board schematic.

1 Like

@ Kayccc
Any chance to have a look at this question?


The pinout differs between B01 modules and A02 devkit module.

By the way, it is best if you look at latest collateral available from Jetson Download Center, e.g. Jetson Nano Developer Kit Carrier Board Design Files.

how to flash B01 board with module from nano A02 devkit via headless sdkmanager?
which target to specify?
I can not flash the board neither with sdkmanager gui, nor with the command below:

sudo sdkmanager --cli install --user --logintype devzone --product Jetson --version DP_4.4 --targetos Linux --target P3668-0000 --flash all --targetimagefolder /home/user/Downloads/nvidia/installation_nano/  --downloadfolder /home/user/Downloads/nvidia

;However I have still have a chacne to flash recovering from sdcard image
Which image? this image ?

Looking at this I see some things about a b0x image being compatible with a02, however in our testing that has not been the case on a custom carrier board.

Our build DOES work on a B00 we believe. We want to know if there is any reason it could not work on a B01?

Also, on a running system, from Tegra Linux, how do we check the exact processor version running? The results from running sudo i2cdump -f -y 2 0x50 do not give me an indication, that gives p3448-0000-400.

Hi john.leggert,

Please help to open a new topic for your issue. Thanks