Splash screen not appearing on verdin IMx8MP for Torizon 7 with LVDS

[dTanks]

I believe this might be related to TOR-3594

On V6.8.2 with the imx8mp, and with my AM62 module on OS 7.2.0, I get a torizon logo, with a spinning wheel underneath shortly after boot. Something like 30 seconds later, the easy pairing screen comes up.

On v7.2.0 (and 7.1.0) with the imx8mp, there is no display until the easy pairing screen appears.

I have changed the device trees on the devices to use LVDS, and this is definitely working as I get the easy pairing screen after waiting long enough, but the splash screen does not appear. It does momentarily appear when using the reboot command, which as I understand is a different splash process.

OS Info.

torizon@verdin-imx8mp-15459942:~$ sudo tdx-info

Software summary

Bootloader: U-Boot
Kernel version: 6.6.74-7.2.0-devel-g4c3f8e570a39 #1-Torizon SMP PREEMPT Wed Feb 26 11:01:24 UTC 2025
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.0/torizon/cbad4b35beae0cde2e41ca00248a65988576929978d28130a2d3b08b3d9a19f2/0
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.2.0-devel-202503-build.7
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx8mp-15459942

Hardware info

HW model: Toradex Verdin iMX8M Plus on Verdin Development Board
Toradex version: 0063 V1.1B
Serial number: 15459942
Processor arch: aarch64

torizon@verdin-imx8mp-15459942:~$ sudo tdx-info -dt

Device tree

Device tree enabled: imx8mp-verdin-nonwifi-dev.dtb
Compatible string: toradex,verdin-imx8mp-nonwifi-devtoradex,verdin-imx8mp-nonwifitoradex,verdin-imx8mpfsl,imx8mp
Device trees available:
imx8mp-verdin-nonwifi-dahlia.dtb
imx8mp-verdin-nonwifi-dev.dtb
imx8mp-verdin-nonwifi-ivy.dtb
imx8mp-verdin-nonwifi-mallow.dtb
imx8mp-verdin-nonwifi-yavia.dtb
imx8mp-verdin-wifi-dahlia.dtb
imx8mp-verdin-wifi-dev.dtb
imx8mp-verdin-wifi-ivy.dtb
imx8mp-verdin-wifi-mallow.dtb
imx8mp-verdin-wifi-yavia.dtb

Device tree overlays

Overlays enabled: fdt_overlays=verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
Overlays available:
verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_hdmi_overlay.dtbo
verdin-imx8mp_hmp_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_nau8822-btl_overlay.dtbo
verdin-imx8mp_ov5640_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_panel-cap-touch-7inch-dsi_overlay.dtbo
verdin-imx8mp_spidev_overlay.dtbo

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello there!

It seems you’re using the Verdin iMX8M Plus with the LVDS overlay verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo. This is a pre-built device tree overlay for the Verdin iMX8M Plus family. From your kernel command line parameters, I see several display-related flags are set, such as quiet, logo.nologo, and splash.

The issue with the splash screen not appearing during the initial boot but showing up on reboot could be related to the timing of framebuffer initialization with your LVDS display. This is a common consideration when dealing with display initialization.

To troubleshoot, please ensure that your LVDS overlay is applied correctly. You can verify this by using the tdx-info -dt command, which will show your enabled overlays and device tree configuration.

If you need further assistance or a more general explanation about display initialization and splash screens on Toradex modules, feel free to ask!

Best regards, Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Device Tree Overlays on Toradex System on Modules | Toradex Developer Center

Getting Device Information with Tdx-Info | Toradex Developer Center.

[mnano]

Hello,

I stumbled upon this topic because I have the exact same problem. The splash screen does not appear upon boot. However, it does appear when shutting down.

I have a custom board based on the imx8mp and it connects to a touchscreen display using native LVDS connection. When started, the display works without any issues. My custom image has a built-in splash screen which worked on Torizon OS 6.8.2. With Torizon OS 7.2.0 it does not seem to work (built with linux-toradex.git and device-tree-overlays.git version toradex_6.6-2.1.x-imx). I also tried the ostree-customize-plymouth.sh script to no avail ( Splash Screen on Torizon OS | Toradex Developer Center)

