英伟达团队，你们好。
我们用Orin NX16GB的核心板，搭配自制载板，JetPack版本为5.1.5。此前正常运行了1个多月一直保持正常。最近两周在多次上电启动过程中，有20%的概率会启动失败，出现FIRMWARE INIT FAILED AT LEVEL 95的情况
[Thu Aug 21 18:52:05.023 2025] I> BR-BCT Boot-Chain is 0, and status is 1. Set UPDATE_BRBCT bit to 0
[Thu Aug 21 18:52:05.023 2025] I> MB2 finished
[Thu Aug 21 18:52:05.023 2025]
[Thu Aug 21 18:52:05.023 2025] ÿäNOTICE: BL31: v2.6(release):5e1f8b33d
[Thu Aug 21 18:52:05.023 2025] NOTICE: BL31: Built : 01:34:51, Mar 4 2025
[Thu Aug 21 18:52:05.023 2025] I/TC: Physical secure memory base 0x47c040000 size 0x3fc0000
[Thu Aug 21 18:52:05.090 2025] I/TC:
[Thu Aug 21 18:52:05.155 2025] I/TC: Non-secure external DT found
[Thu Aug 21 18:52:05.333 2025] I/TC: OP-TEE version: 3.22 (gcc version 9.3.0 (Buildroot 2020.08)) #2 Tue Mar 4 09:47:00 UTC 2025 aarch64
[Thu Aug 21 18:52:05.364 2025] I/TC: WARNING: This OP-TEE configuration might be insecure!
[Thu Aug 21 18:52:05.387 2025] I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
[Thu Aug 21 18:52:05.412 2025] I/TC: Primary CPU initializing
[Thu Aug 21 18:52:05.682 2025] I/TC: Test OEM keys are being used. This is insecure for shipping products!
[Thu Aug 21 18:52:05.762 2025] I/TC: Primary CPU switching to normal world boot
[Thu Aug 21 18:52:05.824 2025] ÿá
[Thu Aug 21 18:52:05.824 2025] Jetson UEFI firmware (version 6.1-39721438 built on 2025-03-04T09:36:16+00:00)
[Thu Aug 21 18:52:05.856 2025]
[Thu Aug 21 18:52:06.312 2025]
[Thu Aug 21 18:52:06.353 2025]
[Thu Aug 21 18:52:06.375 2025]
[Thu Aug 21 18:52:06.499 2025] ÿåERROR: camera-ip/isp5/isp5.c:1980 [isp5_pm_init] "ERROR: Failed to turn isp power on"
[Thu Aug 21 18:52:06.499 2025] BUG: core/init/init.c:85 [init_all] "*** FIRMWARE INIT FAILED AT LEVEL 95 ***"
FIRMWARE INIT FAILED AT LEVEL 95.log (782.9 KB)
请问这种情况应该如何修复，以确保系统可以正常启动运行？
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing issues with your Jetson Orin NX 16GB module, specifically with booting and firmware initialization. The error message “FIRMWARE INIT FAILED AT LEVEL 95” suggests that there is a problem with the firmware initialization process.
After reviewing the context, I found several topics related to Jetson Orin NX boot issues, firmware initialization, and JetPack 5.1.2. Here are a few potential solutions and comparisons:
- Boot fails after restoring a Jetson Orin NX: This topic discusses a similar issue with booting after restoring the Jetson Orin NX. The solution involves checking the boot logs and ensuring that the firmware is properly initialized.
- FIRMWARE INIT FAILED AT LEVEL 95: This error message is similar to the one you provided. However, without more information about the log file (7829 KB), it’s difficult to provide a specific solution.
- JetPack 5.1.2 and L4T R35.4.1: There are several topics related to issues with JetPack 5.1.2 and L4T R35.4.1, including boot problems and firmware initialization issues. It’s possible that the issue is related to a known problem with this version of JetPack.
- Orin NX 16GB: There are several topics related to the Orin NX 16GB module, including boot issues and firmware initialization problems. It’s possible that the issue is specific to this module.
To troubleshoot the issue, I recommend:
- Checking the boot logs to see if there are any specific error messages that can help identify the problem.
- Ensuring that the firmware is properly initialized and that there are no issues with the firmware initialization process.
- Verifying that the JetPack version and L4T version are compatible with the Orin NX 16GB module.
- Searching for known issues with JetPack 5.1.2 and L4T R35.4.1, as well as specific issues with the Orin NX 16GB module.
If you provide more information about the log file (7829 KB), I may be able to provide a more specific solution.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
[Thu Aug 21 18:52:04.776 2025]
[Thu Aug 21 18:52:04.776 2025] FATAL ERROR [FILE=platform/drivers/clk/clk-fwk/clk.c, ERR_UID=659]: clock_set_parent failed for clk dmic2, parent plla_out0 (-23)
[Thu Aug 21 18:52:04.776 2025]
Fatal error is this one. Did you configure anything for the Audio?
No, nothing was changed. 在近期多次上电启动期间，没有任何配置变更
Is same module able to reproduce this issue on NV devkit?
No，we have not tried.我们很奇怪，之前一直运行正常的，怎么突然会有这个故障？ 我们的业务场景中也不涉及使用Audio的功能
No，we have not tried.我们很奇怪，之前一直运行正常的，怎么突然会有这个故障？ 我们的业务场景中也不涉及使用Audio的功能