1, I got the BOARDID=3767 BOARDSKU=0001 FAB=300 BOARDREV=N.2 CHIP_SKU=“00:00:00:D4” RAMCODE_ID=“00:00:00:02” info, so I use command to prepare the env.
2, I use “sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --showlogs --network usb0 --massflash 5 --keep” to flashing the multiple device after setup the multiple devices to recovery mode.
3, Then the error hanppened. It can not starting to create gpt for emmc.
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for device to expose ssh …RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh …Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 76
max_index=75
writing item=59, 6:0:primary_gpt, 512, 19968, gpt_primary_6_0.bin, 16896, fixed--0, bdf464b9652e71d85739f5896c51dfadb1d0f708
Flash failure
Cleaning up…
Keeping working dir at /home/hengyongchao/NVIDIA/jetson-linux_flash/jetson_linux_35.4.1/Linux_for_Tegra/temp_initrdflash/bootloader0 and /tmp/tmp.SQ8LAwr1iD
If a device is connected to your host PC when you generate the flashing package, then these information are not needed; they will be read directly from the device. That may be why flashing directly with initrd flash without massflash works, because these hardware config on your device may differ slightly from the sample we provide.
What’s the root cause of this? left side is mass flash log, the right side is sigle flash. I test it with one orin nx 8gb device pluged in to be flashed.
I want to know why there is an internal difference between the process of flash one unit individually and flash multiple devices? Why can the same device be flashed individually under different commands, but flash multiple device always fails?
What are the correct commands and procedures for mass flash orin nx? please help to fix this issues, we have 200 orin nx devices need to be programmed. It’s urgent!
About our customized development board, It does not have EEPROM, and the USB burning port integrates the HUB function. After using command 2, it will wait until timeout.
According to my understanding.
The first step is to collect the current development board configuration and package them into a burning package.
Step 2: Copy the programming package to multiple development boards connected later.
So, the above content page contains the configuration information of the hardware. If the hardware is somewhat different (such as development board and custom board), will the burning process fail?
How can I do this:
Step 1: flash the customized development board separately and configure some software environments and software. Then package it into a flash package（restores package）.
Step 2: Flash the previous installation packages to multiple connected customized boards.
Question:
What the commands the above steps one and two are?
What is the difference between restoring the installation package and the previous mass flash script processing?
If you are sure it’s Orin NX 8GB, the looks like somehow the wrong dtb file is being used:
[ 0.1494 ] Added binary blob_tegra234-p3767-0000-p3768-0000-a0.dtb of size 343953
p3767-0000 means Orin NX 16GB, and it would be p3767-0001 for Orin NX 8GB.
Did you generate the flashing package with devices connected, so it reads the wright hardware info?
