Kernel Panic When Using DisplayPort on Custom Carrier Board for Nvidia Jetson Orin Nano

Issue Overview

Users have reported experiencing a kernel panic when connecting a DisplayPort (DP) cable to the Nvidia Jetson Orin Nano before booting the system. The panic does not occur if the DP cable is connected after booting. This issue arises specifically in a custom carrier board designed for use with the Orin Nano, while similar setups with the Xavier NX function correctly. The kernel panic logs indicate multiple errors related to the display controller and memory access violations, suggesting a potential issue with device tree configurations or hardware compatibility. The problem appears to be consistent across multiple attempts, significantly impacting user experience by preventing proper system startup.

Possible Causes

1. Hardware Incompatibilities: The custom carrier board may have hardware configurations that are not fully compatible with the Orin Nano, especially regarding display connections.
2. Device Tree Configuration Errors: The adapted device tree for the Orin Nano may contain incorrect settings that lead to kernel panics when initializing the display before boot.
3. Driver Issues: Outdated or incompatible drivers could cause conflicts during the initialization of the display hardware.
4. Configuration Errors: Incorrect pinmux settings for the DP connection might lead to improper initialization sequences.
5. Environmental Factors: Power supply issues or thermal conditions could affect the stability of the system during boot.
6. User Errors: Misconfigurations during setup or flashing of the system could lead to these kernel panic issues.

Troubleshooting Steps, Solutions & Fixes

1. Check Hardware Compatibility:

   • Verify that all components of the custom carrier board are compatible with the Orin Nano specifications.
   • Test with an official Nvidia Jetson Orin Nano devkit to confirm if the issue persists.

2. Review Device Tree Configuration:

   • Ensure that all relevant device tree entries for DisplayPort are correctly configured.
   • Compare your device tree against a known working configuration from the official Orin Nano devkit.

3. Reflash and Update Drivers:

   • Reflash the system using SDK Manager with minimal modifications to ensure a clean installation.
   • Update all drivers to their latest versions compatible with L4T 35.4.1.

4. Modify Pinmux Settings:

   • Review and adjust pinmux settings related to DisplayPort connections as per Nvidia’s guidelines.
   • Ensure that you are using the correct dp-a03 configuration.

5. Test Kernel Configuration:

   • Enable CONFIG_FB_SIMPLE in your kernel configuration if it is not already enabled, as this has resolved similar issues for other users.
   • After making changes, rebuild and flash your kernel image.

6. Use Debugging Tools:

   • Utilize serial console logging to capture detailed boot logs for analysis during kernel panics.
   • Check for specific error messages related to memory access violations or driver loading failures.

7. Isolation Testing:

   • Test different configurations by systematically disabling components or changing settings one at a time to isolate the cause of the panic.

8. Consult Documentation and Community Resources:

   • Refer to Nvidia’s official documentation for troubleshooting kernel panics and device tree configurations.
   • Engage with community forums for insights from other users who may have faced similar issues.

9. Recommended Approach:

   • If multiple users have reported success after enabling CONFIG_FB_SIMPLE, prioritize this step as part of your troubleshooting process.

10. Further Investigation Areas:

    • Investigate any unresolved aspects of your device tree changes that might conflict with existing configurations.
    • Explore whether other patches or updates from Nvidia could address underlying issues affecting kernel stability.

By following these steps, users should be able to diagnose and potentially resolve kernel panic issues when using DisplayPort on their custom carrier boards with Nvidia Jetson Orin Nano systems.