No display output on the Aquila AM69

Aquila AM69, Aquila Development Board, Yocto : kirkstone-6.x.y

There was no output at the first boot. after than, I build with tdx-reference-multimedia-image and boot from SD card. but not work. I tried connecting HDMI and DP. What I will check?


below boot logs


U-Boot SPL 2024.04-ti-g45672232d25d (Nov 29 2024 - 10:33:47 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
Initialized 4 DRAM controllers
SPL initial stack usage: 13456 bytes
HW CFG: 0x 0
:

NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty
NOTICE:  BL31: Built : 04:20:32, Nov  1 2024
I/TC:
I/TC: OP-TEE version: 4.4.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Oct 18 17:45:27 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
:

U-Boot SPL 2024.04-ti-g45672232d25d (Nov 29 2024 - 10:33:47 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')
HW CFG: 0x 0
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2024.04-ti-g45672232d25d (Nov 29 2024 - 10:33:47 +0000)

SoC:   J784S4 SR1.0 HS-FS
DRAM:  2 GiB (effective 32 GiB)
Core:  188 devices, 32 uclasses, devicetree: separate
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... OK
get_tdx_eeprom: no alias for eeprom1
MISSING TORADEX CARRIER CONFIG BLOCKS
get_tdx_eeprom: no alias for eeprom1
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
Model: Toradex 0088 Aquila AM69 Octa 32GB WB IT V1.0A
Serial#: 12593495
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1
:

Starting kernel ...

I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
:

[    5.665569] j721e-pcie-host 2900000.pcie: host bridge /bus@100000/pcie@2900000 ranges:
[    5.673809] j721e-pcie-host 2900000.pcie:       IO 0x0010001000..0x0010010fff -> 0x0010001000
[    5.674773] mc: Linux media interface: v0.10
[    5.674825] pvrsrvkm: loading out-of-tree module taints kernel.
[    5.682406] j721e-pcie-host 2900000.pcie:      MEM 0x0010011000..0x0017ffffff -> 0x0010011000
[    5.688464] lm75 0-004f: supply vs not found, using dummy regulator
[    5.692695] j721e-pcie-host 2900000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[    5.694861] PVR_K:  274: Device: 4e20000000.gpu
[    5.694949] PVR_K:  274: Read BVNC 36.53.104.796 from HW device registers
[    5.695118] PVR_K:  274: RGX Device registered BVNC 36.53.104.796 with 1 core in the system
[    5.695909] m_can_platform 40528000.can: m_can device registered (irq=591, version=32)
[    5.698676] [drm] Initialized pvr 23.3.6512818 20170530 for 4e20000000.gpu on minor 0
[    5.698810] m_can_platform 40568000.can: m_can device registered (irq=592, version=32)
[    5.702858] hwmon hwmon1: temp1_input not attached to any thermal zone
[    5.705586] m_can_platform 27a1000.can: m_can device registered (irq=596, version=32)
[    5.716156] wm8904 1-001a: revision A
[    5.717399] videodev: Linux video capture interface: v2.00
[    5.720368] ina2xx 1-0041: power monitor ina226 (Rshunt = 5000 uOhm)
[    5.721342] lm75 0-004f: hwmon1: sensor 'tmp1075'
[    5.727991] m_can_platform 27d1000.can: m_can device registered (irq=601, version=32)
[    5.737076] k3-dsp-rproc 64800000.dsp: assigned reserved memory node c71-dma-memory@a8000000
[    5.740993] lm75 1-004f: supply vs not found, using dummy regulator
[    5.741895] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[    5.742005] platform 41000000.r5f: configured R5F for IPC-only mode
[    5.742099] platform 41000000.r5f: assigned reserved memory node r5f-dma-memory@a0000000
[    5.742458] remoteproc remoteproc1: 41000000.r5f is available
[    5.742513] remoteproc remoteproc1: attaching to 41000000.r5f
[    5.745097] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.746529] rproc-virtio rproc-virtio.6.auto: assigned reserved memory node r5f-dma-memory@a0000000
[    5.752366] k3-dsp-rproc 64800000.dsp: configured DSP for remoteproc mode
[    5.752936] hwmon hwmon3: temp1_input not attached to any thermal zone
[    5.752946] lm75 1-004f: hwmon3: sensor 'tmp1075'
[    5.760619] virtio_rpmsg_bus virtio0: rpmsg host is online
[    5.760709] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.761514] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.766288] remoteproc remoteproc0: 64800000.dsp is available
[    5.780024] rproc-virtio rproc-virtio.6.auto: registered virtio0 (type 7)
[    5.782981] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.794621] k3-dsp-rproc 64800000.dsp: register pm nitifiers in remoteproc mode
[    5.795428] cdns-mhdp8546 a000000.dp-bridge: invalid resource
[    5.795436] cdns-mhdp8546 a000000.dp-bridge: Failed to get SAPB memory resource, HDCP not supported
[    5.797909] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.803426] remoteproc remoteproc1: remote processor 41000000.r5f is now attached
[    5.817153] k3-dsp-rproc 65800000.dsp: assigned reserved memory node c71-dma-memory@a9000000
[    5.829219] platform 41400000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[    5.830204] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.832203] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.835641] remoteproc remoteproc0: Direct firmware load for j784s4-c71_0-fw failed with error -2
[    5.840030] k3-dsp-rproc 65800000.dsp: configured DSP for remoteproc mode
[    5.843774] platform 41400000.r5f: configured R5F for IPC-only mode
[    5.846805] [drm] Initialized tidss 1.0.0 20180215 for 4a00000.dss on minor 1
[    5.847492] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
[    5.848863] remoteproc remoteproc0: powering up 64800000.dsp
[    5.853027] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
[    5.854169] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
[    5.854967] platform 41400000.r5f: assigned reserved memory node r5f-dma-memory@a1000000
[    5.855230] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.861359] remoteproc remoteproc2: 65800000.dsp is available
[    5.861416] k3-dsp-rproc 65800000.dsp: register pm nitifiers in remoteproc mode
[    5.861474] remoteproc remoteproc2: Direct firmware load for j784s4-c71_1-fw failed with error -2
[    5.861479] remoteproc remoteproc2: powering up 65800000.dsp
[    5.861490] remoteproc remoteproc2: Direct firmware load for j784s4-c71_1-fw failed with error -2
[    5.861494] remoteproc remoteproc2: request_firmware failed: -2
[    5.862675] k3-dsp-rproc 66800000.dsp: assigned reserved memory node c71-dma-memory@aa000000
[    5.863690] k3-dsp-rproc 66800000.dsp: configured DSP for remoteproc mode
[    5.864094] remoteproc remoteproc0: Direct firmware load for j784s4-c71_0-fw failed with error -2
[    5.864105] remoteproc remoteproc0: request_firmware failed: -2
[    5.864301] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.873712] remoteproc remoteproc3: 41400000.r5f is available
[    5.874999] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.879353] remoteproc remoteproc4: 66800000.dsp is available
[    5.885591] remoteproc remoteproc3: attaching to 41400000.r5f
[    5.890437] k3-dsp-rproc 66800000.dsp: register pm nitifiers in remoteproc mode
[    5.895795] remoteproc remoteproc3: remote processor 41400000.r5f is now attached
[    5.904386] remoteproc remoteproc4: Direct firmware load for j784s4-c71_2-fw failed with error -2
[    5.906941] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.907600] k3-dsp-rproc 67800000.dsp: assigned reserved memory node c71-dma-memory@ab000000
[    5.908242] k3-dsp-rproc 67800000.dsp: configured DSP for remoteproc mode
[    5.911075] remoteproc remoteproc5: 67800000.dsp is available
[    5.911182] k3-dsp-rproc 67800000.dsp: register pm nitifiers in remoteproc mode
[    5.911243] remoteproc remoteproc5: Direct firmware load for j784s4-c71_3-fw failed with error -2
[    5.911250] remoteproc remoteproc5: powering up 67800000.dsp
[    5.911262] remoteproc remoteproc5: Direct firmware load for j784s4-c71_3-fw failed with error -2
[    5.911266] remoteproc remoteproc5: request_firmware failed: -2
[    5.912201] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.915014] platform 5c00000.r5f: error -ENODEV: mbox_request_channel failed
[    5.918846] remoteproc remoteproc4: powering up 66800000.dsp
[    5.918937] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    5.925753] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init failed, ret = -19
[    5.933964] remoteproc remoteproc4: Direct firmware load for j784s4-c71_2-fw failed with error -2
[    5.941642] debugfs: File 'Headphone Jack' in directory 'dapm' already present!
[    5.947020] remoteproc remoteproc4: request_firmware failed: -2
[    5.997767] cdns-mhdp8546 a000000.dp-bridge: Failed to read receiver capabilities
[    6.085423] platform 5e00000.r5f: configured R5F for remoteproc mode
[    6.099038] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    6.100172] cdns-mhdp8546 a000000.dp-bridge: get block[0] edid failed: -22
[    6.100187] cdns-mhdp8546 a000000.dp-bridge: Failed to read EDID
[    6.105673] platform 5e00000.r5f: assigned reserved memory node r5f-dma-memory@a4000000
[    6.113100] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    6.153131] remoteproc remoteproc7: 5e00000.r5f is available
[    6.250188] tpm_tis_spi spi1.0: 2.0 TPM (device-id 0x4, rev-id 1)
[    6.256201] remoteproc remoteproc7: Direct firmware load for j784s4-main-r5f1_0-fw failed with error -2
[    6.256705] omap_rng 4e10000.rng: Random Number Generator ver. 241b34c
[    6.257735] OF: graph: no port node found in /bus@100000/bus@28380000/i2c@40b00000/ptn5110@52
[    6.265132] tpm tpm0: A TPM error (256) occurred attempting the self test
[    6.271501] remoteproc remoteproc7: powering up 5e00000.r5f
[    6.277675] tpm tpm0: starting up the TPM manually
[    6.286197] remoteproc remoteproc7: Direct firmware load for j784s4-main-r5f1_0-fw failed with error -2
[    6.318025] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
[    6.323752] remoteproc remoteproc7: request_firmware failed: -2
         Starting Network Time Synchronization...
