Failed to Turn ISP Power On Error at OrinNano 8GB L4T 35.5.0
Issue Overview
Users are encountering a critical issue when migrating from L4T (Linux for Tegra) version 35.4.1 to 35.5.0 on a custom board based on the Jetson Orin Nano 8GB. During the flashing process, an error occurs that prevents the Image Signal Processor (ISP) from powering on, resulting in a boot failure with messages indicating firmware initialization failure. The issue arises specifically when using the bpmp_t234-TE980M-A1_prod.bin
firmware file, which has been found incompatible with the setup.
Relevant Hardware and Software Specifications
- Device: Jetson Orin Nano 8GB Custom Board
- BSP (Board Support Package): L4T 35.5.0
- Firmware Files:
bpmp_t234-TE980M-A1_prod.bin
(causing errors)bpmp_t234-TE950M-A1_prod.bin
(working without errors)
Symptoms
- Error message during bootloader startup:
ERROR: camera-ip/isp5/isp5.c:1980 [isp5_pm_init] "ERROR: Failed to turn isp power on"
*** FIRMWARE INIT FAILED AT LEVEL 95 ***
- The system hangs during firmware writing and fails to boot correctly.
Possible Causes
- Incompatible Firmware File: The use of
bpmp_t234-TE980M-A1_prod.bin
instead of the appropriatebpmp_t234-TE950M-A1_prod.bin
for the Orin Nano may lead to initialization failures. - Changes in Firmware Logic: The migration from L4T 35.4.1 to 35.5.0 introduced changes in how firmware files are selected based on chip SKU rather than board SKU, which may not align with the user’s configuration.
- Incorrect Configuration Settings: Specifying BOARDID and BOARDSKU directly without connecting the board may lead to incorrect chip SKU detection, causing fallback to default firmware settings.
- Missing or Incorrect Device Tree Configuration: The device tree configuration may not be updated correctly to reflect the new firmware requirements, leading to communication issues with hardware components.
Troubleshooting Steps, Solutions & Fixes
Step-by-Step Instructions
-
Verify Firmware Files:
- Ensure that you are using the correct firmware file for your specific board SKU:
- For Orin Nano SKU 0003, use
bpmp_t234-TE950M-A1_prod.bin
.
- For Orin Nano SKU 0003, use
- Ensure that you are using the correct firmware file for your specific board SKU:
-
Check Chip SKU Detection:
- If possible, connect the board and check if it correctly reads the chip SKU:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --showlogs
- If possible, connect the board and check if it correctly reads the chip SKU:
-
Modify Configuration Files:
- Review and modify the configuration settings in
p3767.conf.common
to ensure that they are compatible with your setup:# Ensure correct BPFFILE assignment based on chip SKU process_chip_sku_version() { ... if [ "${chip_SKU}" != "00" ]; then BPFFILE=`echo "${BPFFILE}" | sed "s|T.*-A1|${bpmp_fw_binary[${chip_SKU}]}|"`; fi; }
- Review and modify the configuration settings in
-
Rebuild and Flash:
- If changes were made to device tree or kernel configurations, rebuild and flash your setup:
sudo ./flash.sh jetson-orin-nano-devkit mmcblk0p1
- If changes were made to device tree or kernel configurations, rebuild and flash your setup:
-
Testing After Changes:
- After flashing, reboot the device and monitor for any boot errors or ISP initialization issues.
-
Consult Documentation:
- Refer to NVIDIA’s official documentation for guidance on flashing procedures and troubleshooting steps related to firmware issues.
Recommended Fixes
- Users have reported success by reverting back to using
bpmp_t234-TE950M-A1_prod.bin
for their configurations. - Ensure that all configuration files are correctly set up according to the latest L4T release guidelines.
Best Practices for Future Prevention
- Always confirm that you are using compatible firmware files for your specific hardware configuration before flashing.
- Keep a backup of working configuration files and document any changes made during development.
- Regularly check NVIDIA forums and documentation for updates or known issues related to new L4T releases.
Unresolved Aspects and Further Investigation
- Users continue to seek clarification on whether future updates will further change how firmware files are managed based on chip SKU versus board SKU.
- There may be additional debugging steps required for users who encounter similar issues after following these recommendations.
By following these troubleshooting steps and solutions, users can effectively resolve issues related to ISP power failures during boot on their Jetson Orin Nano platforms while ensuring compatibility with their custom hardware configurations.