How should I get the board version?

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hi All,

why I can’t get the board version by the script from topic “https://devtalk.nvidia.com/default/topic/1064080/jetson-tx2/secure-boot-odmfuse-programming-step-fail-on-32-2-1/1”?

garret:~/tx2/l4t32.2$ sudo ./flash.sh --no-flash -r jetson-tx2 mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 2.1
###############################################################################
Board ID() version() sku() revision()
copying bctfile(/home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/t186ref/BCT/P3310_A00_8GB_Samsung_8GB_lpddr4_204Mhz_A02_l4t.cfg)... done.
copying misc_config(/home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/t186ref/BCT/tegra186-mb1-bct-misc-si-l4t.cfg)... done.
copying pinmux_config(/home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/t186ref/BCT/tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg)... done.
...
Existing flasher(/home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/nvtboot_recovery_cpu.bin) reused.
Existing flashapp(/home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/tegraflash.py) reused.
./tegraflash.py --bl nvtboot_recovery_cpu.bin --sdram_config P3310_A00_8GB_Samsung_8GB_lpddr4_204Mhz_A02_l4t.cfg --odmdata 0x1090000 --applet mb1_recovery_prod.bin --cmd "flash; reboot"  --cfg flash.xml --chip 0x18 --misc_config tegra186-mb1-bct-misc-si-l4t.cfg --pinmux_config tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg --pmic_config tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg --pmc_config tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg --prod_config tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg --scr_config minimal_scr.cfg --scr_cold_boot_config mobile_scr.cfg --br_cmd_config tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg --dev_params emmc.cfg  --bins "mb2_bootloader nvtboot_recovery.bin; mts_preboot preboot_d15_prod_cr.bin; mts_bootpack mce_mts_d15_prod_cr.bin; bpmp_fw bpmp.bin; bpmp_fw_dtb tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb; tlk tos-trusty.img; eks eks.img; bootloader_dtb tegra186-quill-p3310-1000-c03-00-base.dtb" --skipuid  
saving flash command in /home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/flashcmd.txt
saving Windows flash command to /home/garret/nvidia/nvidia_sdk/JetPack_4.2.2_Linux_GA_P3310/Linux_for_Tegra/bootloader/flash_win.bat
*** no-flash flag enabled. Exiting now... ***
2

hello garretzou,

could you please have confirmation by removing --no-flash, it should parse the board information correctly.

I’ve quick check with the latest L4T release on Jetson-TX2, it shows board information even with no-flash options.
for example,

$ sudo ./flash.sh -r --no-flash jetson-tx2 mmcblk0p1
...
Board ID(3310) version(B00) sku(1000) revision(E.0)
3

I found the logs generated when flashing my target tx2 devKit with or without --no-flash option all show board version.

“Board ID(3310) version(B02) sku(1000) revision(E.0)”

Don’t know why.

4

hello garretzou,

did this empty board info only occur for the 1st time?
you may have double confirmation and please also narrow down the steps which reproduce the failure.
thanks

5

Dear JerryChang,

Thanks

Don’t care it.

The logs mentioned above were save several days ago. Here I just try the script “sudo ./flash.sh --no-flash -r jetson-tx2 mmcblk0p1” cause I have not used the “–no-flash” and “-r” options simultaneously.

Maybe I use it on a whole new l4t package.

6

Dear JerryChang,

Sorry for my fault.

Cause I not connect the board, so the board version didn’t show. After I connect the board in RCM, it works.

7

Hi JerryChang,

I found that the jetson tx2 develop user guide marks "developer kit carrier board (revisions B02 and B04) and “developer kit carrier board (revision C02) in page 5.”
But here “Board ID(3310) version(B02) sku(1000) revision(E.0)” show B02 is verison.
Does the version indicate carrier board version, and what is the reversion?

I also confused about jetson-nano-emmc, jetson-nano-sd and jetson-nano-qspi-sd, what the below script I should use when I install a official nano module on a nano devKit carrier board?

sudo ./flash.sh -r jetson-nano-emmc mmcblk0p1
sudo ./flash.sh -r jetson-nano-sd mmcblk0p1
sudo ./flash.sh -r jetson-nano-qspi-sd mmcblk0p1

"
And I get the board version with the “sudo ./flash.sh -r --no-flash jetson-nano-qspi-sd mmcblk0p1” script as below,

Board ID(3448) version(200)

We have several the above nano dev kit in hand, we want install the official Nano module on the these carrier board.

8

hello garretzou,

you may dump the serial number from the eeprom,
for example.

$ sudo i2cdump -f -y 2 0x50

please also check Jetson Module EEPROM Layout for reference,
you should also refer to Jetson FAQ for the Jetson family part numbers.
thanks