[    6.471626] Console: switching to colour frame buffer device 80x30
[    6.496662] tidss 4a00000.dss: [drm] fb0: tidssdrmfb frame buffer device
         Starting Record System Boot/Shutdown in UTMP...
[  OK  ] Started Network Time Synchronization.
[  OK  ] Finished Record System Boot/Shutdown in UTMP.
[    6.711300] j721e-pcie-host 2900000.pcie: PCI host bridge to bus 0000:00
[    6.718055] pci_bus 0000:00: root bus resource [bus 00-ff]
[    6.723563] pci_bus 0000:00: root bus resource [io  0x0000-0xffff] (bus address [0x10001000-0x10010fff])
[    6.733462] pci_bus 0000:00: root bus resource [mem 0x10011000-0x17ffffff]
[  OK  ] Created slice Slice /system/systemd[    6.740777] pci 0000:00:00.0: [104c:b00d] type 01 class 0x060400
-fsck.
[    6.752317] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[    6.763496] pci 0000:00:00.0: supports D1
[    6.767905] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    6.767939] pci 0000:00:00.0: reg 0x224: [mem 0x00000000-0x003fffff 64bit]
[  OK  ] Reached target System Time Set.[    6.781283] pci 0000:00:00.0: VF(n) BAR0 space: [mem 0x00000000-0x00ffffff 64bit] (contains BAR0 for 4 VFs)

