Tezi 7.3 failed to boot on Apalis IMX8QP 1.0 Board

MikeMontoya · July 8, 2025, 12:52pm

I downloaded Tezi 7.3 from the following source today: Download Toradex Easy Installer | Toradex Developer Center

I started the Tezi on my computer with the following command: ./recovery-linux.sh

I got the following error (I interrupted the boot process to enable xtrace outputs):

U-Boot 2024.04-7.3.0+git.4db7ef83ebd6 (Jun 03 2025 - 06:47:58 +0000)

CPU:   NXP i.MX8QM RevB A53 at 1200 MHz at 37C

DRAM:  2 GiB
Core:  203 devices, 24 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex 0048 Apalis iMX8QP 2GB WB V1.0B
Serial#: 06597545
Boot:  USB
Reset cause: Software reset

 BuildInfo:
  - SCFW 83624b99, SECO-FW c9de51c0, IMX-MKIMAGE 71b8c18a, ATF 1b27ee3
  - U-Boot 2024.04-7.3.0+git.4db7ef83ebd6

Detect USB boot. Will enter fastboot mode!
Net:   eth0: ethernet@5b040000
Fastboot: Normal
Boot from USB for uuu
Hit any key to stop autoboot:  0
Apalis iMX8 # <INTERRUPT>
Apalis iMX8 # <INTERRUPT>
Apalis iMX8 #
Apalis iMX8 #
Apalis iMX8 #
Apalis iMX8 #
Apalis iMX8 #
Apalis iMX8 #
Apalis iMX8 # setenv xtrace yes
Apalis iMX8 # boot
+ boot
+ fastboot 0
Failed to configure default pinctrl
+ setenv fastboot_buffer 0x82e00000
Detect USB boot. Will enter fastboot mode!
Starting download of 1834 bytes

downloading of 1834 bytes finished
+ setenv fastboot_buffer 0x82e10000
Detect USB boot. Will enter fastboot mode!
Starting download of 117 bytes

downloading of 117 bytes finished
+ setenv fastboot_buffer 0x8a000000
Detect USB boot. Will enter fastboot mode!
Starting download of 42958743 bytes
..........................................................................
..........................................................................
..........................................................................
..........................................................................
...............................
downloading of 42958743 bytes finished
+ source 0x82e00000
## Executing script at 82e00000
+ env set fitconf_fdt_overlays
+ env set prefix
+ test -n
+ env set overlays_file overlays.txt
+ env set load_cmd load :
+ env set fitimage_addr 0x8a000000
+ env set overlays_addr 0x82e10000
+ env set bootcmd_args env set bootargs quiet video=LVDS-1:d video=HDMI-A-1:640x480-16@60D initcall_blacklist=vpu_driver_init rootfstype=squashfs root=/dev/ram autoinstall ${teziargs}
+ env set bootcmd_run echo "Bootargs: ${bootargs}" && bootm ${fitimage_addr}#conf-freescale_${fdtfile}${fitconf_fdt_overlays}
+ env set tezi_image tezi.itb
+ env set set_default_overlays env set fdt_overlays "     apalis-imx8_hdmi_overlay.dtbo     apalis-imx8_spi1_spidev_overlay.dtbo     apalis-imx8_spi2_spidev_overlay.dtbo "
+ test x1 = x1
+ env set bootcmd_tezi ;
+ env set load_overlays_file env import -t ${overlays_addr} 0x200; test -n ${fdt_overlays} || run set_default_overlays
+ env set set_apply_overlays env set apply_overlays "for overlay_file in "\${fdt_overlays}"; do env set fitconf_fdt_overlays "\"\${fitconf_fdt_overlays}#conf-\${overlay_file}\""; env set overlay_file; done; true"
+ run load_overlays_file
+ env import -t 0x82e10000 0x200
+ test -n apalis-imx8_hdmi_overlay.dtbo apalis-imx8_spi1_spidev_overlay.dtbo apalis-imx8_spi2_spidev_overlay.dtbo
+ run set_apply_overlays
+ env set apply_overlays for overlay_file in ${fdt_overlays}; do env set fitconf_fdt_overlays "${fitconf_fdt_overlays}#conf-${overlay_file}"; env set overlay_file; done; true
+ run apply_overlays
+ env set fitconf_fdt_overlays #conf-apalis-imx8_hdmi_overlay.dtbo
+ env set overlay_file
+ env set fitconf_fdt_overlays #conf-apalis-imx8_hdmi_overlay.dtbo#conf-apalis-imx8_spi1_spidev_overlay.dtbo
+ env set overlay_file
+ env set fitconf_fdt_overlays #conf-apalis-imx8_hdmi_overlay.dtbo#conf-apalis-imx8_spi1_spidev_overlay.dtbo#conf-apalis-imx8_spi2_spidev_overlay.dtbo
+ env set overlay_file
+ true
+ run bootcmd_args
+ env set bootargs quiet video=LVDS-1:d video=HDMI-A-1:640x480-16@60D initcall_blacklist=vpu_driver_init rootfstype=squashfs root=/dev/ram autoinstall
+ run bootcmd_tezi
+ run bootcmd_run
+ echo Bootargs: quiet video=LVDS-1:d video=HDMI-A-1:640x480-16@60D initcall_blacklist=vpu_driver_init rootfstype=squashfs root=/dev/ram autoinstall
Bootargs: quiet video=LVDS-1:d video=HDMI-A-1:640x480-16@60D initcall_blacklist=vpu_driver_init rootfstype=squashfs root=/dev/ram autoinstall
+ bootm 0x8a000000#conf-freescale_imx8qp-apalis-eval.dtb#conf-apalis-imx8_hdmi_overlay.dtbo#conf-apalis-imx8_spi1_spidev_overlay.dtbo#conf-apalis-imx8_spi2_spidev_overlay.dtbo
## Loading kernel from FIT Image at 8a000000 ...
Could not find configuration node
ERROR -2: can't get kernel image!

