I am attempting to perform an image based OTA upgrade from 32.7 to 35.1 on a non-dev Xavier AGX remotely.
I have access to a jetson on hand which has been flashed to be in the same state as our remote units (R32.7) on the nvme drive including some customization the to rootfs from our supplier for testing that the update works before I push to our remote units which are only accessible via ssh.
When I reboot the recovery image is never loaded and it boots straight into R32.7 running on the nvme and there is no log found in ota_logs.
I have tested with the nvme removed from the jetson and the ota_payload_package works(ie updates to the version in the ota update) if the jetson is running on the emmc storage but is unable to be flashed if it was originally flashed to the nvme using SDK manager.
I am happy to switch to emmc rootfs or have the nvme be OTA updated although it looks like thats only supported on the nx modules at this time.
Is there any way to get this to work ie changing from nvme to emmc as the default rootfs after flashing or flash to the nvme itself without having physical access to the device.
When flashing I notice that the ./nv_ota_start.sh moves the extlinux.conf file from /boot so im curious as to how it knows to boot into the recovery partition.
It seems your OTA package is generated for internal eMMC.
Could you share the command you used to generate OTA package?
I would like to check the serial console log rather than dmesg.
For serial console log from the devkit, you could refer to the following instruction. NVIDIA Jetson Xavier - Serial Console (ridgerun.com)
For your custom carrier board, you should check where is the debug UART.
Theres no instructions for generating OTA package for NVME on the AGX hence why I did EMMC is there a way to generate for NVME that I am missing?
I am unable to get any serial logs while the device is booting via the USB or via the uart connection (Via a known working serial converter) it may be something to do with the carrier board
Since it reboots just as fast as before initiating the ota update I feel its not even attempting to do any boot up sequence. Is there a different way to get the boot logs or a setting I need to change on the jetson itself?
Sorry should have specified before I ran the command I did
so it is definitely running in the correct path as I didn’t copy the build tools into the Jetpack_4.6… path.
Is there an ETA on the next release to support image-based OTA for NVMe on the AGX?
The uart console log is not working as directed on the documentation from our carrier board supplier we are in comms with them about it.
For now is there any way for me force the jetson to ignore the nvme on boot so that the jetson uses what is written onto the emmc by the sudo ./nv_ota_start.sh /ota/ota_payload_package.tar.gz command? Or any changes I can make to the command to do this?
The board flashes correctly if I remove the NVMe drive from carrier board
Can you please verify the steps
Flash board to NVME via SDK manager.
Follow steps to create ota_image for EMMC
Follow steps to start ota on the jetson which has been flashed to NVMe
Reboot and send what the logs should look like?
For the devkit, you could refer to the following steps to capture serial console log. NVIDIA Jetson Xavier - Serial Console (ridgerun.com)
For the custom carrier board, please check with your vendor.
Is this board designed by you? If so, please check with HW team.
I would suggest verifying updating eMMC first. (you could boot from eMMC but mount NVMe as rootfs)
I have verified that the ota update package works if the nvme is disconnected the issue is when the nvme is connected it automatically boots from that and since our remote units are all flashed to the NVMe we are unable to use the OTA update because we cannot physically disconnect the nvme is there any work around like tellings the nvme kernel to boot from the emmc instead?
All this says is that I need to enter the UEFI menu to change the boot order which requires connecting to the uart and physical access to the device I assumed the whole point of OTA update was so that the update can be performed “Over the air” ie without physical access.
Is there a way to initialise a OTA update on a device that is running on NVMe and tell it on next boot to boot from the emmc?
Alternatively what is the reason AGX doesn’t support flashing to emmc? Can I use the same partitions as the nx module?
Those instruction say “Flash the device” as the last step this is not helpful when I cannot physically access the device. Am I correct in saying that the R32.7 does not use UEFI boot and is using CBoot? So these instructions are only good for R35.1
So is there documentation for getting it to boot from emmc when the current version is R32.7 SO that it can start using R35.1. I feel the documentation you sent is only useful if the device has been updated which is what I am asking you for help with.
Yes this is what I did there is no instructions for the target version OTA package generation for a device that is already running on NVMe can you please help with this?
So you are saying there is no current solution to this problem? We have to wait for nvidia to release the update THEN our supplier to update the customised packages this could be months without being able to update our devices.
Am I able to check this somehow? Do the logs that I generated show this information?