[    6.798856] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    6.807902] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    6.814926] pci 0000:00:00.0: BAR 7: assigned [mem 0x10400000-0x113fffff 64bit]
[    6.823016] pci 0000:00:00.0: PCI bridge to [bus 01]
[    6.828805] pcieport 0000:00:00.0: PME: Signaling with IRQ 613
[    6.835189] pcieport 0000:00:00.0: AER: enabled with IRQ 613
[    6.841691] j721e-pcie-host 2910000.pcie: host bridge /bus@100000/pcie@2910000 ranges:
[    6.850378] j721e-pcie-host 2910000.pcie:       IO 0x0018001000..0x0018010fff -> 0x0018001000
[    6.859685] j721e-pcie-host 2910000.pcie:      MEM 0x0018011000..0x001fffffff -> 0x0018011000
[    6.868974] j721e-pcie-host 2910000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
         Starting Load Kernel Module efi_pstore...
         Starting File System Check on /dev/mmcblk0p1...
[  OK  ] Finished Load Kernel Module efi_pstore.
[  OK  ] Finished File System Check on /dev/mmcblk0p1.
         Mounting /media/BOOT-mmcblk0p1...
[  OK  ] Mounted /media/BOOT-mmcblk0p1.
[  OK  ] Found device /dev/mmcblk1p1.
         Starting File System Check on /dev/mmcblk1p1...
