Changing Nvidia Splash Screen on L4T 36.4

Issue Overview

Users are experiencing difficulties changing the Nvidia logo displayed during bootup on devices running L4T (Linux for Tegra) version 36.4. The primary symptoms include the inability to locate the bmp.blob file, which was previously used for this purpose in earlier versions. This issue arises during the setup process when users attempt to customize their boot experience. Users have reported that the documentation for L4T 36.x versions lacks clear instructions on how to achieve this customization, leading to frustration and confusion. The problem appears to be consistent across multiple attempts and affects user experience by limiting personalization options during device startup.

Possible Causes

1. Deprecation of Old Methods: The method previously used to change the splash screen has been deprecated since L4T version 35, which means users cannot rely on older documentation or techniques.
2. Missing Documentation: There is a lack of updated resources or documentation for L4T 36.x versions, making it difficult for users to find current methods for modifying the boot logo.
3. File Structure Changes: The absence of the bmp.blob file in the Linux_for_Tegra/boot directory indicates a change in how Nvidia handles boot logos, which may not be clearly communicated to users.
4. Version-Specific Issues: Users running different versions of L4T (such as 36.3 vs. 36.4) may encounter varying levels of support and functionality, complicating the process further.

Troubleshooting Steps, Solutions & Fixes

1. Consult Updated Documentation: Users should refer to the latest Nvidia documentation related to UEFI customization for L4T 36.x versions, specifically:

   • Nvidia UEFI Customization Guide.

2. Check Installed Version: Ensure that the correct version of L4T is installed on your device:

   • Use the command:

     cat /etc/nv_tegra_release
     

   • This will display the currently installed version of L4T.

3. Backup Current Settings: Before making any changes, it’s advisable to back up existing configurations and files related to boot settings.

4. Explore Alternative Methods: If the traditional methods are no longer applicable, consider exploring other customization techniques such as:

   • Modifying UEFI settings directly if available.
   • Checking community forums for user-contributed solutions or scripts that may have emerged since official documentation was last updated.

5. Testing Different Versions: If feasible, test with an earlier version of L4T (like 36.3) where users have reported success in changing the splash screen:

   • Flash your device with L4T 36.3 using SDK Manager or appropriate flashing tools.

6. Community Support: Engage with community forums or Nvidia support channels for additional insights or shared experiences from other users facing similar issues.

7. Document Any Changes: Keep a detailed log of any changes made during troubleshooting, including commands executed and their outcomes, which could be useful for future reference or when seeking help from others.

8. Stay Updated: Monitor Nvidia’s official channels for any updates regarding new releases or patches that might address these issues in future iterations of L4T.

By following these steps and utilizing available resources, users can better navigate the challenges associated with customizing their Nvidia Jetson devices during bootup.