Verdin IMX8M-Plus production fails with 1.1B but passes with 1.1A

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


It seems like the issue you’re encountering with the Verdin iMX8M Plus version 1.1B modules is related to changes in the memory layout or reserved memory regions in the U-Boot environment. The error message ** Reading file would overwrite reserved memory ** indicates that the memory address 0xc0000000 you are trying to load the FPGA configuration file into is now part of a reserved memory region in the new module version.

Here are a few steps you can take to troubleshoot and resolve this issue:

  1. Check U-Boot Configuration:

    • Verify if there have been any changes in the U-Boot configuration between versions 1.1A and 1.1B. Specifically, look for changes in the memory layout or reserved memory regions.
  2. Adjust Memory Address:

    • Try loading the FPGA configuration file into a different memory address that is not reserved. You can find a suitable address by checking the memory map in U-Boot. For example, you can use the bdinfo command in U-Boot to get information about the available memory regions.
  3. Update Device Tree:

    • Ensure that the device tree used in U-Boot is up-to-date and matches the new module version. There might be changes in the reserved memory regions defined in the device tree.
  4. Consult Release Notes:

    • Check the release notes or errata documents for the Verdin iMX8M Plus version 1.1B. There might be documented changes or known issues that could explain the difference in behavior.
  5. Contact Toradex Support:

    • If the above steps do not resolve the issue, it would be best to contact Toradex technical support for further assistance. Provide them with detailed information about the issue, including the exact U-Boot version and configuration you are using.

Here is an example of how you might adjust the memory address in your command:

ext4load mmc 2:2 0x80000000 $fpga_file

Make sure that the new address 0x80000000 is within the available memory range and not part of any reserved region.

By following these steps, you should be able to identify and resolve the issue with the memory address conflict in the new module version.

Please, also check if these links can help you solve your problem:

Load binary file from eMMC instead of SD card.