[  OK  ] Finished File System Check on /dev/mmcblk1p1.
         Mounting /media/boot-mmcblk1p1...
[  OK  ] Mounted /media/boot-mmcblk1p1.
         Mounting /boot...
[  OK  ] Mounted /boot.
[    7.867298] j721e-pcie-host 2910000.pcie: PCI host bridge to bus 0001:00
[    7.874433] pci_bus 0001:00: root bus resource [bus 00-ff]
[    7.880292] pci_bus 0001:00: root bus resource [io  0x10000-0x1ffff] (bus address [0x18001000-0x18010fff])
[    7.890677] pci_bus 0001:00: root bus resource [mem 0x18011000-0x1fffffff]
[    7.897944] pci 0001:00:00.0: [104c:b013] type 01 class 0x060400
[    7.904317] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[    7.914834] pci 0001:00:00.0: supports D1
[    7.919212] pci 0001:00:00.0: PME# supported from D0 D1 D3hot
[    7.925350] pci 0001:00:00.0: reg 0x224: [mem 0x00000000-0x003fffff 64bit]
[    7.932589] pci 0001:00:00.0: VF(n) BAR0 space: [mem 0x00000000-0x00ffffff 64bit] (contains BAR0 for 4 VFs)
[    7.945353] pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    7.954242] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
[    7.961248] pci 0001:00:00.0: BAR 7: assigned [mem 0x18400000-0x193fffff 64bit]
[    7.969303] pci 0001:00:00.0: PCI bridge to [bus 01]
[    7.975007] pcieport 0001:00:00.0: PME: Signaling with IRQ 617
[    7.981404] pcieport 0001:00:00.0: AER: enabled with IRQ 617
[    7.987783] j721e-pcie-host 2920000.pcie: host bridge /bus@100000/pcie@2920000 ranges:
[    7.996492] j721e-pcie-host 2920000.pcie:       IO 0x4400001000..0x4400010fff -> 0x0000001000
[    8.005765] j721e-pcie-host 2920000.pcie:      MEM 0x4400011000..0x4407ffffff -> 0x0000011000
[    8.015033] j721e-pcie-host 2920000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[    8.126390] j721e-pcie-host 2920000.pcie: Link up
[    8.131558] j721e-pcie-host 2920000.pcie: PCI host bridge to bus 0002:00
[    8.138621] pci_bus 0002:00: root bus resource [bus 00-ff]
[    8.144471] pci_bus 0002:00: root bus resource [io  0x20000-0x2ffff] (bus address [0x1000-0x10fff])
[    8.154228] pci_bus 0002:00: root bus resource [mem 0x4400011000-0x4407ffffff] (bus address [0x00011000-0x07ffffff])
[    8.165496] pci 0002:00:00.0: [104c:b012] type 01 class 0x060400
[    8.171869] pci_bus 0002:00: 2-byte config write to 0002:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[    8.182384] pci 0002:00:00.0: supports D1
[    8.186768] pci 0002:00:00.0: PME# supported from D0 D1 D3hot
[    8.192909] pci 0002:00:00.0: reg 0x224: [mem 0x00000000-0x003fffff 64bit]
[    8.200150] pci 0002:00:00.0: VF(n) BAR0 space: [mem 0x00000000-0x00ffffff 64bit] (contains BAR0 for 4 VFs)
[    8.212860] pci 0002:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    8.221738] pci 0002:01:00.0: [104c:8241] type 00 class 0x0c0330
[    8.228186] pci 0002:01:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
[    8.235375] pci 0002:01:00.0: reg 0x18: [mem 0x00000000-0x00001fff 64bit]
[    8.242772] pci 0002:01:00.0: supports D1 D2
[    8.247405] pci 0002:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[    8.287111] k3_r5_rproc bus@100000:r5fss@5e00000: Timed out waiting for 5e00000.r5f core to power up!
[    8.311232] remoteproc remoteproc7: releasing 5e00000.r5f
[    8.318413] platform 5900000.r5f: configured R5F for remoteproc mode
[    8.325496] platform 5900000.r5f: assigned reserved memory node r5f-dma-memory@a6000000
[    8.334534] remoteproc remoteproc7: 5900000.r5f is available
[    8.340644] remoteproc remoteproc7: Direct firmware load for j784s4-main-r5f2_0-fw failed with error -2
[    8.350751] remoteproc remoteproc7: powering up 5900000.r5f
[    8.356688] remoteproc remoteproc7: Direct firmware load for j784s4-main-r5f2_0-fw failed with error -2
[    8.366795] remoteproc remoteproc7: request_firmware failed: -2
[    9.375154] pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
[    9.382141] pci 0002:00:00.0: BAR 7: assigned [mem 0x4400400000-0x44013fffff 64bit]
[    9.390496] pci 0002:00:00.0: BAR 14: assigned [mem 0x4400100000-0x44001fffff]
[    9.398413] pci 0002:01:00.0: BAR 0: assigned [mem 0x4400100000-0x440010ffff 64bit]
[    9.406810] pci 0002:01:00.0: BAR 2: assigned [mem 0x4400110000-0x4400111fff 64bit]
[    9.415226] pci 0002:00:00.0: PCI bridge to [bus 01]
[    9.420558] pci 0002:00:00.0:   bridge window [mem 0x4400100000-0x44001fffff]
[    9.428238] pcieport 0002:00:00.0: enabling device (0000 -> 0002)
[    9.434881] pcieport 0002:00:00.0: PME: Signaling with IRQ 621
[    9.441241] pcieport 0002:00:00.0: AER: enabled with IRQ 621
[    9.447409] pci 0002:01:00.0: enabling device (0000 -> 0002)
[    9.453732] j721e-pcie-host 2930000.pcie: host bridge /bus@100000/pcie@2930000 ranges:
[    9.462433] j721e-pcie-host 2930000.pcie:       IO 0x4410001000..0x4410010fff -> 0x0000001000
[    9.471699] j721e-pcie-host 2930000.pcie:      MEM 0x4410011000..0x4417ffffff -> 0x0000011000
[    9.480964] j721e-pcie-host 2930000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[    9.592285] j721e-pcie-host 2930000.pcie: Link up
[    9.597482] j721e-pcie-host 2930000.pcie: PCI host bridge to bus 0003:00
[    9.604555] pci_bus 0003:00: root bus resource [bus 00-ff]
[    9.610403] pci_bus 0003:00: root bus resource [io  0x30000-0x3ffff] (bus address [0x1000-0x10fff])
[    9.620169] pci_bus 0003:00: root bus resource [mem 0x4410011000-0x4417ffffff] (bus address [0x00011000-0x07ffffff])
[    9.631454] pci 0003:00:00.0: [104c:b00d] type 01 class 0x060400
[    9.637840] pci_bus 0003:00: 2-byte config write to 0003:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[    9.637975] pci 0003:00:00.0: supports D1
[*     ] A start job is running for Wait for…ic[    9.652618] pci 0003:00:00.0: PME# supported from D0 D1 D3hot
e Initialization (2s / 2min 58s)
[    9.663196] pci 0003:00:00.0: reg 0x224: [mem 0x00000000-0x003fffff 64bit]
[    9.672963] pci 0003:00:00.0: VF(n) BAR0 space: [mem 0x00000000-0x00ffffff 64bit] (contains BAR0 for 4 VFs)
[    9.685564] pci 0003:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    9.694424] pci 0003:01:00.0: [17cb:1103] type 00 class 0x028000
[    9.700845] pci 0003:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[**    ] A start job is running for Wait for…ice Initialization (3s / 2min 58s)
[   10.367112] k3_r5_rproc bus@100000:r5fss@5900000: Timed out waiting for 5900000.r5f core to power up!
[***   ] A start job is running for Wait for…ice Initialization (4s / 2min 58s)
[   10.847188] pci_bus 0003:01: busn_res: [bus 01-ff] end is updated to 01
[   10.854248] pci 0003:00:00.0: BAR 7: assigned [mem 0x4410400000-0x44113fffff 64bit]
[   10.862646] pci 0003:00:00.0: BAR 14: assigned [mem 0x4410200000-0x44103fffff]
[   10.870622] pci 0003:01:00.0: BAR 0: assigned [mem 0x4410200000-0x44103fffff 64bit]
[   10.879050] pci 0003:00:00.0: PCI bridge to [bus 01]
[   10.884401] pci 0003:00:00.0:   bridge window [mem 0x4410200000-0x44103fffff]
[   10.892162] pcieport 0003:00:00.0: enabling device (0000 -> 0002)
[   10.898856] pcieport 0003:00:00.0: PME: Signaling with IRQ 625
[   10.905267] pcieport 0003:00:00.0: AER: enabled with IRQ 625
[   10.935793] xhci_hcd 0002:01:00.0: xHCI Host Controller
[   10.941451] xhci_hcd 0002:01:00.0: new USB bus registered, assigned bus number 1
[  OK  ] Listening on Load/Save RF …[   10.960382] xhci_hcd 0002:01:00.0: xHCI Host Controller
itch Status /dev/rfkill Watch.
[   10.961747] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.970514] xhci_hcd 0002:01:00.0: new USB bus registered, assigned bus number 2
[   10.986154] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.988990] xhci_hcd 0002:01:00.0: Host supports USB 3.0 SuperSpeed
[   10.995791] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   11.002112] hub 1-0:1.0: USB hub found
[   11.017450] hub 1-0:1.0: 2 ports detected
[   11.022101] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[   11.031471] hub 2-0:1.0: USB hub found
[   11.035636] hub 2-0:1.0: 2 ports detected
[   11.058521] ath11k_pci 0003:01:00.0: BAR 0: assigned [mem 0x4410200000-0x44103fffff 64bit]
[   11.067593] ath11k_pci 0003:01:00.0: enabling device (0000 -> 0002)
[   11.074998] ath11k_pci 0003:01:00.0: MSI vectors: 32
[   11.080330] ath11k_pci 0003:01:00.0: wcn6855 hw2.1
[   11.093921] NET: Registered PF_QIPCRTR protocol family
[   11.256242] mhi mhi0: Requested to power ON
[   11.260821] mhi mhi0: Power on setup success
[   11.261036] mhi mhi0: Direct firmware load for ath11k/WCN6855/hw2.1/amss.bin failed with error -2
[   11.275014] mhi mhi0: Error loading firmware: -2
[   11.280029] ath11k_pci 0003:01:00.0: failed to power up mhi: -110
[   11.283110] usb 1-2: new full-speed USB device number 2 using xhci_hcd
[   11.286114] ath11k_pci 0003:01:00.0: failed to start mhi: -110
[   11.299514] ath11k_pci 0003:01:00.0: failed to power up :-110
[   11.327135] ath11k_pci 0003:01:00.0: failed to create soc core: -110
[   11.333816] ath11k_pci 0003:01:00.0: failed to init core: -110
[   11.511570] Bluetooth: Core ver 2.22
[   11.515740] NET: Registered PF_BLUETOOTH protocol family
[   11.521367] Bluetooth: HCI device and connection manager initialized
[   11.528070] Bluetooth: HCI socket layer initialized
[   11.533255] Bluetooth: L2CAP socket layer initialized
[   11.538613] Bluetooth: SCO socket layer initialized
[   11.554153] usbcore: registered new interface driver btusb
[   11.560803] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00130201.bin failed with error -2
[   11.570883] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00130201.bin (-2)
         Starting Load/Save RF Kill Switch Status..[   11.588113] ath11k_pci: probe of 0003:01:00.0 failed with error -110
