SMARC iMX95 v1.2B with Easy Installer 7.7.0

Technical Support
1

Hi,

I have MARC Development Board with HDMI Adapter V1.1B and SMARC iMX95 Hexa 8GB Wi-Fi/Bluetooth IT V1.0A and a DP monitor. I had Torizon 7.3.0 installed using Easy Installer 7.3.0 without any problem.

I then got a new SMARC module SMARC iMX95 Hexa 8GB Wi-Fi/Bluetooth IT V1.2B. I use that module with the same development board and Easy Installer 7.7.0 build 13. For the very first boot to Easy Installer, everything was OK and it loaded Torizon 7.6.0 successful and it asked me to reboot. After reboot, the OS did not load (confirm by checking Ethernet connection to DHCP server).

After that I tried to load Easy Installer (recovery mode) again but nothing came up on the DP monitor and on DHCP server’s client’s list.

What could be the problem? any help is appreciated.

Thank you.

Regards,

Aaron

2

Hi, I’m the Toradex AI Assistant.

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

Based on the information available, there are several important considerations for your SMARC iMX95 V1.2B module issue:

Key Hardware Differences

Your new SMARC iMX95 V1.2B module includes significant changes from the V1.0A version you previously used. According to the revision history, V1.2B incorporates:

  • Updated embedded controller firmware to improve RESET_IN# and CARRIER_PWR_ON signal behavior(1)
  • Mass production version industrial-temperature qualified SoC and PMIC components from NXP(1)

Display Connection Requirements

HDMI hotplug is not supported on Toradex modules. You must connect the display/monitor to the carrier board before power on(2). This is critical - if the monitor isn’t connected and powered on before booting, the system won’t detect it.

Troubleshooting Steps

  1. Verify Display Connection: Ensure your DP monitor is connected and powered on before applying power to the development board(2)

  2. Enter Recovery Mode Properly: Follow the specific recovery mode procedure for SMARC iMX95 and SMARC Development Board(2). The recovery process may cause multiple device detections, and downloading can sometimes get stuck(2)

  3. Serial Console Access: Connect to the serial debug UART to verify if the system is actually booting even without display output(2). This will help determine if the issue is display-related or a boot failure.

  4. Check Software Compatibility: The V1.2B module should be compatible with Easy Installer 7.7.0 and Torizon 7.6.0, but verify you’re using the correct recovery image for your specific hardware version.

If recovery mode still doesn’t show output, try accessing the system via serial console to check boot logs and confirm whether the module is actually entering recovery mode successfully.

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.

3

Hi,

There is nothing on serial debug UART when v1.2B module was installed.

DP monitor and serial debug UART worked with v1.0A module.

Here was the output when running recovery-windows.bat with new module v1.2B:

uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.233 Success 0 Failure 0 1:112-80BD9D 1/1 [================100%================] SDPS: boot -f ../imx-boot-recoverytezi

Thank you.

Regards,

Aaron

4

Based on your description, the recovery process appears to complete successfully (Success 0 Failure 0 and 100% progress), but you’re getting no output on either the serial debug UART or the DP monitor afterward. This suggests the Easy Installer image may have loaded into RAM but isn’t booting properly on the V1.2B module.

Serial Console Configuration

First, verify your serial console setup matches the requirements for the SMARC Development Board. The serial console parameters should be(1):

  • Baud Rate: 115200
  • Parity: none
  • Bits: 8
  • Stop bits: 1
  • Flow control: none

For the SMARC Development Board, you should connect a USB C to USB Type-A cable to connector J27(1). The board has an integrated Serial-to-USB converter that lists 4 serial ports on your computer, and the highest index is the serial console(1). For example, if you see /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2, and /dev/ttyUSB3, then /dev/ttyUSB3 is the serial console(1).

Potential Hardware Version Issue

Your V1.2B module may have compatibility differences that aren’t fully addressed in Easy Installer 7.7.0. According to the Product Change Notification, there were significant changes between V1.0A and V1.1A that affected software support(2). While V1.2B isn’t explicitly mentioned in the available documentation, it’s possible similar compatibility considerations apply.