Information

• uname -r

6.6.74-7.2.0-devel-g4c3f8e570a39

• tdx-info:

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.74-7.2.0-devel-g4c3f8e570a39 #1-Torizon SMP PREEMPT Wed Feb 26 11:01:24 UTC 2025
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.0/torizon/793698b90d2307a1b8c78e89b562d0fca617905cbd71f6b7a6030895b0eb0a93/0
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.2.0-devel-202503-build.7
Distro variant:           VARIANT="Docker"
Hostname:                 verdin-imx8mp-14772918
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Plus WB on Custom Board
Toradex version:          0058 V1.1A
Serial number:            14772918
Processor arch:           aarch64
------------------------------------------------------------

• tdx-info -dt:

Device tree
------------------------------------------------------------
Device tree enabled:      imx8mp-verdin-wifi-dev.dtb
Compatible string:        toradex,verdin-imx8mp-wifi-customtoradex,verdin-imx8mp-wifitoradex,verdin-imx8mpfsl,imx8mp
Device trees available:
                          imx8mp-verdin-nonwifi-dahlia.dtb
                          imx8mp-verdin-nonwifi-dev.dtb
                          imx8mp-verdin-nonwifi-ivy.dtb
                          imx8mp-verdin-nonwifi-mallow.dtb
                          imx8mp-verdin-nonwifi-yavia.dtb
                          imx8mp-verdin-wifi-custom.dtb
                          imx8mp-verdin-wifi-dahlia.dtb
                          imx8mp-verdin-wifi-dev.dtb
                          imx8mp-verdin-wifi-ivy.dtb
                          imx8mp-verdin-wifi-mallow.dtb
                          imx8mp-verdin-wifi-yavia.dtb
------------------------------------------------------------

Device tree overlays
------------------------------------------------------------
Overlays enabled:         fdt_overlays=verdin-imx8mp_panel-cap-touch-7inch-lvds_overlay.dtbo verdin-imx8mp_spidev_overlay.dtbo verdin-imx8mp_nau8822-btl_overlay.dtbo
Overlays available:
                          verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
                          verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
                          verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
                          verdin-imx8mp_hdmi_overlay.dtbo
                          verdin-imx8mp_hmp_overlay.dtbo
                          verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
                          verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
                          verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
                          verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
                          verdin-imx8mp_nau8822-btl_overlay.dtbo
                          verdin-imx8mp_ov5640_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-7inch-dsi_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-7inch-lvds_overlay.dtbo
                          verdin-imx8mp_spidev_overlay.dtbo
------------------------------------------------------------

• verdin-imx8mp_panel-cap-touch-7inch-lvds_overlay.dts

/dts-v1/;
/plugin/;


#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/pwm/pwm.h>
#include <imx8mp-pinfunc.h>


/ {
	compatible = "toradex,verdin-imx8mp";
};

&{/} {
	backlight_lvds_native: backlight-lvds-native {
		compatible = "pwm-backlight";
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_i2s_2_d_out_dsi_1_bkl_en>;		
		brightness-levels = <0 45 63 88 119 158 203 255>;
		default-brightness-level = <4>;
		/* Verdin I2S_2_D_OUT as GPIO (SODIMM 46) */
		enable-gpios = <&gpio5 1 GPIO_ACTIVE_HIGH>;	
		/* Verdin PWM_2 (SODIMM 16) */
		pwms = <&pwm2 0 6666667 PWM_POLARITY_INVERTED>;
	};

	panel-lvds-native {
		compatible = "panel-lvds";
		backlight = <&backlight_lvds_native>;
		data-mapping = "vesa-24";
		height-mm = <86>;
		width-mm = <154>;
		/* Verdin I2S_2_BCLK as GPIO (SODIMM 42) */
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_i2s_2_bclk_touch_reset>;
		reset-gpios = <&gpio5 0 GPIO_ACTIVE_HIGH>;

		panel-timing {
			clock-frequency = <44900000 51200000 63000000>;
			de-active = <1>;
			hactive = <1024>;
			hback-porch = <160>;
			hfront-porch = <16 160 216>;
            hsync-active = <0>;
			hsync-len = <1 70 140>;
			pixelclk-active = <1>; /* positive edge */
			vactive = <600>;
			vback-porch = <23>;
			vfront-porch = <1 12 127>;
            vsync-active = <0>;
			vsync-len = <1 10 20>;
		};

		port {
			panel_lvds_native_in: endpoint {
				remote-endpoint = <&lvds_out>;
			};
		};
	};
};