.
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Finished Wait for udev To Complete Device Initialization.
         Starting Load Kernel Module efi_pstore...
[   11.704597] audit: type=1334 audit(1703415340.828:4): prog-id=7 op=LOAD
[   11.711584] audit: type=1334 audit(1703415340.836:5): prog-id=8 op=LOAD
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
[  OK  ] Finished Load Kernel Module efi_pstore.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timer Units.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on dropbear.socket.
[  OK  ] Listening on GPS (Global P…ioning System) Daemon Sockets.
         Starting Weston socket...
[  OK  ] Listening on Weston socket.
[  OK  ] Reached target Socket Units.
[  OK  ] Reached target Basic System.
         Starting Save/Restore Sound Card State...
         Starting Bluetooth service...
[  OK  ] Started Kernel Logging Service.
[   12.051704] systemd-journald[220]: Data hash table of /run/log/journal/111d0fffb51741c497311b114c5b6d73/system.journal has a fill level at 75.1 (2732 of 3640 items, 2097152 file size, 767 bytes per hash table item), suggesting rotation.
[   12.073758] systemd-journald[220]: /run/log/journal/111d0fffb51741c497311b114c5b6d73/system.journal: Journal header limits reached or header out-of-date, rotating.
[  OK  ] Started System Logging Service.
         Starting D-Bus System Message Bus...
         Starting IPv6 Packet Filtering Framework...
         Starting IPv4 Packet Filtering Framework...
         Starting Telephony service...
