Remove boot logo and add boot progress bar

Issue Overview

Users of the Nvidia Jetson Orin Nano Dev board (8GB) are experiencing difficulties in customizing the boot process of their devices. Specifically, they want to remove the Nvidia boot logo and add a boot progress bar during startup. The issue arises during the setup phase, particularly while attempting to modify the UEFI (Unified Extensible Firmware Interface) settings.

Symptoms

• Users report that after following instructions to replace the Nvidia logo with a custom one, the logo does not appear during boot.
• Some users encounter errors when compiling UEFI binaries, which prevents them from successfully making these changes.

Context

• The problem occurs in a development environment using Jetson release 36.3.
• Users are employing various methods, including Docker, to compile UEFI, but face issues related to missing files and compilation errors.
• The impact on user experience is significant, as the boot logo is a crucial part of their product’s branding and user interface.

Frequency

The issue appears to be relatively common among users attempting similar customizations, with multiple threads discussing various aspects of the problem.

Possible Causes

• Hardware Incompatibilities or Defects: Issues may arise if the custom carrier board has compatibility problems with the Orin Nano.

• Software Bugs or Conflicts: Errors in the UEFI source code or conflicts between different versions of software could lead to failures in displaying custom logos.

• Configuration Errors: Incorrect settings during the UEFI build process can prevent successful modifications.

• Driver Issues: Outdated or incompatible drivers may hinder the functionality of graphical outputs during boot.

• Environmental Factors: Power supply issues or overheating could affect system performance and behavior during startup.

• User Errors or Misconfigurations: Mistakes in following instructions for replacing logos or compiling UEFI could result in failures.

Troubleshooting Steps, Solutions & Fixes

Step-by-Step Instructions

1. Verify Hardware Compatibility:

   • Ensure that your custom carrier board is compatible with the Orin Nano.

2. Clone the Correct UEFI Source:

   • Use the following command to clone the source for R36.3.0:

     edk2_docker edkrepo clone nvidia-uefi-r36.3.0 NVIDIA-Platforms r36.3.0
     

3. Build UEFI Binary:

   • Follow these commands to compile UEFI:

     cd nvidia-uefi
     edk2_docker edk2-nvidia/Platform/NVIDIA/Jetson/build.sh
     

4. Check Logo File Specifications:

   • Confirm that your custom BMP files have correct resolutions (e.g., 640×480 for small logos).
   • Ensure that there are no compression issues; use exiftool to verify BMP file details.

5. Modify Logo Files:

   • Replace existing logo files located at:

     nvidia-uefi-r36.3.0/edk2-nvidia/Silicon/NVIDIA/Assets/
     

   • Make sure to replace nvidiagray*.bmp files with your custom logos.

6. Update UEFI Binary:

   • After compiling without modifications, update the UEFI binary (uefi_Jetson_RELEASE.bin) and verify if it boots correctly.

7. Debugging:

   • If issues persist, enable debug mode in UEFI to check for errors during boot.

8. Check Bootloader Partition Size:

   • Ensure that the size of your UEFI binary does not exceed the bootloader partition limit (e.g., 2.5MB).

9. Consult Documentation:

   • Refer to NVIDIA’s official documentation for any updates or patches related to your version.

Recommended Fixes

• If you encounter a black screen after replacing logos, ensure that your BMP files are in Windows V3 format and not V5.

• Check if any hex values related to logos need modification in edk2-nvidia/Silicon/NVIDIA/NVIDIA.dec.

Best Practices for Prevention

• Always back up existing configurations before making changes.

• Use version control for your source code modifications to easily revert changes if necessary.

Additional Notes

• Users have reported success by compiling without any modifications before attempting further changes.

• If issues remain unresolved after following these steps, consider reaching out to NVIDIA support or community forums for additional assistance.