JP 6.0 AGX ORIN flash failed

Dear nvidia team:
Below is flash error due to the absence of tegra234-p3701-overlay.dtbo config file.I can find tegra234-p3701-overlay.dtbo file on JP 5.1.1.But I can’t find it in JP 6.0.How to fix it?

OVERLAY_DTB_FILE=“L4TConfiguration.dtbo,tegra234-p3701-overlay.dtbo”;

[ 0.0161 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0162 ] Assuming zero filled SBK key
[ 0.0151 ] Parsing partition layout
[ 0.0177 ] tegraparser_v2 --pt flash.xml.tmp
[ 0.0267 ] Change tegra234-bpmp-3701-0004-3737-0000.dtb to tegra234-bpmp-3701-0004-3737-0000_with_odm.dtb
[ 0.0267 ] Change tegra234-bpmp-3701-0004-3737-0000.dtb to tegra234-bpmp-3701-0004-3737-0000_with_odm.dtb
[ 0.0713 ] /usr/bin/python3 dtbcheck.py -c t234 -o tegra234-bpmp-3701-0004-3737-0000_with_odm.dtb tegra234-bpmp-3701-0004-3737-0000_with_odm_tmp.dtb
[ 0.2440 ] Concatenating L4TConfiguration.dtbo,tegra234-p3701-overlay.dtbo to tegra234-p3737-0000+p3701-0004-nv_with_odm_overlay.dtb.updated
Traceback (most recent call last):
File “./tegraflash.py”, line 1456, in
tegraflash_run_commands()
File “./tegraflash.py”, line 1276, in tegraflash_run_commands
interpreter.onecmd(command)
File “/usr/lib/python3.8/cmd.py”, line 217, in onecmd
return func(arg)
File “./tegraflash.py”, line 289, in do_flash
self.chip_inst.tegraflash_flash(exports)
File “/home/lcfc/nvidia_B600/JetPack_6.0_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py”, line 972, in tegraflash_flash
self.tegraflash_parse_partitionlayout()
File “/home/lcfc/nvidia_B600/JetPack_6.0_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py”, line 495, in tegraflash_parse_partitionlayout
tegraflash_concat_overlay_dtb()
File “/home/lcfc/nvidia_B600/JetPack_6.0_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py”, line 4572, in tegraflash_concat_overlay_dtb
values[‘–bldtb’] = concat_file_4k(cpubl_dtb, dtb_files)
File “/home/lcfc/nvidia_B600/JetPack_6.0_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/bootloader/tegraflash_internal.py”, line 4557, in concat_file_4k
with open(infilename, ‘rb’) as infile:
FileNotFoundError: [Errno 2] No such file or directory: ‘tegra234-p3701-overlay.dtbo’
Failed flashing generic.

Hi,
Please check the quick start in developer guide and make sure you follow the steps one by one:
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/IN/QuickStart.html
If the device still cannot be flashed/booted, please refer to the page to get uart log from the device:
https://elinux.org/Jetson/General_debug
If you are using custom board, you can compare uart log of developer kit and custom board to get more information.

Thanks!

Hi 592803276,

Are you using the devkit or custom board for AGX Orin?

JP5 and JP6 have different SW stack for DTB handling.
There may be no tegra234-p3701-overlay.dtbo in JP6 as expected.

What do you want to configure in device tree?

Dear KevinFFF:

I am using our custom board for AGX Orin.I don’t know how to modify the OVERLAY_DTB_FILE configuration file for JP 6.0 32G SKU( DTB_FILE=tegra234-p3737-0000+p3701-0004-nv.dtb) now.
Our carrier customer board can’t enter the desktop if I replace OVERLAY_DTB_FILE=“L4TConfiguration.dtbo,tegra234-p3701-overlay.dtbo” configuration by OVERLAY_DTB_FILE=“L4TConfiguration.dtbo”.
Our carrier customer board can enter desktop if I use the default configuration below in p3737-0000-p3701-0000.conf:
OVERLAY_DTB_FILE=“L4TConfiguration.dtbo,tegra234-p3737-0000+p3701-0000-dynamic.dtbo,tegra234-carveouts.dtbo,tegra-optee.dtbo,tegra234-p3737-camera-dual-imx274-overlay.dtbo,tegra234-p3737-camera-e3331-overlay.dtbo,tegra234-p3737-camera-e3333-overlay.dtbo,tegra234-p3737-camera-imx185-overlay.dtbo”;

When the device is finished flashing I reboot it and it eventually gets stuck. It can’t enter desktop and I see on screen :

[***  ] A start job is running for Wait until snapd is fully seeded (10min 7s / no limit)

image

I would suggest you using the default configurations with your customization in any dtbo.

Could you share the /boot/extlinux/extlinux.conf from your board?

Please provide the full serial console log for boot issue.

I have uploaded the serial port log. Please help me to check.
serial_log.txt (74.3 KB)
Thanks
The log “A start job is running for Wait until snapd is fully seeded” always be displayed on the screen after flashing it when you reboot at the first time. If you reboot next time, it will disappear.What’s the reason?Is there any influence?

From the log you shared, it seems you can boot up the board now.

In your screenshot, it seems there’s the issue about your USB device mode.
I’m not sure if it is specific to your custom carrier board since I don’t see that issue on the devkit.

Dear KevinFFF:
Please helpe me to see the topic “JP 6.0 mass flash takes a long time”
Thanks

updated.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.