[   12.182522] audit: type=1334 audit(1703415341.304:6): prog-id=9 op=LOAD
[   12.189545] audit: type=1334 audit(1703415341.312:7): prog-id=10 op=LOAD
         Starting User Login Management...
[  OK  ] Started Timestamping service.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Finished Save/Restore Sound Card State.
[  OK  ] Finished IPv6 Packet Filtering Framework.
[  OK  ] Finished IPv4 Packet Filtering Framework.
[  OK  ] Reached target Preparation for Network.
[  OK  ] Reached target Sound Card.
         Starting Connection service...
         Starting Network Configuration...
[  OK  ] Started User Login Management.
[  OK  ] Started Bluetooth service.
[  OK  ] Started Telephony service.
[   12.451481] audit: type=1334 audit(1703415376.220:8): prog-id=11 op=LOAD
[   12.458609] audit: type=1334 audit(1703415376.224:9): prog-id=12 op=LOAD
[   12.497286] am65-cpsw-nuss 46000000.ethernet eth0: PHY [46000f00.mdio:00] driver [TI DP83867] (irq=312)
         Starting BlueALSA service...
[   12.508253] am65-cpsw-nuss 46000000.ethernet eth0: configuring for phy/rgmii-rxid link mode
[   12.525346] audit: type=1334 audit(1703415376.292:10): prog-id=13 op=LOAD
[   12.532560] audit: type=1334 audit(1703415376.300:11): prog-id=14 op=LOAD
[   12.539265] am65-cpsw-nuss c000000.ethernet eth1: PHY [gpio-0:04] driver [TI DP83867] (irq=371)
         Starting Hostname Service...
