Getting started with Apalis Evaluation Board V1.1B and an imx8 Module - no output on Monitor through DVI-D

Hi,
I just received my Boards and working on setting it up following all instructions. I however, do not get any signal output on the monitor connected to the board through DVI-D. I tried several different monitors with no luck and tried a different cable.
This is the boot up sequence I am seeing on the host computer:

U-Boot 2018.03-toradex_imx_v2018.03_4.14.78_1.0.0_ga-bringup+g25f68add54 (Jul 17 2019 - 00:34:05 +0000)

CPU:   Freescale i.MX8QM revB A53 at 1200 MHz at 62C
DRAM:  2 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 QuadPlus 2GB Wi-Fi / BT V1.0B, Serial# 06517981
BuildInfo: 
  - SCFW cb6f758b, SECO-FW d7523fe8, IMX-MKIMAGE dd023400, ATF d6451cc
  - U-Boot 2018.03-toradex_imx_v2018.03_4.14.78_1.0.0_ga-bringup+g25f68add54 

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:  3  2  1  0 
switch to partitions #0, OK
mmc0(part 0) is current device
761 bytes read in 6 ms (123 KiB/s)
Running bootscript from mmc ...
## Executing script at 80280000
102464 bytes read in 11 ms (8.9 MiB/s)
Loading hdp firmware from 0x0000000084000000 offset 0x0000000000002000
Loading hdp firmware Complete
48887640 bytes read in 848 ms (55 MiB/s)
## Loading kernel from FIT Image at 86400000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Linux Kernel 4.14
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x864000dc
     Data Size:    9889576 Bytes = 9.4 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80280000
     Entry Point:  0x80280000
     Hash algo:    md5
     Hash value:   32d5bf1b0500a2aeb396d5be7ad798b0
   Verifying Hash Integrity ... md5+ OK
## Loading ramdisk from FIT Image at 86400000 ...
   Using 'config@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  SquashFS RAMdisk
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x86d6e8f0
     Data Size:    38891520 Bytes = 37.1 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0xa0000000
     Entry Point:  unavailable
     Hash algo:    md5
     Hash value:   dbfb0e75a69d11056cb757aa9c9ca342
   Verifying Hash Integrity ... md5+ OK
   Loading ramdisk from 0x86d6e8f0 to 0xa0000000
## Loading fdt from FIT Image at 86400000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
     Description:  Apalis iMX8 Device Tree
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x892859cc
     Data Size:    104517 Bytes = 102.1 KiB
     Architecture: AArch64
     Hash algo:    md5
     Hash value:   b2b775590bd7eedf9745d550a6c5ce45
   Verifying Hash Integrity ... md5+ OK
   Booting using the fdt blob at 0x892859cc
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 00000000fd660000, end 00000000fd67c844 ... OK
/dma-controller@5a1f0000, 73320
/dma-controller@591F0000, 74200
/dma-controller@591F0000, 74200
/dma-controller@599F0000, 75176

Starting kernel ...

[    0.184204] psci: failed to boot CPU5 (-22)
[    0.184212] CPU5: failed to boot: -22
[    0.184216] CPU5: failed in unknown state : 0x0
[    0.314253] clk: couldn't set hdmi_lis_ipg_clk clk rate to 100000000 (-22), current rate: 84857142
[    0.445741] dmi: Firmware registration failed.
[    0.568971] imx6q-pcie 5f000000.pcie: pcie_ext clock source missing or invalid
[    0.571575] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[    0.646157] Can't support > 32 bit dma.
[    0.731511] i.mx8-hdp 56268000.hdmi: invalid resource
[    0.900367] Can't support > 32 bit dma.
[    0.909958] fsl_lpspi 5a000000.lpspi: dma setup error -19, use pio
[    0.917473] fsl_lpspi 5a020000.lpspi: dma setup error -19, use pio
[    0.927842] NXP PHY: loading NXP PHY driver: [autonomous mode]
[    0.963821] Can't support > 32 bit dma.
[    1.192445] atmel_mxt_ts 4-004a: __mxt_read_reg: i2c transfer failed (-5)
[    1.199375] atmel_mxt_ts 4-004a: mxt_bootloader_read: i2c recv failed (-5)
[    1.206391] atmel_mxt_ts 4-004a: mxt_bootloader_read: i2c recv failed (-5)
[    1.280447] ov5640_mipi_v3 5-003c: Read reg error: reg=300a
[    1.933862] imx6q-pcie 5f010000.pcie: Speed change timeout
Running /etc/rc.local...
TDX_VER_ID="Apalis-iMX8_ToradexEasyInstaller_2.0b2-20190716"
Starting udev
[    2.529128] udevd[2388]: specified group 'kvm' unknown
$Starting haveged: haveged: haveged starting up
[  OK  ]
Certificates for RDP not found in /var/volatile
Generating RSA private key, 2048 bit long modulus (2 primes)
haveged: haveged: ver: 1.9.2; arch: generic; vend: ; build: (gcc 8.2.0 CTV); collect: 128K