&gpu_2d {
	status = "okay";
};

&gpu_3d {
	status = "okay";
};

// On Mallow, I2C_2_DSI (&i2c2) is used, On Custom I2C_1 (&i2c4)
&i2c4 {
    // Pin 44 (SAI3_TXFS, GPIO4_IO31) > INT_TOUCH#
    // Pin 48 (SAI3_RXD, GPIO4_IO30) > RST_TOUCH#
    touchscreen@41 {
        compatible = "ilitek,ili251x";
        reg = <0x41>;
		pinctrl-names = "default";
		pinctrl-0 = <&pinctrl_i2s_2_d_in_gpio>,
			    <&pinctrl_i2s_2_sync_gpio>;
		/* Verdin I2S_2_SYNC as GPIO (SODIMM 44) */
        interrupt-parent = <&gpio4>;
        interrupts = <31 IRQ_TYPE_EDGE_FALLING>;
		/* Verdin I2S_2_D_IN as GPIO (SODIMM 48) */
        reset-gpios = <&gpio4 30 GPIO_ACTIVE_LOW>;
        status = "okay";
    };
};

&lcdif2 {
	status = "okay";
};

&ldb {
	status = "okay";

    lvds-channel@0 {
        fsl,data-mapping = "vesa-24";
        fsl,data-width = <24>;
        status = "okay";

        port@1 {
            reg = <1>;

            lvds_out: endpoint {
                remote-endpoint = <&panel_lvds_native_in>;
            };
        };
    };
};

&ldb_phy {
	status = "okay";
};

&mix_gpu_ml {
	status = "okay";
};

&ml_vipsi {
	status = "okay";
};

/* Verdin PWM_2 */
&pwm2 {
	status = "okay";
};

&iomuxc {
	pinctrl_i2s_2_d_in_gpio: gpio4io30grp {
		fsl,pins =
			<MX8MP_IOMUXC_SAI3_RXD__GPIO4_IO30 0x1c4>;	/* SODIMM 48 */
	};

	pinctrl_i2s_2_sync_gpio: gpio4io31grp {
		fsl,pins =
			<MX8MP_IOMUXC_SAI3_TXFS__GPIO4_IO31 0x184>;	/* SODIMM 44 */
	};
};

[jeremias.tx]

Greeting All,

This issue will be resolved in our upcoming 7.2.0 quarterly release scheduled for sometime this April 2025. If the issue still exists we should catch it during our release testing and resolve it before the release. Therefore I would ask your patience and wait for this release, then try it again.

Best Regards,
Jeremias

[michael.tx]

Hi Dustin,

As Jeremias mentioned above this should be solved in the latest release. I will close this ticket.

Best regards,

Michael Park
Toradex

[dTanks]

I updated today, and still not getting the splash screen before my application starts up. Not sure where to go from here.

torizon@verdin-imx8mp-15636855:~$ sudo tdx-info

Software summary

Bootloader: U-Boot
Kernel version: 6.6.84-7.2.0-g87bfb710b6f1 #1-Torizon SMP PREEMPT Mon Mar 31 08:47:48 UTC 2025
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/157a467dd3b97eaebfbf6e17d0c8859fdd0abc1d397c637c6ecd808f79dc0260/0
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.2.0-build.13
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx8mp-15636855

Hardware info

HW model: Toradex Verdin iMX8M Plus on Verdin Development Board
Toradex version: 0063 V1.1B
Serial number: 15636855
Processor arch: aarch64

[jeremias.tx]

Hi @dTanks,

An issue was found that only affects the native LVDS of the iMX8M Plus. All the other display interfaces seem to be unaffected by this. Just checking you are using native LVDS, correct? Not DSI to LVDS?

In any case, the team will investigate this further.

Best Regards,
Jeremias

[dTanks]

