hello,
I have this configuration : Mallow Carrier Board + Verdin iMX8M Plus
I have a problem!
When entering the recovery mode i have video output only for a few seconds than black screen and no video signal (HDMI output);
sometimes i see the window with all the items available, i select one linux versions and then click install, i wait for the next screen - i click I agreee then black screen - no video signal;
sometime i only see the window - status - refreshing items and then black screen - no video signal
On debug console :
"Welcome to the Toradex Easy Installer
This is a Linux based installer for Toradex modules. Current
does not have a serial console interface. You can use the To
via any of the available display interfaces using USB mouse/
network connection using VNC. Use:
# ip addr show
to display the Ethernet IP address(es) or use USB NCM at IP
Check our documentation at:
https://developer.toradex.com/software/toradex-easy-instal
/ #
"
Console not responding !
Can’t connect using VNC (linux or windows);
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
I’m sorry to hear about the difficulties you’re experiencing with the HDMI output on your Mallow Carrier Board and Verdin iMX8M Plus. Let’s try a few steps to troubleshoot and resolve this issue:
Check HDMI Connection: Ensure that the HDMI cable is securely connected to both the carrier board and the display. If possible, try using a different HDMI cable or port to rule out any connection issues.
Access Serial Console: Since the console is unresponsive, try accessing the Toradex Easy Installer’s shell via the serial console on UART1/UART_A. This can provide more detailed information about the recovery process.
Review Log Files: Examine the log file located at /var/volatile/tezi.log for any error messages or clues about the video output issue. Use the cat command to view the log contents.
Restart the UI: If the user interface is not responding, you can manually restart it. This might help regain control over the installation process.
Update Toradex Easy Installer: Ensure you are using the latest version of the Toradex Easy Installer, as updates may include fixes for known issues.
VNC Connection: If HDMI issues persist, try connecting to the Toradex Easy Installer via VNC. Verify your network settings and ensure you can access the device’s IP address.
These steps should help you diagnose and potentially resolve the HDMI output issue during recovery mode. If the problem continues, further investigation into the software configuration may be necessary.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
U-Boot 2022.04-6.7.0+git.7588eb559ca2 (May 28 2024 - 11:19:14 +0000)
CPU: i.MX8MP[6] rev1.1 1600 MHz (running at 1200 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 37C
Reset cause: POR
DRAM: 2 GiB
Core: 89 devices, 23 uclasses, devicetree: separate
WDT: Started watchdog@30280000 with servicing (60s timeout)
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In: serial
Out: serial
Err: serial
Model: Toradex 0064 Verdin iMX8M Plus Quad 2GB WB IT V1.1A
Serial#: 15336792
MISSING TORADEX CARRIER CONFIG BLOCKS
SEC0: RNG instantiated
BuildInfo:
- ATF 3c1583b
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
MMC: no card present
switch to partitions #0, OK
mmc2(part 0) is current device
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
ethernet@30bf0000 Waiting for PHY auto negotiation to complete....... done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.0.184 (260 ms)
Using ethernet@30bf0000 device
TFTP from server 192.168.0.1; our IP address is 192.168.0.184
Filename 'boot.scr'.
Load address: 0x50280000
U-Boot 2022.04-6.8.0+git.a1eb18d157f4 (Jul 16 2024 - 20:38:08 +0000)
CPU: i.MX8MP[6] rev1.1 1600 MHz (running at 1200 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 38C
Reset cause: POR
DRAM: 2 GiB
Core: 89 devices, 23 uclasses, devicetree: separate
WDT: Started watchdog@30280000 with servicing (60s timeout)
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from nowhere... OK
In: serial
Out: serial
Err: serial
Model: Toradex 0064 Verdin iMX8M Plus Quad 2GB WB IT V1.1A
Serial#: 15336792
MISSING TORADEX CARRIER CONFIG BLOCKS
SEC0: RNG instantiated
BuildInfo:
- ATF 3c1583b
Setting variant to wifi
Detect USB boot. Will enter fastboot mode!
Net: eth1: ethernet@30be0000, eth0: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Boot from USB for uuu
Hit any key to stop autoboot: 0
Detect USB boot. Will enter fastboot mode!
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
Starting download of 1888 bytes
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
downloading of 1888 bytes finished
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
Detect USB boot. Will enter fastboot mode!
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
Starting download of 118 bytes
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
downloading of 118 bytes finished
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
Detect USB boot. Will enter fastboot mode!
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
Starting download of 44775628 bytes
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
..........................................................................
..........................................................................
..........................................................................
..........................................................................
.............................................
downloading of 44775628 bytes finished
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
(NULL udevice *): request 00000000bfb473c0 was not queued to ep1in-bulk
## Executing script at 42e00000
Bootargs: quiet edid/1280x720.bin video=HDMI-A-1:1280x720-16@60D video=HDMI-A-2:1280x720-16@60D initcall_blacklist=vpu_driver_init rootfstype=squashfs root=/dev/ram autoinstall clk_ignore_unused pci=nomsi
## Loading kernel from FIT Image at 44200000 ...
Using 'conf-freescale_imx8mp-verdin-wifi-dev.dtb' configuration
Trying 'kernel-1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x44200108
Data Size: 9940294 Bytes = 9.5 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x48200000
Entry Point: 0x48200000
Hash algo: sha256
Hash value: 38f6b71c3f27a9ad7f657b54aaa559ad54a96e0a417354fefefd7d713e05e7fc
Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 44200000 ...
Using 'conf-freescale_imx8mp-verdin-wifi-dev.dtb' configuration
Trying 'ramdisk-1' ramdisk subimage
Description: tezi-initramfs
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x44c35d64
Data Size: 34062336 Bytes = 32.5 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x52300000
Entry Point: unavailable
Hash algo: sha256
Hash value: e479e4bad3932d21273593db30ec31e77d487f1d5b29266daab7beef58e04666
Verifying Hash Integrity ... sha256+ OK
Loading ramdisk from 0x44c35d64 to 0x52300000
## Loading fdt from FIT Image at 44200000 ...
Using 'conf-freescale_imx8mp-verdin-wifi-dev.dtb' configuration
Trying 'fdt-freescale_imx8mp-verdin-wifi-dev.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x44be9224
Data Size: 90278 Bytes = 88.2 KiB
Architecture: AArch64
Load Address: 0x50200000
Hash algo: sha256
Hash value: 056df943ff904fdf2bfa5439d13f48092caf2da03c7935101de54019444855b6
Verifying Hash Integrity ... sha256+ OK
Loading fdt from 0x44be9224 to 0x50200000
## Loading fdt from FIT Image at 44200000 ...
Using 'conf-verdin-imx8mp_hdmi_overlay.dtbo' configuration
Trying 'fdt-verdin-imx8mp_hdmi_overlay.dtbo' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x44c2e8d8
Data Size: 2219 Bytes = 2.2 KiB
Architecture: AArch64
Load Address: 0x50240000
Hash algo: sha256
Hash value: c4ec36638c7d6bff0af64735d0a5a71acf2a1041b7de69bca1dd1a1ca25b8112
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 44200000 ...
Using 'conf-verdin-imx8mp_dsi-to-hdmi_overlay.dtbo' configuration
Trying 'fdt-verdin-imx8mp_dsi-to-hdmi_overlay.dtbo' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x44c2b444
Data Size: 3652 Bytes = 3.6 KiB
Architecture: AArch64
Load Address: 0x50240000
Hash algo: sha256
Hash value: 2afe82462f32ab9d163b816bfd8ae4071a7f48a9382fb545b4feede3bc93598e
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 44200000 ...
Using 'conf-verdin-imx8mp_spidev_overlay.dtbo' configuration
Trying 'fdt-verdin-imx8mp_spidev_overlay.dtbo' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x44c35a58
Data Size: 561 Bytes = 561 Bytes
Architecture: AArch64
Load Address: 0x50240000
Hash algo: sha256
Hash value: a18be5d8a83083491c21b8de76d20e403b0ba28685fce6b628e196f46b1924d2
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x50200000
Uncompressing Kernel Image
Loading Device Tree to 00000000bfae2000, end 00000000bfafb4a6 ... OK
Modify /vipsi@38500000:status disabled
Starting kernel ...
[ 0.307105] rtc-ds1307 0-0032: hctosys: unable to read the hardware clock
[ 0.317857] pca953x 3-0021: failed writing register
[ 0.373677] clk: failed to reparent hsio_axi to sys_pll2_500m: -16
[ 0.383921] clk: failed to reparent hsio_axi to sys_pll2_500m: -16
Running /etc/rc.local...
Toradex Easy Installer 6.8.0+build.8 ()
Starting udev
[ 1.192847] ina2xx 3-0040: error configuring the device: -6
System time was Thu Jan 1 00:00:01 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:01 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:
https://developer.toradex.com/software/toradex-easy-installer
/ #
If you’re facing display issues, I recommend trying different HDMI cables and displays. The problem could stem from an HDMI mismatch between the Verdin iMX8M Plus HDMI output and your display. Potential factors include:
I’m using the latest version of Toradex easy installer image.
If board gives no video signal on connected monitor I can’t access the board using VNC (connection error);
When entering the recovery mode i have video output only for a few seconds than black screen and no video signal (HDMI output);
sometimes i see the window with all the items available, i select one linux versions and then click install, i wait for the next screen - i click I agree then black screen - no video signal;
sometime i only see the window - status - refreshing items and then black screen - no video signal
HDMI cable is fine, I’ve tried tried with a different cable and the same problem.
I’ve found out that the problem is related to UART connector - UART Header (X11)
TTL-232RG-VREG1V8-WE
If the UART header is connected to pc - then i have debug information on debug console but the board can’t stay to much time in the recovery menu - no display signal after recovery menu becomes visible.
If the UART header is NOT connected - i can get acces to recovery menu and chose and full install an OS image.
At first the board worked well in this configuration, after 1-2 weeks of testing the board the problem appeared and it seems strange the even if the board was written with on OS image, when the problem began the board didn’t find any OS image at boot.
I’ve powered on the board without UART connected, the board is OK (I can access the recovery menu and install an OS image and video signal has no problem), then i connect the UART connector.
If the UART connector is connected before power on - problem appears not all the time seems, but if it appears it stays even if i power off the board and try again the same steps.
We bought another 4 pieces of this configuration for developing (Mallow Carrier Board + Verdin iMX8M Plus) and for the moment there is no problem (I’ve tried the same cables on only one piece of board (one of the four) and is working fine).
We used the setup you described before and I can confirm it should work.
I will try to reproduce the issue and get back. Can you provide the Mallow board version and confirm it is the Verdin iMX8M Plus V1.1A?
Meanwhile, I suggest trying to measure the voltage/signals in the UART pins to make sure it is within the limits.
I would also try different Carrier + SoM + Adapter set to eliminate possible damage to the ones presenting the issue.
Hi,
Mallow board version is V1.1A - SN:35699055
Verdin iMX8M Plus is V1.1A - SN:15336792
I’ve measured the voltage/signals in the UART pins and they are in the limits.
For the moment i used the same cable set with 2 boards set and they are working fine, but sometimes the problem occurs with only 1 board (V1.1 A), with V1.1C no problem.
I am glad that you are able to get your setup working. I will mark your post as solution to the topic.
Checking the revision history and erratas for those boards, I saw an errata on early Mallow revisions before V1.1C related to EDID HDMI issues. I don’t know if your problem is related to that. You can check further information on our issue tracker