haveged: haveged: cpu: (VC); data: 16K (D V); inst: 16K (D V); idx: 11/40; sz: 15528/64688

haveged: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B):  last entropy estimate 8.00031

haveged: haveged: fills: 0, generated: 0 

.............................................+++++
................................................................................................+++++
e is 65537 (0x010001)
Signature ok
subject=C = CH, ST = Luzern, L = Luzern, O = Toradex, CN = (none)
Getting Private key
Certificate for RDP successfully generated
[    4.532425] udevd[2389]: specified group 'kvm' unknown

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 RDP. Use:
  # ip addr show eth0
to display the Ethernet IP address or use USB RNDIS at IP 192.168.11.1.

Check our documentation at:
  https://developer.toradex.com/software/toradex-easy-installer
/ #

HI @Dabd and Welcome to the Toradex Community!

Concerning your issue, could you install Toradex Easy Installer version as explained here and check if you still get the issue?

Best regards,
Jaski

Hi @jaski.tx, thank you for your help!
I just followed those steps and installed “Toradex Easy Installer” by entering recovery mode and through USB OTG. However, the problem still persists. No output on Monitor connected to Module.
It does seem like my module already had “Toradex Easy Installer” from the serial output.

See successful install below:
alt text

Thank you,
Dana

Hi Dana

You should also check the serial console output of the console as described here.
Additionally for installing Toradex Easy Installer you can use any VNC client and connect either to 192.168.11.1 over RNDIS or to the ip address of the module over Ethernet.

It does seem like my module already had “Toradex Easy Installer” from the serial output.

Yeah, you have installed the version Bsp 2.0b2 and I rather recommend you to install Bsp 2.0b4.

Please note: I hope you are running Apalis iMX8 with heatsink since it is not recommended to run Apalis iMX8 without heatsink.

Best regards,
Jaski

Hi Jaski,

After every system restart it seems to default back to rev 2.0b2 even though after recovery mode it installs the correct version 2.0b4 as you can see below.

Here is my serial console output: (unless you are referring to something else)
U-Boot 2018.03-toradex_imx_v2018.03_4.14.78_1.0.0_ga-bringup+gc0ff506c39 (Dec 31 2019 - 15:53:00 +0000)

CPU: Freescale i.MX8QM revB A53 at 1200 MHz at 45C
DRAM: 2 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 QuadPlus 2GB Wi-Fi / BT V1.0B, Serial# 06517981

BuildInfo:

  • SCFW 494c97f3, SECO-FW d7523fe8, IMX-MKIMAGE dd023400, ATF a-20190
  • U-Boot 2018.03-toradex_imx_v2018.03_4.14.78_1.0.0_ga-bringup+gc0ff506c39

switch to partitions #0, OK
mmc0(part 0) is current device
Detect USB boot. Will enter fastboot mode!
Net: eth0: ethernet@5b040000
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: fastboot 0
Hit any key to stop autoboot: 0
Detect USB boot. Will enter fastboot mode!
Starting download of 2225 bytes

downloading of 2225 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 102464 bytes

downloading of 102464 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 37130512 bytes




downloading of 37130512 bytes finished

Executing script at 82e00000

Loading hdp firmware from 0x0000000082fe0000 offset 0x0000000000002000
Loading hdp firmware Complete

Loading kernel from FIT Image at 83000000 …

Using ‘config@1’ configuration
Trying ‘kernel@1’ kernel subimage
Description: Linux Kernel 4.14.159-2.0.4+gfff496c2a1bd
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x830000f4
Data Size: 6676173 Bytes = 6.4 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x80280000
Entry Point: 0x80280000
Hash algo: md5
Hash value: a31874602b85bbb1d182034cbecd204f
Verifying Hash Integrity … md5+ OK

Loading ramdisk from FIT Image at 83000000 …

Using ‘config@1’ configuration
Trying ‘ramdisk@1’ ramdisk subimage
Description: SquashFS RAMdisk
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x8365e0b0
Data Size: 30347264 Bytes = 28.9 MiB
Architecture: AArch64
OS: Linux
Load Address: 0xa0000000
Entry Point: unavailable
Hash algo: md5
Hash value: 14e6e434f6ab782c5c0ca4a8a2c5f518
Verifying Hash Integrity … md5+ OK
Loading ramdisk from 0x8365e0b0 to 0xa0000000

Loading fdt from FIT Image at 83000000 …

