Display Driver Integration in Bootloader for Nvidia Jetson Orin Nano

Issue Overview

Users are experiencing a delay in display activation when using the Nvidia Jetson Orin Nano Dev board with a custom carrier board. Specifically, displays connected via an MST (Multi-Stream Transport) hub are only activating after approximately 33 seconds of boot time, which prevents users from seeing early boot logs or boot logos. This issue arises during the BIOS stage, where the display configuration defaults to a resolution of 800×600 instead of the intended 600×1024.

The problem has been reported consistently across different setups, indicating that it is not an isolated incident. The impact on user experience is significant, as early diagnostics and branding visibility are compromised. Users have noted that the same displays function correctly with the Nvidia development kit, which shows output from the UEFI stage.

Possible Causes

• Hardware Incompatibilities: The custom carrier board may not fully support MST functionality as seen in the Nvidia dev kit, leading to display initialization delays.

• Driver Issues: The UEFI does not currently support MST mode, which could result in improper display configurations during boot.

• Configuration Errors: The settings in the BIOS may not be optimized for dual display setups, causing resolution mismatches and delayed activation.

• Environmental Factors: Power supply issues or temperature variations could potentially affect hardware performance, although this is less likely given the consistent nature of the problem.

• User Errors: Misconfigurations during setup or incorrect connections might contribute to display issues, but users have indicated that they are following standard procedures.

Troubleshooting Steps, Solutions & Fixes

1. Verify Hardware Connections:

   • Ensure that all connections between the displays and the custom carrier board are secure.
   • Test with different cables or ports to rule out physical defects.

2. Check Compatibility with Nvidia Dev Kit:

   • Connect the same displays and MST hub to the Nvidia development kit to confirm if the issue persists. This can help isolate whether the problem lies with the custom board or the displays themselves.

3. Review UEFI Settings:

   • Investigate UEFI configuration options for any available settings related to display outputs.
   • Note that current guidance indicates UEFI does not support MST mode.

4. Experiment with Different Resolutions:

   • Attempt to manually set resolutions supported by UEFI (1080×1920, 480×640, and 720×1280) during BIOS configuration to see if this resolves the initial display issue.

5. Driver Updates:

   • Check for any available updates for Jetpack or relevant drivers that might address compatibility issues.
   • Note that users have indicated no additional drivers exist for MST support in UEFI at this time.

6. Modify Bootloader Code (if applicable):

   • While direct modifications are not currently supported, users can explore existing bootloader code for potential customization options regarding MST support.
   • Consult with Nvidia’s documentation for any advanced configurations that might be possible.

7. Monitor Temperature and Power Supply:

   • Ensure that the power supply meets specifications and that there are no overheating issues affecting performance.

8. Document Findings and Share with Community:

   • If successful solutions are found through experimentation, share these findings back on forums to assist others facing similar issues.

9. Contact Nvidia Support:

   • If none of these steps resolve the issue, consider reaching out to Nvidia’s technical support for further assistance.

Recommended Approach

Users have found success by testing configurations on the Nvidia development kit first before applying them to their custom boards. This method helps identify whether issues stem from hardware compatibility or configuration errors on their custom setup.

Unresolved Aspects

Further investigation is needed regarding potential firmware updates that might enable MST mode in future versions of UEFI or Jetpack software. Users should remain engaged in community discussions for updates on these developments.