[   12.549394] am65-cpsw-nuss c000000.ethernet eth1: configuring for phy/sgmii link mode
[  OK  ] Started Connection service.
[  OK  ] Started Network Configuration.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting WPA supplicant...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Hostname Service.
[  OK  ] Started BlueALSA service.
[  OK  ] Started WPA supplicant.
[  OK  ] Reached target Bluetooth Support.
[  OK  ] Reached target Network.
[  OK  ] Started NFS status monitor for NFSv2/3 locking..
         Starting Permit User Sessions...
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS2.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
         Starting Weston, a Wayland…ositor, as a system service...
[   12.953920] audit: type=1334 audit(1703415376.720:12): prog-id=15 op=LOAD
[   12.961126] audit: type=1334 audit(1703415376.728:13): prog-id=16 op=LOAD
         Starting User Database Manager...
[  OK  ] Started User Database Manager.
[  OK  ] Created slice User Slice of UID 0.
         Starting User Runtime Directory /run/user/0...
[  OK  ] Finished User Runtime Directory /run/user/0.
         Starting User Manager for UID 0...
[  OK  ] Started User Manager for UID 0.
[  OK  ] Started Session c1 of User root.
[   13.741938] PVR_K:  792: RGX Firmware image 'rgx.fw.36.53.104.796' loaded
[   13.754436] PVR_K:  792: Shader binary image 'rgx.sh.36.53.104.796' loaded
[  OK  ] Started Weston, a Wayland …mpositor, as a system service.
[  OK  ] Started Start a wayland application.
[  OK  ] Reached target Graphical Interface.
         Starting Record Runlevel Change in UTMP...
[  OK  ] Finished Record Runlevel Change in UTMP.

TDX Wayland with XWayland 6.8.2-devel-20250520044903+build.0 (kirkstone) aquila-am69-12593495 -
Aquila-AM69_Reference-Multimedia-Image

aquila-am69-12593495 login:

Some parts were deleted due to line restrictions.
tested command : gst-launch-1.0 videotestsrc ! autovideosink

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:


Hello! Thank you for providing a detailed boot log and sharing your setup with the Aquila AM69 and Development Board.

Based on your logs and description, here’s how to troubleshoot and verify display output for both HDMI and DisplayPort:


1. Identify Display Interface and Connections

  • HDMI Output:
    The Aquila AM69 does not have a native HDMI port. HDMI output requires a MIPI-DSI to HDMI adapter. Make sure you are using the recommended MIPI-DSI to HDMI adapter and it is properly connected.
    Reference: Aquila AM69 Product Page

  • DisplayPort Output:
    If you are connecting via DisplayPort, ensure the DisplayPort cable is firmly attached to both the Aquila board and your monitor.


