Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY=“” /home/trident/Downloads/r36_3_0/Linux_for_Tegra/flash.sh --no-flash --sign -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY=“” /home/trident/Downloads/r36_3_0/Linux_for_Tegra/flash.sh --no-flash --sign -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
We dont have devkit.I doubt SOM is the issue here.
Just to inform about the background of this issue:
This error did not occur initially and we were able to proceed successfully with the first half of the flashing process.
flashing failed in the second half, "waiting for the target to reboot… " - we observed the the uart console log and saw it was error related to eeprom size to be set to “0” as ours it customized carrier board.
We updated this fix and built the dtb files and tried flashing again.
that time we are getting this error…
note, FYI:
when we do lsusb, we can observer “nvidia corp…”
I have updated my device tree also to support micro usb type b for usb2.0 - port 0 used for flashing accordingly.
Sounds like a hardware issue.
If it also cannot be flashed with a DevKit, then clearly the module itself is broken.
If it can, then there’s some issue with your board that the EEPROM on the module cannot be accessed.
How many Jetson modules do you have on your side? If no devkit can try here, then should do cross check with other modules and see if all modules have problem or only one.
In this readme file the command for flashing is bit different( last parameter is external in one place and internal in another place):
Please explain this discrepancy with the command provided in the website:
For a device with internal QSPI and external NVMe:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml
-p “-c bootloader/generic/cfg/flash_t234_qspi.xml --no-systemimg” --network usb0
external
but again, we are getting the some eeprom slave related error as per the uart serial log in the middle of flashing, which says “waiting for unit to reboot…”
[ 0.0555 ] Sending mb1
[ 0.0559 ] Sending psc_bl1
[ 0.0656 ] Sending bct_mb1
[ 0.0710 ] Generating blob for T23x
[ 0.0732 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[ 0.0740 ] The number of images in blob is 19
[ 0.0743 ] blobsize is 96368595
[ 0.0743 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 3563584
[ 0.1156 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 310768
[ 0.1162 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 187120
[ 0.1164 ] Added binary blob_tsec_t234_sigheader.bin.encrypt of size 176128
[ 0.1166 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 279616
[ 0.1168 ] Not supported type: mb2_applet
[ 0.1168 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 439968
[ 0.1171 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[ 0.1173 ] Added binary blob_nvpva_020_sigheader.fw.encrypt of size 2164640
[ 0.1179 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 12065344
[ 0.1248 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 0.1270 ] Added binary blob_bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt of size 1027008
[ 0.1276 ] Added binary blob_tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt of size 383232
[ 0.1279 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 458096
[ 0.1281 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 414960
[ 0.1282 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 0.1284 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1633344
[ 0.1289 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 0.1291 ] Added binary blob_boot0.img of size 72280064
[ 0.1713 ] Added binary blob_tegra234-p3768-0000+p3767-0000-nv.dtb of size 244275
[ 0.2438 ] tegrarcm_v2 --instance 1-5 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.2446 ] BL: version 1.4.0.2-t234-54845784-08a4de08 last_boot_error: 0
[ 0.3324 ] Sending bct_mem
[ 0.3561 ] Sending blob
[ 3.7248 ] RCM-boot started
/home/trident/Downloads/r36_3_0/Linux_for_Tegra
*
Step 3: Start the flashing process *
*
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 target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Timeout
Device failed to boot to the initrd flash kernel. Please retrive the serial log during flashing to debug further.
Cleaning up…
You should just follow moderators suggestion. Most of your trying are just creating unrelated erros. Honestly, this is your own time that got wasted if you are always not able to understand the order and suggestions…
We only suggested
Do crosscheck with all the modules to clarify if this is hardware issue
If you want to hardcoded the value to flash script, then the readme file has the SOM info. We only want you to read this. But not randomly pick any command from readme file.
/home/trident/Downloads/r36_3_0/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
Export list for localhost:
/home/trident/Downloads/r36_3_0/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1
Better delete everything and start over again.
Or delete the copy of that file under Linux_for_Tegra/bootloader/.
Once a copy is generated, the flashing script uses that copy instead of the original file.
