Jetson Orin Nano UEFI Memory Test Configuration and Execution

Issue Overview

Users of the Nvidia Jetson Orin Nano development board have been experiencing difficulties with configuring and executing memory tests using the UEFI (Unified Extensible Firmware Interface) bootloader. The main issues revolve around:

• Uncertainty about the availability of memory test features on the Jetson Orin Nano
• Confusion regarding the functionality of the "Memory Test options" in UEFI
• Difficulty in enabling and verifying the execution of memory tests
• Discrepancies between debug and release versions of UEFI binaries

These issues are primarily encountered during the setup and configuration phase, impacting users’ ability to perform comprehensive hardware diagnostics on their Jetson Orin Nano boards.

Possible Causes

1. Feature Availability: Some memory test features, such as Double-Bit ECC Error Detection, are only supported on specific Jetson models like the AGX Orin Industrial.

2. Configuration Issues: The memory test protocol may not be enabled by default in the UEFI configuration files.

3. Software Version Discrepancies: Different versions of JetPack or UEFI binaries may have varying levels of support for memory test features.

4. User Misunderstanding: Confusion about the proper way to enable and execute memory tests, as well as how to interpret the results.

5. Incomplete Documentation: Lack of clear, comprehensive documentation on how to use and interpret memory test features on the Jetson Orin Nano.

Troubleshooting Steps, Solutions & Fixes

Enabling Memory Tests

1. Download the latest UEFI source for R35.5.0:

   $ edkrepo clone nvidia-uefi-r35.5.0 NVIDIA-Platforms r35.5.0
   

2. Enable the memory test protocol in the NVIDIA.common.dsc.inc file:

   [Defines]
   !ifndef CONFIG_MEMORY_TEST
   CONFIG_MEMORY_TEST=y
   !endif
   

3. Rebuild the UEFI binary after making this change.

Accessing Memory Test Options

1. Navigate to the UEFI menu:
   Device Manager → NVIDIA Configuration → Memory Test options

2. Configure the desired memory test options according to the descriptions provided in the menu.

Using Debug UEFI Binary

For more detailed debugging information:

1. Build the debug UEFI binary (uefi_Jetson_DEBUG.bin) following the instructions in the "Build without docker" guide.

2. Replace the existing UEFI binary in your Linux_for_Tegra directory:

   cp uefi_Jetson_DEBUG.bin <Linux_for_Tegra>/bootloader/uefi_jetson.bin
   

Verifying Memory Test Execution

1. Enable debug logging in the UEFI binary as described above.

2. Reboot the system and capture the full serial console log.

3. Look for memory test-related messages in the log, such as the execution start (around line 1626) and test results (around line 1935) in the provided example.

Troubleshooting Common Issues

• If you encounter the message "Failed to find memory test protocol," ensure that the memory test protocol is enabled in the UEFI configuration as described earlier.

• If memory tests don’t seem to complete in the release version, try using the debug version to gather more information about the test execution process.

• Note that the memory test duration may vary; in the provided example, it took about 18 seconds in the debug version.

Additional Notes

• The default UEFI included in JetPack 5.1.3 may not have memory tests enabled by default. Users need to manually enable and configure this feature.

• Both debug and release versions of the UEFI binary should support memory tests when properly configured.

• If you continue to experience issues or need further clarification, consider reaching out to NVIDIA support or posting in the official Jetson developer forums with detailed logs and configuration information.