Can not boot after Capsule Update

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

Hello NVIDIA experts,

I have a custom industrial Orin (r36.3) board. After attempting a Capsule Update, the device failed to boot properly and Cannot enter UEFI menu either. The UEFI version timestamp shows that the update was successful, but during boot I encountered the following error:

FATAL ERROR [FILE=platform/drivers/thermal/bjt/soctherm-cal.c, ERR_UID=2053]: 
BPMP-DTB property ‘/soctherm/thermtrip_hot’ above maximum permitted (118000 > 105000)


▒▒ERROR: camera-ip/isp5/isp5.c:2031 [isp5_pm_init] "ERROR: Failed to turn isp1 power on"
BUG: core/init/init.c:86 [init_all] "*** FIRMWARE INIT FAILED AT LEVEL 95 ***"

The full boot log is attached below. Could you please help analyze what might be causing this issue?

log.txt (202.1 KB)

2

My procedure is as follows:


sudo FAB=000 BOARDID=3701 FUSELEVEL=fuselevel_production BOARDSKU=0008 ./build_l4t_bup.sh jetson-agx-orin-devkit-industrial mmcblk0p1

./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_BL.Cap t234

nv_bootloader_capsule_updater.sh -q /root/TEGRA_BL.Cap t234
3

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing a boot issue with your custom industrial Orin r363 board after attempting a Capsule Update. The UEFI version timestamp indicates that the update was successful, but the device failed to boot properly, resulting in an error.

To analyze this issue, let’s break down the key points:

  1. Capsule Update: The update process involves updating the KEK, db, and dbx keys, which are used for UEFI Secure Boot. The update process seems to have completed successfully, as indicated by the UEFI version timestamp.
  2. Boot failure: Despite the successful update, the device failed to boot properly, resulting in an error. This suggests that there might be an issue with the boot process or the updated keys.
  3. Error log: The attached log file (log.txt) contains the full boot log, which might provide more information about the error.

To help you analyze the issue, I’ll provide some general guidance and potential causes:

  • UEFI Secure Boot: Ensure that UEFI Secure Boot is enabled and set to UEFI mode. Also, verify that the updated KEK, db, and dbx keys are correctly configured.
  • Boot partition: Check if the boot partition is correctly configured and if the updated keys are properly applied to the boot partition.
  • Kernel or driver issues: It’s possible that there’s an issue with the kernel or drivers that’s preventing the device from booting properly.
  • Hardware compatibility: Verify that the custom industrial Orin r363 board is compatible with the updated UEFI and boot process.

To further assist you, I recommend:

  • Checking the boot log: Analyze the attached log file (log.txt) to identify any specific error messages or clues that might indicate the cause of the issue.
  • Verifying UEFI settings: Double-check the UEFI settings to ensure that Secure Boot is enabled and set to UEFI mode.
  • Updating the boot partition: Try updating the boot partition again to ensure that the updated keys are properly applied.
  • Seeking additional support: If none of the above steps resolve the issue, consider seeking additional support from NVIDIA experts or the developer community.

In comparison to other topics in the provided context, this issue seems to be related to the “Boot failed” topic, which also involves a boot issue with a Jetson Xavier NX device. However, the specific error message and context are different, so it’s essential to analyze this issue separately.

Please provide more information about the error log and any additional details you can share about your setup and configuration. This will help me provide a more accurate and comprehensive analysis of the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

6

Hi wpceswpces,

It seems one property(thermtrip_hot) in BPMP-DTB has been changed.

Are you using the custom board config or jetson-agx-orin-devkit-industrial.conf for your AGX Orin industrial module(P3701-0008)?

Please share the full log when you were generating the capsule update payload.

8

Hello,KevinFFF.

The log is as follows:

log.txt (78.2 KB)

9

Just now, when I tried to re-flash the device, it seems that writing rootfs_b failed. i will try it again.

I> Writing A_kernel-dtb partition.
I> Writing B_kernel partition.
I> Writing B_kernel-dtb partition.
I> Writing recovery partition.
I> Writing recovery-dtb partition.
I> Writing esp partition.
I> Writing APP partition.
I> Writing APP_b partition.
C> Task 0x0 failed (err: 0x3e3e0204)
E> Top caller module: TIMER, error module: TIMER, reason: 0x04, aux_info: 0x02
I> Busy Spin
10 
Existing bpffile(/home/wpces/Downloads/Linux_for_Tegra/bootloader/bpmp_t234-TE990M-A1_prod.bin) reused.

From the log you shared, it uses bpmp_t234-TE990M-A1_prod.bin rather than bpmp_t234-TE992M-A1_prod.bin for BPMP-FW.

It may be caused from the wrong customization in ota_board_specs.conf to support capsule update for your custom carrier board config.

11

Hi,KevinFFF

i wonder how to use the right bin file bpmp_t234-TE992M-A1_prod.bin rather than bpmp_t234-TE990M-A1_prod.bin. my commandline is

sudo FAB=000 BOARDID=3701 FUSELEVEL=fuselevel_production BOARDSKU=0008 ./build_l4t_bup.sh jetson-agx-orin-devkit-industrial mmcblk0p1

./generate_capsule/l4t_generate_soc_capsule.sh -i bootloader/payloads_t23x/bl_only_payload -o ./TEGRA_BL.Cap t234

nv_bootloader_capsule_updater.sh -q /root/TEGRA_BL.Cap t234

can you give me some suggestions in detail？

12

It seems a deprecated script, could you use l4t_generate_soc_bup.sh instead?

BPMP-FW should be specified in board config.
Please also share jetson-agx-orin-devkit-industrial.conf for further check.

Do you have the flash log you used to flash this board before?