Hi!
I encountered 2 issues when using Image Based OTA to burn the AGX Xavier
Firstly, I update from R35.1.0（JetPack5.0.2）to R35.2.1（JetPack5.1） execute the command:
“sudo ./tools/ota_tools/version_upgrade/build_base_recovery_image.sh jetson-agx-xavier-devkit R35-1 ${BASE_BSP} ${BASE_BSP}/rootfs ${TARGET_BSP}”
but there was an issue:
"Target board(JETSON_XAVIER_NX_DEVKIT) and base version(R35_1) is not supported
Failed to run “ota_validate_params jetson-agx-xavier-devkit R35-1 internal /home/mch/tmpL4T/r35.2.1/Linux_for_Tegra/tools/ota_tools/version_upgrade/ota_board_specs.conf BOARD_SPECS_ARRAY CHIPID”
Then try updating from R32.4.2（JetPack4.4）to R32.6.1（JetPack4.6） and generate the OTA Payload package on my host PC.
When I execute commands on the AGX Xavier
“sudo ./nv_ota_start.sh /dev/mmcblk0 /home/nvidia/ota/ota_payload_package.tar.gz” or “sudo ./nv_ota_start.sh /dev/mmcblk0p1 /home/nvidia/ota/ota_payload_package.tar.gz”
but the device is down and cannot be up.
The log is as follows：
OTA log
OTA_LOG_FILE=/ota_log/ota_20180129-000348.log
update_nv_boot_control_in_rootfs /ota_work
check_prerequisites
get_chip_id chip_id
nv_ota_update_without_layout_change.sh /ota_work/ota_package.tar.gz
Command: nv_ota_update_without_layout_change.sh /ota_work/ota_package.tar.gz
decompress_ota_package /ota_work/ota_package.tar.gz /ota_work
decompress_ota_package: start at Mon Jan 29 00:04:02 CST 2018
Sha1 checksum for /ota_work/ota_package.tar (da857161956c959471e0e24da3456a96c70a303a) matches
decompress_ota_package: end at Mon Jan 29 00:04:31 CST 2018
check_target_board /ota_work TARGET_BOARD
get_chip_id CHIP_ID
update_utilities_for_BUP_update /ota_work
enable_a_b_redundancy
get_rootfs_a_b_enabled ROOTFS_AB_ENABLED UNIFIED_AB_ENABLED
ROOTFS_AB_ENABLED=0
UNIFIED_AB_ENABLED=0
check_bsp_version /ota_work BASE_VERSION
get_update_control /ota_work UPDATE_BOOTLOADER UPDATE_ROOTFS
UPDATE_BOOTLOADER=1, UPDATE_ROOTFS=1
update_bootloader /ota_work 0 0x19
get_update_slot bootloader 0 update_slot
update_slot=B
update_bootloader_with_UE /ota_work 0x19
Copy /opt/ota_package/entry_table into /ota_work/entry_table.ota_backup
Bootloader on non-current slot(B) is updated
update_rootfs /ota_work 0
update_rootfs_with_a_b_disabled /ota_work
write_base_recovery /ota_work
Verifying image /ota_work/recovery.img.R32_3_4 with sha1 chksum file /ota_work/recovery.img.R32_3_4.sha1sum
Sha1 checksum for /ota_work/recovery.img.R32_3_4 (554bf2912b1a5aae5b7e56a225c846ca4f3fe5e6) matches
Verifying image /ota_work/recovery.dtb.R32_3_4 with sha1 chksum file /ota_work/recovery.dtb.R32_3_4.sha1sum
Sha1 checksum for /ota_work/recovery.dtb.R32_3_4 (074c63453a43897dba18cd774d91a94eb0645bd5) matches
Backed up kernel and kernel-dtb partition under /ota_work before writing them
Writing base recovery image into /dev/disk/by-partlabel/recovery
Read back base recovery image into /ota_work/image.tmp and verify it
Reading 47792128 bytes from /dev/disk/by-partlabel/recovery: 1KB block=46672 remainder=0 offset=47792128
Verifying image /ota_work/image.tmp with sha1 chksum file /ota_work/recovery.img.R32_3_4.sha1sum
Sha1 checksum for /ota_work/image.tmp (554bf2912b1a5aae5b7e56a225c846ca4f3fe5e6) matches
Writing base recovery dtb into /dev/disk/by-partlabel/recovery-dtb
Read back base recovery dtb into /ota_work/image.tmp and verify it
Reading 280256 bytes from /dev/disk/by-partlabel/recovery-dtb: 1KB block=273 remainder=704 offset=279552
Verifying image /ota_work/image.tmp with sha1 chksum file /ota_work/recovery.dtb.R32_3_4.sha1sum
Sha1 checksum for /ota_work/image.tmp (074c63453a43897dba18cd774d91a94eb0645bd5) matches
write_kernel_bootctrl /ota_work images-R32-ToT
Backed up kernel-bootctrl partition under /ota_work before writing them
Writing bootctrl update file into /dev/disk/by-partlabel/kernel-bootctrl
Read back bootctrl update file into /ota_work/image.tmp and verify it
Reading 20 bytes from /dev/disk/by-partlabel/kernel-bootctrl: 1KB block=0 remainder=20 offset=0
backup_extlinux_conf /ota_work
Backing up /boot/extlinux/extlinux.conf
Rootfs is to be updated in recovery kernel once device is rebooted.
Finally, I hope you can guide me to solve it. Thank you
Hi 1131020145,
Are you using the devkit or custom board for AGX Xavier?
Could you use R35-1 instead of R35_1 for <bsp_version>?
So, what is your BASE_BSP and TARGET_BSP?
(R35.1 → R35.2.1 Or R32.4.2 to R32.6.1)?
I should use devkit for XGA Xavier
Official post introducing using ‘Rmm-n’.I used ‘R35-1’ and ‘R35_1’ failed
BASE_BSP TARGET_BSP(ToT_BSP)
R35.1 → R35.2.1
R32.4.2 → R35.6.1
Thanks
I tried “R32.7.1(4.6.1)/R32.7.2(4.6.2) → R35.2.1(5.1)”
When I execute command in my host PC：
sudo -E ./…/l4t…sh
but it failed. it always “make img…”
it not generate OTA Payload package
Could you share the full commands you use and the flash log on your terminal for further check?
The full commands：“sudo -E ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh jetson-agx-xavier-devkit R32-7”
sorry,I forgot to save the flash log，but when flashing, my host repeatedly prints content："Making system.img…
Setting “FDT /boot/dtb/kernel_tegra194-p2888-0001-p2822-0000.dtb” successfully in the extlinux.conf…done.
populating rootfs from /home/mch/tmpL4T/r35.2.1/Linux_for_Tegra/rootfs … "
This would take some time in this step.
Could you run it again and share the full flash log for further check?
For R32.7.1(4.6.1)/R32.7.2(4.6.2) → R35.2.1(5.1),I execute command in my host PC:“sudo -E ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh jetson-agx-xavier-devkit R32-7”
When creating OTA payload packages on my host, the host screen cycles and prints the following content every few minutes:"Making system.img…
Setting “FDT /boot/dtb/kernel_tegra194-p2888-0001-p2822-0000.dtb” successfully in the extlinux.conf…done.
populating rootfs from /home/mch/tmpL4T/r35.2.1/Linux_for_Tegra/rootfs … ", and I don’t know where the corresponding log is at this time
Then I waited for it to print four or five times, and before I finished making the OTA payload package, I manually canceled and stopped the production
At this time, I haven’t burned the log on the device yet
The good news is that the second issue in this topic has been resolved.I successfully upgraded from R32.4.2（JetPack4.4）to R32.6.1（JetPack4.6）.
So,The only issue with this is updating from R32.7.1 → R35.2.1. Why does the host print “Making system.img…” every few minutes when creating load packages
How long did you wait for it?
Could you share the full flash log from your host?
It may have taken 1 hour to manually stop and end.
Execute 2 commands on my host.
Order 1
sudo ./tools/ota_tools/version_upgrade/build_base_recovery_image.sh jetson-agx-xavier-devkit R32-7 ${BASE_BSP} ${BASE_BSP}/rootfs ${TARGET_BSP}
The printed content of the host can be found in Order-1.log
Order-1.log (122.4 KB)
Order 2
sudo -E ./tools/ota_tools/version_upgrade/l4t_generate_ota_package.sh jetson-agx-xavier-devkit R32-7
The printed content of the host can be found in Order-2.log
Order-2.log (325.3 KB)
From your Order-2.log, it seems you are generating the system.img repeatly.
Line 75: Making system.img...
Line 2233: Making system.img...
Line 4391: Making system.img...
Could you help to check why it flash multiple times?
Sorry, I do not konw
I only executed command 2 once, and during nearly an hour of waiting, I found that it was repeatedly creating a mirror image
After following the instructions on the official website, I didn’t know why it was Wae Ireoni?, so I came to ask
Sorry, I made an editing error. Don’t worry about “Wae Ireoni”
I don’t know why it flashes multiple times, so I’m asking
Could you help to verify the image-based OTA from R32.7.1 to R35.4.1 for AGX Xavier?
I have tried upgrading from ‘R32.7.1’ to ‘R35.4.1’, but it still doesn’t work. Please refer to “3541. log” for the printed content
3541.log (166.5 KB)
It seems the log when you generate the OTA package from your host.
Does it stuck at the following line to generate rootfs?
Making system.img...
Setting "FDT /boot/dtb/kernel_tegra194-p2888-0001-p2822-0000.dtb" successfully in the extlinux.conf...done.
populating rootfs from /home/mch/tmpL4T/r35.4.1/Linux_for_Tegra/rootfs ...
Do you run step6 in this instruction before run your command in that log to generate OTA package?
It did not stop to generate rootfs
My command to execute step 6 is “sudo ./tools/ota_tools/version_upgrade/build_base_recovery_image.sh jetson-agx-xavier-devkit R32-7 ${BASE_BSP} ${BASE_BSP}/rootfs ${TARGET_BSP}”
Do you have any custom modification in rootfs of R35.4.1 BSP package?