Apalis IMX8 + TorizonCore continuous reboot when the dvi cable is plugged in

Technical Support
, , , ,
1

Hi all,
I’m using an APALIS IMX8 on an Apalis Evaluation Board, running TorizonCore.

As soon as I plug in the dvi cable of my monitor, the Operating- Apalis iMX8 6.4.0-devel-202309+build.13
System reboots and then contiuously reboots.
I tried several versions (listed below) of the TorizonCore operating system, every time the result is the same.

  • Apalis iMX8 5.7.2+build.20 2023/04/13
  • Apalis iMX8 6.3.0+build.4 2023/07/25
  • Apalis iMX8 6.4.0-devel-202309+build.13
  • Apalis iMX8 5.7.0+build.1

The ouput shown on the serial console is the following:

U-Boot 2020.04-5.7.0+git.33bb8e968332 (Jan 01 1970 - 00:00:00 +0000)

CPU:   NXP i.MX8QM RevB A53 at 1200 MHz

DRAM:  4 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex Apalis iMX8 QuadMax 4GB IT V1.1D, Serial# 14759808

 BuildInfo:
  - SCFW 216a2c2e, SECO-FW c9de51c0, IMX-MKIMAGE 6a315dbc, ATF 2fa8c63
  - U-Boot 2020.04-5.7.0+git.33bb8e968332

switch to partitions #0, OK
mmc0(part 0) is current device
flash target is MMC:0
Net:   eth0: ethernet@5b040000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
973 bytes read in 12 ms (79.1 KiB/s)
## Executing script at 83100000
4529 bytes read in 21 ms (210 KiB/s)
167875 bytes read in 31 ms (5.2 MiB/s)
43 bytes read in 24 ms (1000 Bytes/s)
Applying Overlay: apalis-imx8_hdmi_overlay.dtbo
2177 bytes read in 30 ms (70.3 KiB/s)
12192077 bytes read in 295 ms (39.4 MiB/s)
Uncompressed size: 30659072 = 0x1D3D200
9179951 bytes read in 230 ms (38.1 MiB/s)
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Loading Ramdisk to fcd8c000, end fd64d32f ... OK
   Loading Device Tree to 00000000fcd3f000, end 00000000fcd8bfff ... OK

Starting kernel ...

[    0.146883] No BMan portals available!
[    0.148081] No QMan portals available!
[    1.614158] imx-audmix imx-audmix.0: failed to find SAI platform device
[    1.724593] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[    1.725145] imx6q-pcie 5f000000.pcie: pcie_ext clock source missing or invalid
[    2.187902] debugfs: Directory '59050000.sai' with parent 'apalis-imx8qm-sgtl5000' already present!
[    2.215598] rtc-ds1307 4-0068: hctosys: unable to read the hardware clock
[    3.441335] imx6q-pcie 5f010000.pcie: failed to initialize host
[    3.447290] imx6q-pcie 5f010000.pcie: unable to add pcie port.
[    3.555589] imx6q-pcie 5f000000.pcie: failed to initialize host
[    3.561566] imx6q-pcie 5f000000.pcie: unable to add pcie port.
Starting version 244.5+
[    7.539341] debugfs: Directory '59090000.sai' with parent 'imx-audio-hdmi-tx' already present!
[    7.548775] debugfs: File 'Capture' in directory 'dapm' already present!

TorizonCore 5.7.0+build.17 apalis-imx8-14759808 ttyLP1

apalis-imx8-14759808 login:

U-Boot 2020.04-5.7.0+git.33bb8e968332 (Jan 01 1970 - 00:00:00 +0000)

CPU:   NXP i.MX8QM RevB A53 at 1200 MHz

DRAM:  4 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex Apalis iMX8 QuadMax 4GB IT V1.1D, Serial# 14759808

 BuildInfo:
  - SCFW 216a2c2e, SECO-FW c9de51c0, IMX-MKIMAGE 6a315dbc, ATF 2fa8c63
  - U-Boot 2020.04-5.7.0+git.33bb8e968332

switch to partitions #0, OK
mmc0(part 0) is current device
flash target is MMC:0
Net:   eth0: ethernet@5b040000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
973 bytes read in 11 ms (85.9 KiB/s)
## Executing script at 83100000
4529 bytes read in 21 ms (210 KiB/s)
167875 bytes read in 31 ms (5.2 MiB/s)
43 bytes read in 25 ms (1000 Bytes/s)
Applying Overlay: apalis-imx8_hdmi_overlay.dtbo
2177 bytes read in 30 ms (70.3 KiB/s)
12192077 bytes read in 295 ms (39.4 MiB/s)
Uncompressed size: 30659072 = 0x1D3D200
9179951 bytes read in 230 ms (38.1 MiB/s)
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Loading Ramdisk to fcd8c000, end fd64d32f ... OK
   Loading Device Tree to 00000000fcd3f000, end 00000000fcd8bfff ... OK

Starting kernel ...

[    0.150419] No BMan portals available!
[    0.151633] No QMan portals available!
[    2.578439] imx-audmix imx-audmix.0: failed to find SAI platform device
[    3.201825] imx6q-pcie 5f000000.pcie: pcie_ext clock source missing or invalid
[    3.203375] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[    3.688581] debugfs: Directory '59050000.sai' with parent 'apalis-imx8qm-sgtl5000' already present!
[    3.711986] rtc-ds1307 4-0068: hctosys: unable to read the hardware clock
2

Hi @luigi ,

The output of the serial console you shared doesn’t seem to have any obvious unusual messages, at least from a quick look.

I’ll try testing here with the same setup and see if I can reproduce your results.

In the meantime, can you confirm if the power supply being used for the Apalis Evaluation Board is providing enough current to the board?

Best regards,
Lucas Akira

3

Hi Lucas,

I’m using a Power Supply AC Adapter (plugged in the X17 connector) whose output characteristics are:

12V
4.16 A

Regards,
Luigi.

4

Hi @luigi ,

12V
4.16 A

4A should be more than enough available current for the board, so it doesn’t look like a power supply issue.

On my side I tested an Apalis iMX8QM V1.0B with an Apalis Evaluation board V1.1C running TorizonCore 6.3.0 Quarterly release, and I wasn’t able to reproduce your issue: Plugging and unplugging the DVI cable from the board didn’t cause any reboots. All tests were done with a 12V/2A power supply.

With the DVI cable unplugged, you can try enabling persistent journald logging on TorizonCore, as detailed here:

After that try plugging in the DVI cable on the board and see if can find any error logs on journalctl after it reboots. If no related error logs appear there then the cause of the issue could be hardware-related.

Best regards,
Lucas Akira