Yes, I am using the native LVDS interface.

[bw908]

Are there any known similar issues with the (native) HDMI interface? I’m seeing similar behaviour on 7.2 with a blank screen instead of Plymouth. (Mallow carrier board, 1920x1080 HDMI display).

I’m able to start Weston just fine which suggests the overlays are correct. But Plymouth will not render even if started manually.

 tdx-info -dt

Device tree
------------------------------------------------------------
Device tree enabled:      imx8mp-verdin-wifi-mallow.dtb
Compatible string:        toradex,verdin-imx8mp-wifi-mallowtoradex,verdin-imx8mp-wifitoradex,verdin-imx8mpfsl,imx8mp
Device trees available:
                          imx8mp-verdin-nonwifi-dahlia.dtb
                          imx8mp-verdin-nonwifi-dev.dtb
                          imx8mp-verdin-nonwifi-ivy.dtb
                          imx8mp-verdin-nonwifi-mallow.dtb
                          imx8mp-verdin-nonwifi-yavia.dtb
                          imx8mp-verdin-wifi-dahlia.dtb
                          imx8mp-verdin-wifi-dev.dtb
                          imx8mp-verdin-wifi-ivy.dtb
                          imx8mp-verdin-wifi-mallow.dtb
                          imx8mp-verdin-wifi-yavia.dtb
------------------------------------------------------------

Device tree overlays
------------------------------------------------------------
Overlays enabled:         fdt_overlays=verdin-imx8mp_hdmi_overlay.dtbo verdin-imx8mp_spidev_overlay.dtbo custom-kargs_overlay.dtbo
Overlays available:
                          custom-kargs_overlay.dtbo
                          verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
                          verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
                          verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
                          verdin-imx8mp_hdmi_overlay.dtbo
                          verdin-imx8mp_hmp_overlay.dtbo
                          verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
                          verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
                          verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
                          verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
                          verdin-imx8mp_nau8822-btl_overlay.dtbo
                          verdin-imx8mp_ov5640_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
                          verdin-imx8mp_panel-cap-touch-7inch-dsi_overlay.dtbo
                          verdin-imx8mp_spidev_overlay.dtbo
------------------------------------------------------------

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.84-7.2.0-g87bfb710b6f1 #1-Torizon SMP PREEMPT Mon Mar 31 08:47:48 UTC 2025
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/02e76bc45f11b0a51f19d2808590ad011ceaea4e724b4533698f4e802dd095d1/0 osver=Unknown
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.2.0-build.13
Distro variant:           VARIANT="Docker"
Hostname:                 DEVBOARD
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Plus WB on Mallow Board
Toradex version:          0058 V1.1A
Serial number:            15006575
Processor arch:           aarch64
------------------------------------------------------------

[dTanks]

Torizon OS 7.2.0+build13 doesn't show custom splash screen anymore at boot

I double-checked internally and there is a known issue with splash screen on native HDMI as well. The issue was found during the release testing for 7.2.0. Though the issue wasn’t deemed critical and the release happened with the issue present. For now there is no known fixes or workarounds. Our team is already aware of the issue. They will need to investigate and work on a fix in the future. Best Regards, Jeremias

Seems like they became aware of it after posting here.

[bw908]

Thanks, I thought/knew I read that somewhere but could only find this thread on LVDS in my history.

[jeremias.tx]

Correct there is also an issue with splash screen on the native HDMI of the Verdin i.MX8M Plus. As said in the other thread, this will be noted in the release notes for 7.2.0 when they are published. Furthermore, the team is aware of these issues and will work on fixing them. It was decided internally that these issues should not postpone/block the quarterly release which is why it was decided to fix them afterwards.

Best Regards,
Jeremias

[dTanks]

Is there an update on the ETA for this to be fixed? We are internally trying to decide if we should wait a little longer for the splash screen to be functional, or to just use OS v6 as the splash works there.

[jeremias.tx]

Is there an update on the ETA for this to be fixed?

We will aim to try and have this resolved for the next quarterly release (7.3.0). Which is scheduled for the start of Q3, so sometime in July 2025 assuming no extraordinary delays occur.

Best Regards,
Jeremias