What are the differences in boot partitions between manual flash and OTA update?

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

Hi all,

We have a custom board based on AGX Orin running JetPack 5.1.4 with RootFS_AB enabled and I am testing OTA updates to JetPack 6.1.

The OTA procedure seems to work, the system is able to perform the OTA to update the rootfs and bootloader, the board boots in JetPack 6.1, however, the displays doesn’t work.

So. I reach the point were the system is running in JetPack6 but the displays doesn’t, there is not specific error on the dmesg neither.

At this point, I used the JetPack6.1 build to only flash bootloader files and the system booted correctly using the same rootfs.

My conclusion is that there are some bootloader partitions that are not being updated by the OTA process that they are indeed updated by the flash script, so I wanted to ask a couple of questions:

  • Is there a list of boot partitions that are being skipped by the OTA procedure?
  • Is this a OTA limitation for JP5 to JP6 updates?

I am not sure which OTA partition is doing the trick but any information will be appreciated.

Thanks.

3

Hi greivin.fallas,

You may perform the OTA update process 2 times to update both A/B slots.

Do you mean the display gets working after you used the Jetpack 6.1 package(same as the one you generate OTA payload) to flash bootloader?

You can check the log when you were generating the OTA payload and also the log during OTA update for them.
Please check the flash.idx for the partitions updated for external device.
For internal QSPI, it does the similar process as capsule update. (TEGRA_BL.Cap)

5

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