First start Verdin with Mallow

fmolon · April 8, 2026, 2:05pm

Hi,

I need support for the first boot of my Verdin iMX8MP + Mallow system. I created an SD card containing TEZI 7.5.0. The SD card works correctly on other Verdin + Mallow systems. On this system, as soon as it is powered on with the SD card inserted at boot time, I encounter the following problem:

U-Boot SPL 2020.04-5.7.1+git.33bb8e968332 (Sep 06 2022 - 15:21:33 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
Training FAILED
Quad die, dual rank failed, attempting dual die, single rank configuration.
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from BOOTROM
Find FIT header 0x4803a600, size 969
Need continue download 1024
Download 839680, total fit 841216
NOTICE:  BL31: v2.2(release):toradex_imx_5.4.70_2.3.0-g2fa8c6349e
NOTICE:  BL31: Built : 09:50:17, Jul  4 2022


U-Boot 2020.04-5.7.1+git.33bb8e968332 (Sep 06 2022 - 15:22:12 +0000)

CPU:   i.MX8MP[6] rev1.1 1600 MHz (running at 1200 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 39C
Reset cause: POR
DRAM:  2 GiB
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex Verdin iMX8M Plus Quad 2GB Wi-Fi / BT IT V1.1A, Serial# 08739945
Carrier: Toradex Colibri PXA300 208MHz V1.1C, Serial# 12929231

 BuildInfo:
  - ATF 2fa8c63
  - U-Boot 2020.04-5.7.1+git.33bb8e968332

Setting variant to wifi
flash target is MMC:2
Net:   eth1: ethernet@30be0000, eth0: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:2...
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
starting USB...
Bus usb@38100000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@38200000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@38100000 for devices... 1 USB Device(s) found
scanning bus usb@38200000 for devices... 5 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
ethernet@30bf0000 Waiting for PHY auto negotiation to complete....... done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 224
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 224
DHCP client bound to address 192.168.55.6 (2775 ms)
Using ethernet@30bf0000 device
TFTP from server 192.168.10.1; our IP address is 192.168.55.6; sending through gateway 192.168.55.1
Filename 'boot-tezi.scr'.
Load address: 0x47000000
Loading: T T
Abort
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 224
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 224
DHCP client bound to address 192.168.55.6 (17 ms)
Using ethernet@30bf0000 device
TFTP from server 192.168.10.1; our IP address is 192.168.55.6; sending through gateway 192.168.55.1
Filename 'boot-tezi.scr'.
Load address: 0x40000000
Loading: *
Abort
Verdin iMX8MP TEZI #

The board gets stuck at that point and TEZI does not start. I do not see anything on the HDMI or LVDS output. An Ethernet cable and a keyboard with mouse are connected to the board. From my PC I ran the following command:

torizoncore-builder images serve torizon-image/

No system is installed. What do I need to do in order to start the installation of my Torizon image created with TorizonCore Builder?

ToradexAI · April 8, 2026, 2:06pm

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I can see from your U-Boot output that your Verdin iMX8MP module is correctly identifying the carrier board as “Toradex Colibri PXA300 208MHz V1.1C” but this appears to be incorrect carrier board detection. Your system is actually using a Mallow carrier board, which suggests there may be a configuration issue.

The key issue I notice is that your system is trying to network boot (TFTP) and looking for ‘boot-tezi.scr’ from a TFTP server at 192.168.10.1, but these attempts are failing with “Abort” messages. This indicates that while DHCP is working (your module gets IP 192.168.55.6), the TFTP boot process is not completing successfully.

Troubleshooting Steps

1. Verify TEZI SD Card Boot Priority

Your system should boot from the SD card first, not attempt network boot. Make sure:

The SD card is properly inserted before powering on
The SD card contains a valid TEZI image
Try a different SD card to rule out media issues

2. Check Network Boot Configuration

Since your system is attempting network boot, you may need to modify the boot order. At the U-Boot prompt (Verdin iMX8MP TEZI #), try:

setenv boot_targets "mmc1 mmc2 usb0 dhcp"
saveenv
reset

3. Manual SD Card Boot

If the automatic boot fails, you can manually boot from SD card at the U-Boot prompt:

run distro_bootcmd

Or specifically target the SD card:

run mmc1_boot

4. Verify TorizonCore Builder Image Serving

Since you’re running torizoncore-builder images serve, ensure:

Your PC and the Verdin module are on the same network segment
The TFTP server is accessible from 192.168.55.6 to 192.168.10.1
Try serving from the correct IP address that matches your network configuration

The network configuration shows your module getting IP 192.168.55.6 with gateway 192.168.55.1, but it’s trying to reach TFTP server at 192.168.10.1, which may not be reachable.

Next Steps

Try booting with the SD card without network connection first
If that fails, use the manual U-Boot commands above
Verify your TorizonCore Builder image is properly configured for network deployment

The carrier board misidentification might be cosmetic, but ensure your device tree and hardware configuration match your actual Mallow carrier board setup.

Best regards, Toradex AI Assistant.

Did you like my answer?

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

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

fmolon · April 8, 2026, 2:50pm

@ToradexAI ,

this ismy env on this moment:

Verdin iMX8MP TEZI # print
arch=arm
baudrate=115200
board=verdin-imx8mp
board_name=verdin-imx8mp
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf}
boot_file=Image
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot-tezi.scr
boot_scripts=boot-tezi.scr
boot_syslinux_conf=extlinux/extlinux.conf
boot_targets=mmc1 mmc2 usb0 dhcp
bootcmd=run distro_bootcmd
bootcmd_dhcp=setenv devtype dhcp; run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00011:UNDI:003000;setenv bootp_arch 0xb;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci;
bootcmd_mfg=fastboot 0
bootcmd_mmc1=devnum=1; run mmc_boot
bootcmd_mmc2=devnum=2; run mmc_boot
bootcmd_usb0=devnum=0; run usb_boot
bootcount=1
bootdelay=1
bootfstype=ext4
carrier_serial#=12929231
console=ttymxc2
cpu=armv8
devtype=dhcp
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
efi_dtb_prefixes=/ /dtb/ /dtb/current/
eth1addr=00:14:2d:95:5c:69
ethact=ethernet@30be0000
ethaddr=00:14:2d:85:5c:69
ethprime=eth0
fastboot_dev=mmc2
fdt_addr_r=0x44000000
fdt_board=dev
fdtcontroladdr=bdbf7400
fdtfile=imx8mp-verdin-wifi-dev.dtb
initrd_addr=0x43800000
initrd_high=0xffffffffffffffff
ipaddr=192.168.10.2
kernel_addr_r=0x40000000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile}
loadaddr=0x44500000
mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi
netmask=255.255.255.0
preboot=setenv fdtfile imx8mp-verdin-${variant}-${fdt_board}.dtb
ramdisk_addr_r=0x47400000
rootpath=/srv/nfs
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist
scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootaa64.efi; then echo Found EFI removable media binary efi/boot/bootaa64.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x47000000
serial#=08739945
serverip=192.168.10.1
setup=setenv setupargs console=tty1 console=${console},${baudrate} consoleblank=0 earlycon
soc=imx8m
soc_type=imx8mp
update_uboot=askenv confirm Did you load imx-boot (y/N)?; if test "$confirm" = "y"; then setexpr blkcnt ${filesize} + 0x1ff && setexpr blkcnt ${blkcnt} / 0x200; mmc dev 2 1; mmc write ${loadaddr} 0x0 ${blkcnt}; fi
usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi
variant=wifi
vendor=toradex

Environment size: 4294/8188 bytes
Verdin iMX8MP TEZI #

I tried to follow the second point you suggested, but it doesn’t work.
This is the result of the command above:

Verdin iMX8MP TEZI # run mmc1_boot
## Error: "mmc1_boot" not defined
Verdin iMX8MP TEZI # run distro_bootcmd
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
** Bad device specification dhcp 1 **
switch to partitions #0, OK
mmc2(part 0) is current device
** Bad device specification dhcp 2 **

Device 0: unknown device
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded; starting again
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded; starting again
Verdin iMX8MP TEZI #

ToradexAI · April 8, 2026, 2:50pm

Looking at your U-Boot environment, I can see the issue. Your system is correctly configured but the DHCP boot is failing because it can’t reach the TFTP server. Let me provide the correct steps to force SD card boot.

Direct SD Card Boot Commands

Since your environment shows bootcmd_mmc1=devnum=1; run mmc_boot, try these commands at the U-Boot prompt:

setenv devnum 1
run mmc_boot

(1)

If that doesn’t work, try manually scanning the SD card:

mmc dev 1
fatls mmc 1:1

Check SD Card Content

First, verify your SD card has the correct TEZI files:

mmc dev 1
fatls mmc 1:1

You should see files like boot-tezi.scr, image.json, and other TEZI components.

Alternative Boot Method

If the SD card contains the proper TEZI files, try loading the boot script directly:

mmc dev 1
load mmc 1:1 ${scriptaddr} boot-tezi.scr
source ${scriptaddr}

(1)

Network Configuration Issue

Your environment shows:

serverip=192.168.10.1
But your DHCP assigns IP 192.168.55.6 with gateway 192.168.55.1

This network mismatch is why TFTP fails. If you want to use network boot with TorizonCore Builder’s serve command (2), ensure your PC running the serve command is accessible from the module’s network.

Reset Boot Order

To prioritize SD card boot, modify the boot targets:

setenv boot_targets "mmc1 mmc2 usb0"
saveenv
reset

(1)

This removes dhcp from the boot sequence entirely, forcing the system to try SD card first.

Try the direct mmc_boot command first, then check if your SD card contains the proper TEZI files. The network boot attempts are failing because of the IP address mismatch between your DHCP-assigned address and the configured TFTP server.

Best regards, Toradex AI Assistant.

Did you like my answer?

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

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

fmolon · April 8, 2026, 2:54pm

@ToradexAI ,

this is the result of the command above

Retry time exceeded; starting again
Verdin iMX8MP TEZI # setenv devnum 1
Verdin iMX8MP TEZI # run mmc_boot
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
** Bad device specification dhcp 1 **
Verdin iMX8MP TEZI # mmc dev 1
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Verdin iMX8MP TEZI # fatls mmc 1:1
** Invalid partition 1 **
Verdin iMX8MP TEZI # mmc dev 1
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Verdin iMX8MP TEZI # load mmc 1:1 ${scriptaddr} boot-tezi.scr
** Invalid partition 1 **
Verdin iMX8MP TEZI # source ${scriptaddr}
## Executing script at 47000000
Wrong image format for "source" command
Verdin iMX8MP TEZI # mmc dev 1
Run CMD11 1.8V switch
switch to partitions #0, OK
mmc1 is current device
Verdin iMX8MP TEZI # load mmc 1:1 ${scriptaddr} boot-tezi.scr
** Invalid partition 1 **
Verdin iMX8MP TEZI # source ${scriptaddr}
## Executing script at 47000000
Wrong image format for "source" command

ToradexAI · April 8, 2026, 2:54pm

The “Invalid partition 1” error indicates that your SD card doesn’t have the expected partition structure for TEZI. Let’s diagnose the SD card structure and fix this issue.

Check SD Card Partition Structure

First, let’s examine what partitions exist on your SD card:

mmc info
mmc part

This will show you the actual partition layout. TEZI typically expects specific partitions.

Check Different Partition Numbers

Since partition 1 is invalid, try checking what partitions exist:

fatls mmc 1:0

Or try partition 2:

fatls mmc 1:2

Verify SD Card Detection

Check if the SD card is properly detected:

mmc list
mmc rescan
mmc info

Alternative: Check Boot Files Location

TEZI boot files might be on a different partition. Try:

ext4ls mmc 1:1
ext4ls mmc 1:2

SD Card Recreation

If the partition structure is incorrect, you may need to recreate your TEZI SD card. The issue suggests that either:

The SD card wasn’t properly flashed with TEZI 7.5.0
The partition table is corrupted
The SD card has hardware issues

Manual Boot Script Load

If you find the correct partition with boot files, try:

load mmc 1:X ${scriptaddr} boot-tezi.scr
source ${scriptaddr}

Replace X with the correct partition number you find.

Network Boot Alternative

Since your SD card appears to have issues, you can use your TorizonCore Builder serve command (1). Fix the network configuration:

setenv serverip 192.168.55.1
saveenv
reset

This sets the TFTP server to your gateway address, which should be reachable from your module.

The root cause appears to be that your TEZI SD card doesn’t have the proper partition structure. I recommend recreating the TEZI SD card or using a different SD card to rule out hardware issues.

Best regards, Toradex AI Assistant.

Did you like my answer?

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

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

fmolon · April 8, 2026, 3:01pm

@ToradexAI,

how do i reset the boot env?

ToradexAI · April 8, 2026, 3:02pm

To reset the U-Boot environment variables to their default values, use the following commands in the U-Boot console (1):

Reset Environment to Defaults

env default -a
saveenv

(1)

This will:

env default -a - Restores all environment variables to their default values (1)
saveenv - Makes the changes permanent by saving them to flash memory (1)

Important Notes

Writing variables only changes the RAM representation (2). When you use setenv and printenv in the U-Boot console, you’re working with the RAM copy of the environment. Changes made with setenv are only valid for the current U-Boot session (2).

To make changes persistent, you must use saveenv to write the entire environment to the preconfigured non-volatile location (2). After this procedure, there’s a valid image of the environment on non-volatile memory and the default environment is not recalled anymore (2).

Complete Reset Process

env default -a
## Resetting to default environment
saveenv
Saving Environment to MMC...
Writing to MMC(0)... done

(1)

After running these commands and rebooting your system, all U-Boot environment variables will be restored to their factory default values. This should resolve any configuration issues that might be preventing proper boot behavior.

Best regards, Toradex AI Assistant.

Did you like my answer?

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

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

fmolon · April 8, 2026, 3:08pm

@ToradexAI,

I tried to boot using DHCP. I set the IP address of the server to 192.168.55.43, and it is reachable. I started the Torizon Core Build server, but no kind of procedure is started.

Verdin iMX8MP TEZI # ping 192.168.55.43
Using ethernet@30bf0000 device
host 192.168.55.43 is alive

and

BOOTP broadcast 2
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 224
*** Unhandled DHCP Option in OFFER/ACK: 42
*** Unhandled DHCP Option in OFFER/ACK: 224
DHCP client bound to address 192.168.55.6 (269 ms)
Using ethernet@30bf0000 device
TFTP from server 192.168.55.43; our IP address is 192.168.55.6
Filename 'boot-tezi.scr'.
Load address: 0x47000000
Loading: T T T T T T

fmolon · April 8, 2026, 3:12pm

@ToradexAI,

Is there a way to reset the device to factory settings?

ToradexAI · April 8, 2026, 3:12pm

I can see two issues here: the TFTP server setup and the factory reset question. Let me address both.

TFTP Boot Issue

The TFTP loading is timing out with “T T T T T T” which indicates the server is reachable but not serving the expected file. For TorizonCore Builder’s serve command, you need to ensure:

Set the correct server IP in U-Boot:

setenv serverip 192.168.55.43
saveenv

Verify TorizonCore Builder is serving properly:
Make sure you’re running the serve command correctly and that it’s serving the right files for TEZI boot.
Check the boot script location:
Your system is looking for boot-tezi.scr but TorizonCore Builder might serve different files. The TFTP timeout suggests the file isn’t available at the expected path.

Factory Reset Options

Yes, there are several ways to reset your Verdin iMX8MP to factory settings:

Option 1: Recovery Mode (Recommended)

You can enter recovery mode to reload the Toradex Easy Installer (1). This involves:

Power off your module
Enter recovery mode following the specific steps for your hardware setup
Load the Easy Installer via USB OTG interface
Use the Easy Installer to flash a fresh image

Option 2: U-Boot Environment Reset

Reset the U-Boot environment to defaults (which we discussed earlier):

env default -a
saveenv

(2)

Option 3: Complete Reflash

If you have access to the Toradex Easy Installer, you can completely wipe and reinstall the system. The Easy Installer allows you to install OS images either from online sources or from external media like SD cards (3).

Recommended Next Steps

Given your current situation, I recommend:

Try recovery mode to load a fresh TEZI instance
Use a properly prepared SD card with TEZI 7.5.0 (recreate it if the current one has partition issues)
If network boot is essential, verify that your TorizonCore Builder serve command is correctly configured for TEZI boot files

The recovery mode approach will give you a clean slate to work with, bypassing any current configuration issues.

Best regards, Toradex AI Assistant.

Did you like my answer?

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

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

fmolon · April 8, 2026, 3:14pm

@ToradexAI
i don’t see start tezi from shell and hdmi output.

ToradexAI · April 8, 2026, 3:15pm

I understand you’re not seeing TEZI start from shell and there’s no HDMI output. This suggests multiple issues that need to be addressed systematically.

Troubleshooting No TEZI Display

1. Check Boot Process Status

First, verify if TEZI is actually starting but just not displaying. At the U-Boot prompt, check what’s happening during boot:

printenv bootcmd
run bootcmd

(1)

2. Manual TEZI Boot Attempt

Since your SD card has partition issues, try forcing a manual boot sequence:

mmc list
mmc dev 1
mmc info

3. HDMI Output Configuration

Your Verdin iMX8MP with Mallow carrier board should support HDMI output. The lack of display could be due to:

Display configuration issues - TEZI might not be detecting your HDMI display properly
Boot process not reaching display initialization
Hardware connection issues

4. Recovery Mode Approach

Given the persistent issues with both SD card boot and network boot, I strongly recommend entering recovery mode to reload TEZI completely. This will:

Bypass any corrupted U-Boot environment issues (1)
Provide a fresh TEZI installation
Reset any display configuration problems

5. Alternative Boot Methods

If the standard boot methods continue to fail, you can try:

Network Boot with Proper Configuration:

setenv serverip 192.168.55.43
setenv bootcmd_dhcp "dhcp; tftp ${loadaddr} boot.scr; source ${loadaddr}"
saveenv
boot

(1)

6. Check for Hardware Issues

The combination of:

SD card partition detection failure
Network boot timeouts
No HDMI output
Incorrect carrier board detection in U-Boot

Suggests there might be hardware-level issues with either the module or carrier board connections.

Immediate Next Steps

Try recovery mode - This is your most reliable path to get TEZI running
Test with a different SD card - Rule out SD card hardware issues
Verify HDMI cable and display - Test with known working display setup
Check carrier board connections - Ensure the module is properly seated

The fact that you’re getting U-Boot output but no TEZI display indicates the boot process is failing before TEZI’s GUI initializes.

Best regards, Toradex AI Assistant.

Did you like my answer?

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

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

collin.tx · April 14, 2026, 10:52am

Dear @fmolon,

I understand you were able to recover and reflash the module, correct?
Could you maybe elaborate on what your precise intent is and if there is something I could help you with?

As a quick sidenote I would like to mention the following developer page:
https://developer.toradex.com/easy-installer/toradex-easy-installer/loading-toradex-easy-installer/?module=verdin_imx8mp&carrier=mallow#start

Best regards,
Collin