Apart from that, my device boots from BSP 7.2 perfectly (with patch from Missing support for Apalis IMX8QP 1.0 Boards in BSP 7 - #9 by allan.tx).

U-Boot 2024.04-7.2.0-devel+git.5c6f89c91d3d (Mar 14 2025 - 21:21:12 +0000)

CPU:   NXP i.MX8QM RevB A53 at 1200 MHz at 37C

DRAM:  2 GiB
Core:  203 devices, 24 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex 0048 Apalis iMX8QP 2GB WB V1.0B
Serial#: 06597545
Boot:  MMC0
Reset cause: POR

 BuildInfo:
  - SCFW 83624b99, SECO-FW c9de51c0, IMX-MKIMAGE 4622115c, ATF
  - U-Boot 2024.04-7.2.0-devel+git.5c6f89c91d3d

flash target is MMC:0
Net:   eth0: ethernet@5b040000 
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
MMC: no card present
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device 
Scanning mmc 0:1...
Found U-Boot script /boot.scr  
5974 bytes read in 2 ms (2.8 MiB/s)
## Executing script at 9d480000
Loading DeviceTree: imx8qp-apalis-v1.1-eval.dtb
176610 bytes read in 5 ms (33.7 MiB/s)
147 bytes read in 1 ms (143.6 KiB/s)
Working FDT set to 9d400000
Applying Overlay: apalis-imx8_hdmi_overlay.dtbo
2205 bytes read in 2 ms (1.1 MiB/s)
Applying Overlay: apalis-imx8_spi1_spidev_overlay.dtbo
551 bytes read in 2 ms (268.6 KiB/s)
Applying Overlay: apalis-imx8_spi2_spidev_overlay.dtbo
551 bytes read in 2 ms (268.6 KiB/s)
Applying Overlay: apalis-imx8_lvds_overlay.dtbo
2031 bytes read in 2 ms (991.2 KiB/s)
8233798 bytes read in 185 ms (42.4 MiB/s)
Bootargs: root=PARTUUID=8dfbeff1-02 ro rootwait console=tty1 console=ttyLP1,115200
   Uncompressing Kernel Image to 0
## Flattened Device Tree blob at 9d400000
   Booting using the fdt blob at 0x9d400000
Working FDT set to 9d400000
   Loading Device Tree to 00000000fd628000, end 00000000fd676fff ... OK
Working FDT set to fd628000
/bus@5a000000/dma-controller@5a1f0000, 57852
/bus@5a000000/dma-controller@5a9f0000, 59084
/bus@59000000/dma-controller@591f0000, 23492
/bus@59000000/dma-controller@591f0000, 23492
/bus@59000000/dma-controller@599f0000, 24844

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.6.84-7.2.0-devel (oe-user@oe-host) (aarch64-tdx-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1 SMP PREEMPT Mon Mar 31 08:47:48 UTC 2025
[    0.000000] KASLR disabled due to lack of seed
[    0.000000] Machine model: Toradex Apalis iMX8QP V1.1 on Apalis Evaluation Board
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000c0000000, size 960 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000c0000000..0x00000000fbffffff (983040 KiB) map reusable linux,cma
[    0.000000] OF: reserved mem: 0x0000000084000000..0x0000000085ffffff (32768 KiB) nomap non-reusable decoder-boot@84000000
...

I’m currently on Tezi 5.7.6 which is still working.

ToradexAI · July 8, 2025, 12:53pm

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer?

Hello! Thank you for providing detailed logs and a clear description of your issue.

Based on your report, the key points are:

Your hardware is: Toradex Apalis iMX8QP 2GB WB V1.0B.
The device boots fine with BSP 7.2.
With Toradex Easy Installer (Tezi) 7.3, U-Boot fails to boot the FIT image, reporting:
```
Could not find configuration node
ERROR -2: can't get kernel image!
```
The boot command tries to use:
bootm 0x8a000000#conf-freescale_imx8qp-apalis-eval.dtb#conf-apalis-imx8_hdmi_overlay.dtbo#...

Root Cause:
This indicates that the FIT image (tezi.itb) packaged in Tezi 7.3 likely does not contain a configuration for freescale_imx8qp-apalis-eval.dtb.

BSP 7.2 loads imx8qp-apalis-v1.1-eval.dtb, while Tezi 7.3 defaults to imx8qp-apalis-eval.dtb. It appears the automatic device tree selection logic or the naming convention in the new release does not match your hardware variant (V1.0B).

What You Can Do:

Check Available Device Trees in the FIT Image
- Interrupt U-Boot and use this command to list available FIT configs:
```
iminfo 0x8a000000
```
- Or, if supported:
```
fdt list 0x8a000000
```
- This will help confirm the actual config names present inside the FIT image.
Identify the Correct Device Tree File
- For Apalis iMX8QP V1.0B, the correct file may be imx8qp-apalis-eval.dtb or a variant thereof. However, if the old release used imx8qp-apalis-v1.1-eval.dtb and your hardware is V1.0B, this may cause issues.
Manually Set the fdtfile Variable
- At the U-Boot prompt, try setting the fdtfile variable to match what’s actually inside the FIT image. For example, if imx8qp-apalis-v1.1-eval.dtb is available:
```
setenv fdtfile imx8qp-apalis-v1.1-eval.dtb
```
- Or, if only imx8qp-apalis-eval.dtb exists in the image:
```
setenv fdtfile imx8qp-apalis-eval.dtb
```
- After setting, try booting again with:
```
run bootcmd_run
```
- If this works, you can make the change persistent with:
```
saveenv
```
Check for Naming Changes in Device Tree Support
- There may have been changes to device tree file naming between BSP 7.2 and 7.3. Review the release notes for BSP 7.3 and compare the image contents if possible.
- More info:
  Best Practices with U-Boot Environment Variables
  The U-Boot Console

Next Steps:

Try setting the fdtfile as shown and see if Tezi boots correctly.
If the FIT image is missing the configuration for your hardware, you may need to use a Tezi version that includes the correct device tree, or if possible, customize the Tezi image.

If you report back the results of the iminfo or fdt list command, I can provide more directed guidance.

Best regards,
Toradex AI Assistant.

joaom.tx · July 17, 2025, 1:05pm

Hello @MikeMontoya !

This is a known issue with Tezi 7.3 when used on the Apalis iMX8QP V1.0B. Unfortunately, I don’t have an ETA on a permanent fix, but this is already tracked internally and should be addressed in a future release.

In the meantime, the workaround suggested by our AI assistant is valid. Alternatively, using your current Tezi 5.7.6 with a USB stick containing your intended image can also be a way to install images.

MikeMontoya · July 17, 2025, 1:34pm

Thank you for the confirmation. Yes, I will continue using 5.7.6. It works fine even for loading the images via network.

Looking forward to having the bug fixed soon.