2. Analyze Relevant Boot Log Messages

Your log includes:

tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
cdns-mhdp8546 a000000.dp-bridge: Failed to read receiver capabilities
cdns-mhdp8546 a000000.dp-bridge: get block[0] edid failed: -22
cdns-mhdp8546 a000000.dp-bridge: Failed to read EDID
tidss 4a00000.dss: [drm] fb0: tidssdrmfb frame buffer device

These messages indicate that:

  • The system sees a framebuffer (so graphics are being initialized),
  • But it is not able to detect a valid display via EDID (EDID is the mechanism monitors use to tell computers about their supported modes).

3. Steps to Troubleshoot

For HDMI

  • Verify Adapter: Confirm you have a supported MIPI-DSI to HDMI adapter.
  • Power and Cable: Ensure the adapter is powered, and check all cable connections.
  • Monitor Input: Make sure your monitor is set to the HDMI input where the adapter is connected.

For DisplayPort

  • Cable Quality: Try another DisplayPort cable if possible.
  • Monitor Capability: Verify your monitor supports DisplayPort and the resolution/mode expected by the board.
  • Hot-plug: Try unplugging and replugging the cable, or power-cycling the monitor.

General

  • Default Output: The image may not be configured by default to output video to the desired interface. Sometimes, the default device tree overlays may need modification for other display options.
  • Check with Another Monitor: Sometimes specific monitors may have compatibility issues with EDID handshakes.

4. Further Checks

  • Once booted, you can check if the framebuffer device is present by running:

    ls /dev/fb*
    

    You should see /dev/fb0 if the framebuffer is available.

  • For Weston/Wayland issues, you can check Weston logs for errors after login:

    cat /var/log/weston.log
    

5. Reference

Main Product Information:
Aquila AM69 - Product Overview and Display Details


If you let me know which display interface (HDMI with adapter or DisplayPort) you would like to focus on, I can provide further targeted troubleshooting or configuration steps.

Best regards,
Toradex AI Assistant.

Hi @LeeBak365

Can you test if you get the same results in our latest BSP 7?


You don’t need to build it yourself, you can test it with a pre-built image.

The reference multimedia is expected to show the Qt cinematic experience demo.

The display work good.

DT to DT : success
DT to HDMI : x
HDMI to HDMI : x

My test results that only DT to DT cable works.

I failed to build BSP 7.

I don’t know how to boot with pre-build BSP. Please give me a link.
Also tell me how to create sdcard and boot from it.
I also want to know about device tree.

thanks

@LeeBak365

You mean DP right?

  • DP to DP
    • Yes, everything should work as expected using a DP cable connected to a DP monitor
  • DP to HDMI
  • HDMI to HDMI
    • You need to enable the correct overlay, which is currently only available in the nightly builds, it’s planned in the next release.

Do you need to use HDMI specifically?

@ToradexAI

How do i install a pre-build image from Toradex?

Thanks for your response.

Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.

Did you like my answer? :+1: :-1:


Hello! Installing a pre-built image from Toradex is straightforward when using the Toradex Easy Installer (Tezi). Here’s how you can do it:

  1. Requirements
  • Ensure your Toradex System on Module (SoM) has Toradex Easy Installer installed. If it’s not installed, you’ll need to manually launch it first.
  1. Access the Easy Installer Interface
  • Connect a display to your carrier board’s video output, or
  • Use a remote desktop via VNC (Ethernet connection, default IP: 192.168.11.1).
  1. Provide the OS Image
  • Online Installation: Connect the board to the Internet using Ethernet. The Easy Installer will show available images to download.
  • Offline Installation: Download the desired image from Toradex’s website on your PC and put it on an SD card or USB flash drive. Plug the storage device into the board; the image should appear in the installer’s list.
  1. Install the Image
  • Select your desired image from the list.
  • Click “Install” or press “i” on your connected keyboard.
  • Follow the on-screen instructions.
  • Once installation completes, you’ll see a success message. You can now safely reset or power off your system.

For complete instructions, visit the official guide: Flash a New Image Using Toradex Easy Installer.

If you need further clarification about any of these steps or the device tree, just ask!

Best regards,
Toradex AI Assistant.