Recommended Actions

  1. Verify Serial Port Selection: Confirm you’re connected to the correct serial port (the highest numbered one)(1)
  2. Check Serial Console Before Recovery: Connect the serial console and verify you can see U-Boot output with the V1.0A module first to confirm your setup is correct
  3. Try Different Recovery Image Version: Consider testing with Easy Installer 7.3.0 (which worked with V1.0A) to see if there’s a version-specific compatibility issue
  4. Contact Toradex Support: Since you have a newer hardware revision (V1.2B) that may not be fully documented yet, I recommend reaching out through the Toradex Community or GitHub for specific guidance on V1.2B compatibility

The lack of any serial output suggests the module may not be booting at all after the recovery image loads, which could indicate a hardware revision compatibility issue with the recovery image version.

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.

5

I just tried Easy Installer nightly pre-release 7.8.0 and it worked.

6

However, the latest Torizon 7.7.0 did not worked. Below is the output from debug port. It stopped after loading OS and reboot.

U-Boot SPL 2024.04-7.8.0-devel+git.b7c747d8c084 (Sep 04 2026 - 16:19:18 +0000)
SOC: 0xb0009500
LC: 0x40010
Trying to boot from USB SDP
Failed to configure default pinctrl
UID: 80bd9ddb0a344f3cab420f67f2c030ce
SDP: initialize…
SDP: handle requests…
Downloading file of size 1644544 to 0x90400000… done
Jumping to header at 0x90400000
Header Tag is not an IMX image
Found header at 0x90400000
NOTICE: BL31: v2.10.0 (release):lf-6.6.52-2.2.1-dirty
NOTICE: BL31: Built : 06:40:36, Jul 7 2025

U-Boot 2024.04-7.8.0-devel+git.b7c747d8c084 (Sep 04 2026 - 16:19:18 +0000)

CPU: i.MX95 rev2.0 at 1800MHz
CPU: Industrial temperature grade (-40C to 105C) at 42C
LM Boot reason: por, origin: -1, errid: -1
LM shutdown reason: por, origin: -1, errid: -1
DRAM: 7.8 GiB
Core: 319 devices, 32 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 0096 SMARC iMX95 Hexa 8GB WB IT V1.2B
Serial#: 08968038

BuildInfo:

  • SM firmware Build 571, Commit f0911787, Sep 14 2026 22:53:19
  • ELE firmware version 2.0.5-fe6641ef

Detect USB boot. Will enter fastboot mode!
Net: WARNING: no MAC address assigned for MAC0
imx_get_mac_from_fuse: fuse read err: 0
eth0: enetc-0 [PRIME]WARNING: no MAC address assigned for MAC1
imx_get_mac_from_fuse: fuse read err: 0
, eth1: enetc-1WARNING: no MAC address assigned for MAC2
imx_get_mac_from_fuse: fuse read err: 0

Warning: enetc-2 (eth2) using random MAC address - de:39:c4:11:6a:ac
, eth2: enetc-2
Fastboot: Normal
Boot from USB for uuu
Hit any key to stop autoboot: 0
Failed to configure default pinctrl
Starting download of 2248 bytes

downloading of 2248 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 209 bytes

downloading of 209 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 40022487 bytes
…
…
…
…
…
downloading of 40022487 bytes finished

Executing script at 9c600000

Bootargs: video=DP-1:1280x720@60D console=ttyLP1,115200 quiet rootfstype=squashfs root=/dev/ram autoinstall

Loading kernel from FIT Image at 90400000 …

Using ‘conf-freescale_imx95-toradex-smarc-dev.dtb’ configuration
Trying ‘kernel-1’ kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x904000fc
Data Size: 7830659 Bytes = 7.5 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x94400000
Entry Point: 0x94400000
Hash algo: sha256
Hash value: 721c9160f899f58db0de3bf2490b2827683cad271e630c7df338965ce420a2fd
Verifying Hash Integrity … sha256+ OK