Using ‘config@1’ configuration
Trying ‘fdt@1’ fdt subimage
Description: Apalis iMX8 Device Tree
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x8534f18c
Data Size: 105024 Bytes = 102.6 KiB
Architecture: AArch64
Hash algo: md5
Hash value: 33b82ac99dc7c9456a28f54bd479ee3e
Verifying Hash Integrity … md5+ OK
Booting using the fdt blob at 0x8534f18c
Uncompressing Kernel Image … OK
Loading Device Tree to 00000000fd65e000, end 00000000fd67aa3f … OK
/dma-controller@5a1f0000, 73440
/dma-controller@591F0000, 74320
/dma-controller@591F0000, 74320
/dma-controller@599F0000, 75296

Starting kernel …

[ 0.184219] psci: failed to boot CPU5 (-22)
[ 0.184237] CPU5: failed to boot: -22
[ 0.304561] clk: couldn’t set hdmi_lis_ipg_clk clk rate to 100000000 (-22), current rate: 84857142
[ 0.423996] dmi: Firmware registration failed.
[ 0.513866] imx6q-pcie 5f000000.pcie: pcie_ext clock source missing or invalid
[ 0.516463] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[ 0.569975] Can’t support > 32 bit dma.
[ 0.652662] i.mx8-hdp 56268000.hdmi: invalid resource
[ 0.828427] Can’t support > 32 bit dma.
[ 0.857555] Can’t support > 32 bit dma.
[ 1.085338] atmel_mxt_ts 4-004a: __mxt_read_reg: i2c transfer failed (-5)
[ 1.092350] atmel_mxt_ts 4-004a: mxt_bootloader_read: i2c recv failed (-5)
[ 1.099430] atmel_mxt_ts 4-004a: mxt_bootloader_read: i2c recv failed (-5)
Running /etc/rc.local…
TDX_VER_ID=“Apalis-iMX8_ToradexEasyInstaller_2.0b4-20191231”
Starting udev
System time was Mon Jan 20 22:40:28 UTC 2020.
Setting the System Clock using the Hardware Clock as reference…
System Clock set. System local time is now Mon Jan 20 22:40:28 UTC 2020.

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 eth0

to display the Ethernet IP address or use USB RNDIS at IP 192.168.11.1.

Check our documentation at:
https://developer.toradex.com/software/toradex-easy-installer
/ #

Hi Jaski,

It seems with every system restart of the board it resets to the default toradex installer version 2.0b2 even though as you can see below it installed v2.0b4

Here is my serial console output (unless you are referring to something else?):

U-Boot 2018.03-toradex_imx_v2018.03_4.14.78_1.0.0_ga-bringup+gc0ff506c39 (Dec 31 2019 - 15:53:00 +0000)

CPU:   Freescale i.MX8QM revB A53 at 1200 MHz at 45C
DRAM:  2 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 QuadPlus 2GB Wi-Fi / BT V1.0B, Serial# 06517981

 BuildInfo: 
  - SCFW 494c97f3, SECO-FW d7523fe8, IMX-MKIMAGE dd023400, ATF a-20190
  - U-Boot 2018.03-toradex_imx_v2018.03_4.14.78_1.0.0_ga-bringup+gc0ff506c39 

switch to partitions #0, OK
mmc0(part 0) is current device
Detect USB boot. Will enter fastboot mode!
Net:   eth0: ethernet@5b040000
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for 				 mfgtools
Run bootcmd_mfg: fastboot 0
Hit any key to stop autoboot:  0 
Detect USB boot. Will enter fastboot mode!
Starting download of 2225 bytes

downloading of 2225 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 102464 bytes

downloading of 102464 bytes finished
Detect USB boot. Will enter fastboot mode!
Starting download of 37130512 bytes
..........................................................................
..........................................................................
..........................................................................
.............................................................
downloading of 37130512 bytes finished
## Executing script at 82e00000
Loading hdp firmware from 0x0000000082fe0000 offset 0x0000000000002000
Loading hdp firmware Complete
## Loading kernel from FIT Image at 83000000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Linux Kernel 4.14.159-2.0.4+gfff496c2a1bd
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x830000f4
     Data Size:    6676173 Bytes = 6.4 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80280000
     Entry Point:  0x80280000
     Hash algo:    md5
     Hash value:   a31874602b85bbb1d182034cbecd204f
   Verifying Hash Integrity ... md5+ OK
## Loading ramdisk from FIT Image at 83000000 ...
   Using 'config@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  SquashFS RAMdisk
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x8365e0b0
     Data Size:    30347264 Bytes = 28.9 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0xa0000000
     Entry Point:  unavailable
     Hash algo:    md5
     Hash value:   14e6e434f6ab782c5c0ca4a8a2c5f518
   Verifying Hash Integrity ... md5+ OK
   Loading ramdisk from 0x8365e0b0 to 0xa0000000
