Boot Easy Installer from USB/SD

Technical Support
, , ,
4

The decompression error you’re encountering indicates a potential memory overlap issue when manually loading the TEZI image. The error “inflate() returned -3” suggests the kernel decompression failed, likely due to memory address conflicts.

Root Cause Analysis

The issue appears to be related to the FIT image configuration selection. When you manually boot with bootm ${loadaddr}, U-Boot selects the configuration conf-freescale_imx8mm-verdin-nonwifi-dahlia.dtb, but your module is a Wi-Fi variant (as shown by “Setting variant to wifi” in your boot log).

Troubleshooting Steps

1. Check Device Tree Configuration

Your boot log shows U-Boot is setting the variant to “wifi”, but the FIT image is trying to use the non-wifi configuration. The fdtfile variable should match your hardware variant(1).

You can check and modify this in U-Boot:

> printenv fdtfile
> setenv fdtfile imx8mm-verdin-wifi-dev.dtb
> saveenv

(1)

2. Memory Address Considerations

The decompression error suggests memory overlap. Try loading the image to a different address:

> load usb 0:1 0x50000000 tezi.itb
> bootm 0x50000000

3. Boot Script Analysis

Since the automatic boot from USB fails with “Could not find configuration node”, the issue is likely in how the boot script (boot.scr) selects the FIT configuration. The boot script should properly detect your Wi-Fi variant and select the appropriate configuration node.

4. Alternative Boot Target Configuration

Based on the community discussion, you can modify the U-Boot environment to include USB as a boot target with fallback to eMMC(2). Your current configuration looks correct:

boot_targets=usb0 mmc1 mmc0 dhcp

(1)

5. Verify Boot Script Compatibility

The boot script in your TEZI package might not be compatible with the newer U-Boot version. Try using the boot-tezi.scr file renamed to boot.scr as suggested in the community forum(2).

Recommended Solution

  1. Download a fresh TEZI package for your specific module variant (Wi-Fi version)
  2. Rename boot-tezi.scr to boot.scr on your USB device(2)
  3. Ensure compatibility between your BSP version and the TEZI version

The fact that this worked with older builds suggests there have been changes in either the U-Boot FIT image handling or the device tree configuration detection between BSP versions.

Alternative Recovery Method

If USB boot continues to fail, you might need to use the serial console to access U-Boot and manually configure the environment variables to force the correct device tree selection before attempting to boot TEZI.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.