Several error messages while booting TorizonCore on Verdin iMX8M-Plus

Technical Support
, , ,
1

I’ve just downloaded and installed the latest TorizonCore Monthly for Verdin iMX8M-Plus (today is 6.2.0-devel-202303+build.6.container on my SoM mounted on Verdin Development Board V1.1B.

From the Linux serial console I see a lot of error messages during the boot

Starting kernel ...

[    2.338066] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    2.349798] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    2.358078] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
Starting version 250.5+
[    2.554728] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    2.567123] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    2.575446] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    2.793116] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    2.804866] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    2.813150] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    4.106196] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    4.118362] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    4.126717] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    4.141845] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    4.153707] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    4.162027] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    4.242366] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    4.254984] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    4.269453] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    4.959323] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    4.971067] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    4.979551] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.149260] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    5.163088] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    5.172190] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.241048] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    5.253586] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    5.262468] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.337815] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    5.349737] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    5.358658] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.413397] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    5.425237] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    5.433730] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.501091] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    5.514527] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    5.522895] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.550587] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    5.562352] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    5.570868] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    5.681528] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    5.845066] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517)

TorizonCore 6.2.0-devel-202303+build.6 verdin-imx8mp-14777722 ttymxc2

verdin-imx8mp-14777722 login:

even if TorizonCore boots and I can see Portainer page.
Is there something that must be changed from my side?
Or something that should be fixed on TorizonCore?

Thanks

iMX8M Plus enable HDCP in sink device
Verdin IMX8M-Plus production fails with 1.1B but passes with 1.1A
2

Greetings @vix,

These messages are already known to our team. However, they do not represent any major issues and can be safely ignored for the most part. Are you concerned because the messages look concerning? Or are you actually experiencing issues?

Best Regards,
Jeremias

3

I don’t see any issue (at the moment).

4

In that case as I said these messages can be disregarded as they are known.

5

At a first sight, the only message that is suspicious to me is the last one

because I need to transmit sound over HDMI calble to an external monitor with speakers.

Does this message mean that sound over HDMI doesn’t work?

6

Hello @vix ,
I have loaded the following image:
TorizonCore 6.2.0-devel-202303+build.6

and I don’t see any HDMI error messages.
My output of dmesg | grep hdmi

torizon@verdin-imx8mp-07011753:~$ dmesg | grep hdmi
[    0.073429] platform 32fd8000.hdmi: Fixing up cyclic dependency with 32fc6000.lcd-controller
[    1.026973] i2c 3-0048: Fixing up cyclic dependency with hdmi-connector
[    1.314573] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2)
[    1.316922] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver
[    5.055575] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_ops)
[    5.691979] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card1/input2

Best regards,
Josep

7

Hello @vix ,
Do you have any news on this topic? Have you been able to test the sound over HDMI?

Best regards,
Josep

8

Not yet.
A list of other showstopper issues is on my to do list.
I let you know

9

Hi @josep.tx and @jeremias.tx
I can share some news on this topic.
I did all the tests with:

  • Verdin iMX8M-Plus Quad 4GB WB IT V 1.1A
  • Verdin Development Board V 1.1B + Verdin DSI to HDMI Adapter Rev 1.1 (which is mounted, but nothing is connected)
  • HDMI monitor connected to X37 + X53 (touch screen)
  • TorizonCore with Eval Containers 6.3.0-devel-202305+build.7.container

If I look to the Linux console during boot, I see a long list of these *ERROR* messages

[    2.524373] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    2.536198] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    2.544481] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517

If I login at the end of the boot, and I run dmesg | grep hdmi I get the following output

[    0.073109] platform 32fd8000.hdmi: Fixing up cyclic dependency with 32fc6000.lcd-controller
[    1.022819] i2c 3-0048: Fixing up cyclic dependency with hdmi-connector
[    1.277862] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2)
[    1.278992] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver
[    6.050159] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_ops)
[    6.560547] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card1/input8

Please, not the the timestamps of this last command are not visible in the Linux boot console log (the timestamps there start from

Starting kernel ...

[    2.306977] +V3.3_SW: Underflow of regulator enable count

and finish to

...
[    5.669723] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517

TorizonCore 6.3.0-devel-202305+build.7 verdin-imx8mp-14777722 ttymxc2

The above list of *ERROR* messages doesn’t seem problematic, most of the time.
But sometimes at the end of the boot console log I see a some additional errors related to fsl-aud2htx and imx-hdmi sound-hdmi

...
[    6.071558] [drm:drm_bridge_attach] *ERROR* failed to attach bridge /soc@0/bus@32c00000/mipi_dsi@32e60000 to encoder DSI-37: -517
[    6.083326] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi
[    6.091664] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -517
[    6.264280] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    6.376443] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517)
[    6.490400] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    6.566328] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517)

When this happens, nothing is shown on the HDMI monitor. Nothing is shown if I unplug and replug the HDMI cable.

Can you reproduce this behavior?
Do you have any idea on why this happens (sometimes)?

10

Hello @vix ,
I have reproduced the behavior that you explain with similar hardware and software.
The Verdin development boatd was version 1.1C
I have used a HDMI capture card instead of a HDMI monitor + touchscreen.
I tried TorizonCore 6.3.0-devel-202305+build.7 and TorizonCore 6.3.0-devel-202306+build.8 (more recent)

Regarding these messages:

they can be disregarded, as @jeremias.tx pointed out.

In some of the reboots the following messages have also appeared,

[    5.878153] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517)
[    5.945855] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517)
[    5.950974] fsl-aud2htx 30cb0000.aud2htx: failed to pcm register
[    6.019903] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517)

but they did not cause any malfunction of the HDMI output (to the image, I mean).
Have you tried with another monitor to check if the problem persists?
Can you share the dmesg output when you see no image in the monitor?

Best regards,
Josep

11

Hello @vix,

Do you have any updates on this topic?

Best regards,
Josep

12

Hoi @josep.tx,
not yet.