Loading ramdisk from FIT Image at 90400000 …

Using ‘conf-freescale_imx95-toradex-smarc-dev.dtb’ configuration
Trying ‘ramdisk-1’ ramdisk subimage
Description: tezi-initramfs
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x90b9cfd4
Data Size: 32034816 Bytes = 30.6 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x9e800000
Entry Point: unavailable
Hash algo: sha256
Hash value: 0f5bafd1cdf2fe2c82e9cc687e82f867160b2e315dcd5beadd5fd08e95184f79
Verifying Hash Integrity … sha256+ OK
Loading ramdisk from 0x90b9cfd4 to 0x9e800000

Loading fdt from FIT Image at 90400000 …

Using ‘conf-freescale_imx95-toradex-smarc-dev.dtb’ configuration
Trying ‘fdt-freescale_imx95-toradex-smarc-dev.dtb’ fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x90b77ea8
Data Size: 101636 Bytes = 99.3 KiB
Architecture: AArch64
Load Address: 0x9c400000
Hash algo: sha256
Hash value: ea9d71b21c7dadfc003a6a9f149049788c800deb4531e502596c15ed6a9f640b
Verifying Hash Integrity … sha256+ OK
Loading fdt from 0x90b77ea8 to 0x9c400000

Loading fdt from FIT Image at 90400000 …

Using ‘conf-toradex-smarc-imx95_spi0-cs0_spidev_overlay.dtbo’ configuration
Trying ‘fdt-toradex-smarc-imx95_spi0-cs0_spidev_overlay.dtbo’ fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x90b9a2a0
Data Size: 557 Bytes = 557 Bytes
Architecture: AArch64
Load Address: 0x9c440000
Hash algo: sha256
Hash value: 1a0d95c31dd950c895689fbac3fd7522afa3f5418a4e417bab1a31ab3d35bcb1
Verifying Hash Integrity … sha256+ OK

Loading fdt from FIT Image at 90400000 …

Using ‘conf-toradex-smarc-imx95_spi0-cs1_spidev_overlay.dtbo’ configuration
Trying ‘fdt-toradex-smarc-imx95_spi0-cs1_spidev_overlay.dtbo’ fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x90b9a5e0
Data Size: 557 Bytes = 557 Bytes
Architecture: AArch64
Load Address: 0x9c440000
Hash algo: sha256
Hash value: adbe8c7b152f096aa3be779abeafb4621496876a9d7c562c9586bb39217d6f7c
Verifying Hash Integrity … sha256+ OK

Loading fdt from FIT Image at 90400000 …

Using ‘conf-toradex-smarc-imx95_spi1-cs0_spidev_overlay.dtbo’ configuration
Trying ‘fdt-toradex-smarc-imx95_spi1-cs0_spidev_overlay.dtbo’ fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x90b9a920
Data Size: 530 Bytes = 530 Bytes
Architecture: AArch64
Load Address: 0x9c440000
Hash algo: sha256
Hash value: ecbb9bd3d53190acbaec1e8ac4c510c70b833cb5feae0050c450e93782ddf333
Verifying Hash Integrity … sha256+ OK

Loading fdt from FIT Image at 90400000 …

Using ‘conf-toradex-smarc-imx95_spi1-cs1_spidev_overlay.dtbo’ configuration
Trying ‘fdt-toradex-smarc-imx95_spi1-cs1_spidev_overlay.dtbo’ fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x90b9ac44
Data Size: 530 Bytes = 530 Bytes
Architecture: AArch64
Load Address: 0x9c440000
Hash algo: sha256
Hash value: 8bbbdabe93075fc9aac41c8b03aff9012ea05b45f785a2294270eafa1d6b3880
Verifying Hash Integrity … sha256+ OK
Booting using the fdt blob at 0x9c400000
Working FDT set to 9c400000
Uncompressing Kernel Image to 94400000
Loading Ramdisk to fb053000, end fcee0000 … OK
Loading Device Tree to 00000000fb037000, end 00000000fb052e43 … OK
Working FDT set to fb037000

