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?
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)
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.