## Loading fdt from FIT Image at 83000000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
     Description:  Apalis iMX8 Device Tree
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x8534f18c
     Data Size:    105024 Bytes = 102.6 KiB
     Architecture: AArch64
     Hash algo:    md5
     Hash value:   33b82ac99dc7c9456a28f54bd479ee3e
   Verifying Hash Integrity ... md5+ OK
   Booting using the fdt blob at 0x8534f18c
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 00000000fd65e000, end 00000000fd67aa3f ... OK
/dma-controller@5a1f0000, 73440
/dma-controller@591F0000, 74320
/dma-controller@591F0000, 74320
/dma-controller@599F0000, 75296

Starting kernel ...

[    0.184219] psci: failed to boot CPU5 (-22)
[    0.184237] CPU5: failed to boot: -22
[    0.304561] clk: couldn't set hdmi_lis_ipg_clk clk rate to 100000000 (-22), current rate: 84857142
[    0.423996] dmi: Firmware registration failed.
[    0.513866] imx6q-pcie 5f000000.pcie: pcie_ext clock source missing or invalid
[    0.516463] imx6q-pcie 5f010000.pcie: pcie_ext clock source missing or invalid
[    0.569975] Can't support > 32 bit dma.
[    0.652662] i.mx8-hdp 56268000.hdmi: invalid resource
[    0.828427] Can't support > 32 bit dma.
[    0.857555] Can't support > 32 bit dma.
[    1.085338] atmel_mxt_ts 4-004a: __mxt_read_reg: i2c transfer failed (-5)
[    1.092350] atmel_mxt_ts 4-004a: mxt_bootloader_read: i2c recv failed (-5)
[    1.099430] atmel_mxt_ts 4-004a: mxt_bootloader_read: i2c recv failed (-5)
Running /etc/rc.local...
TDX_VER_ID="Apalis-iMX8_ToradexEasyInstaller_2.0b4-20191231"
Starting udev
System time was Mon Jan 20 22:40:28 UTC 2020.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Mon Jan 20 22:40:28 UTC 2020.

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 eth0
to display the Ethernet IP address or use USB RNDIS at IP 192.168.11.1.

Check our documentation at:
  https://developer.toradex.com/software/toradex-easy-installer
/ # 

Thank you,

Dana

HI Dana

When you launch the recovery script, then Toradex Easy Installer is copied to the RAM of the module and booted from there.
Then you need to connect to the module by using a VNC Client and install Toradex Easy Installer by selecting it from the image shown in VNC Client. Have you done this?

Best regards,
Jaski

Hi Jaski,

Yes, that worked. I was able to connect through VNC and install the image. No display on the monitor still but at least I was able to move on.

Thank you!
Dana

HI Dana

These are good news. Which image did you install?
Could you provide some information about your monitor?

Best regards,
Jaski

Hi Jaski,

I used the torizon image, the monitor I am using is an HP EliteDisplay E231i 1920X1080 at 60Hz.

Thank you,
Dana

HI Dana

Which Torizon version ( uname -a ) did you install?
Could you provide a dmesg log ( dmesg > dmesg.txt )?

Thanks and best regards,
Jaski

Hi Jaski,

The Torizon version is “Linux 4.14.126-0.0.0”
See attached log "dmesg.txt"link text

Please advise.

Thank you,

Dana

Greetings @Dabd,

I’m unable to recreate this issue on my end.

Just to double check a few things, so you’ve had issues getting display working via DVI-D for both our easy installer tool and the Torizon image, correct?

Could you try installing another image through easy installer and see if the problem persists?

If the issue continues then the issue might be hardware/display related. One thing to check is that jumpers X39 and X40 on the evaluation board are properly set to the DVI-D option.

Best Regards,
Jeremias

Hi Jeremias,

That’s correct, I haven’t been able to get my display to work at all. I tried multiple monitors and cables.
I installed a different image - the NXP and AWS demo image - and the problem persists.
Both jumpers are set correctly to DVI.

Please advise.

Thank you,

Dana

Hi Jeremias,

I tried a monitor with an HDMI input, and a DVI-D to HDMI adapter. And that worked!!

Thank you so much!
-Dana

Hi Dana,

Could you see what the output of running fbset on the device is. It’d help to know what kind of timing information the device is parsing from the display if any at all.

Also are the cables you are trying straight DVI-D to DVI-D? If you have any DVI-D to HDMI it might be worth a shot as I recall some customers had better results with DVI-D to HDMI.

Best Regards,
Jeremias

Glad it worked out for you!