Starting kernel …

[ 0.127677] cpu cpu0: EM: invalid power: 0
[ 0.200222] fsl_enetc_mdio 0003:01:00.0: Cannot get IERB init status: -517
[ 0.200329] pcieport 0003:01:01.0: of_irq_parse_pci: failed with rc=-22
[ 0.268580] rtc-ds1307 3-0032: hctosys: unable to read the hardware clock
[ 0.431350] debugfs: Directory ‘wakeup’ with parent ‘pm_genpd’ already present!
[ 0.438674] debugfs: Directory ‘vpu’ with parent ‘pm_genpd’ already present!
[ 0.445723] debugfs: Directory ‘npu’ with parent ‘pm_genpd’ already present!
[ 0.452763] debugfs: Directory ‘noc’ with parent ‘pm_genpd’ already present!
[ 0.459822] debugfs: Directory ‘m7’ with parent ‘pm_genpd’ already present!
[ 0.466817] debugfs: Directory ‘gpu’ with parent ‘pm_genpd’ already present!
Running /etc/rc.local…
Toradex Easy Installer 7.8.0-devel-20260917+build.611 ()
Starting udev
[ 3.278779] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 3.288028] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 3.859044] mdio_bus 0002:00:10.0-imdio:10: Polling timeout, line: 381
[ 3.875592] fsl_enetc4 0002:00:10.0: cannot create xpcs mdiodev (-19)
[ 3.882275] fsl_enetc4 0002:00:10.0: Failed to create MDIO bus
[ 4.229768] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 4.238930] debugfs: File ‘:soc:display-controller@4b400000’ in directory ‘domains’ already present!
[ 4.435207] imx95-pixel-interleaver 4b0d0000.bridge: Failed to create device link (0x180) with 4b400000.display-controller
[ 4.453647] usbmisc_imx 4c200200.usbmisc: vbus is error
[ 4.458926] usbmisc_imx 4c200200.usbmisc: Error occurs during detection: -22
System time was Thu Jan 1 00:00:05 UTC 1970.
Setting the System Clock using the Hardware Clock as reference…
hwclock: RTC_RD_TIME: Invalid argument
System Clock set. System local time is now Thu Jan 1 00:00:05 UTC 1970.
Fri Mar 9 12:34:56 UTC 2018
Saving the System Clock time to the Hardware Clock…
Hardware Clock updated to Fri Mar 9 12:34:56 UTC 2018.

Welcome to the Toradex Easy Installer

This is a Linux based installer for Toradex modules. Currently, the installer
does not have a serial console interface. You can use the Toradex Easy Installer
via any of the available display interfaces using USB mouse/keyboard or via a
network connection using VNC. Use:

ip addr show

to display the Ethernet IP address(es) or use USB NCM at IP 192.168.11.1.

Check our documentation at:

~ # [ 175.393032] reboot: Restarting system

7

Hi @apham!

The SMARC iMX95 V1.0A uses the old silicon revision (A1). Because of this, the latest versions of Torizon OS and the Toradex Easy Installer will not work on this module, as explained in the i.MX 95 A1 to B0 Silicon Revision Update Guide article.

To ensure full hardware and software support, we recommend migrating to a newer version of the module (V1.2A in your case).

Best regards.

8

Hi Lucas, thank you for your reply.

As mentioned above I got The SMARC iMX95 V1.0A worked with Easy Installer 7.3.0 and Torizon OS 7.3.0 without any problem.

I just got SMARC iMX95 Hexa 8GB Wi-Fi/Bluetooth IT V1.2B and so far it only worked with the pre-release Easy Installer 7.8.0 and Torizon OS 7.8.0.

Toradex’s roadmap specifically lists ELB-7175, “Add support for i.MX95 SoC M-parts”, for SMARC iMX95 in BSP 7.8.0.