The response I received from tech support was to include the following file in the build and promptly closed:
imx6sxscm-1gb-evb-lcdif1-ldo.dts
My issue with this response is that their manual clearly states the HDMI display port adapter should work regardless of what image is being used. I would have assumed that using the provided "all bells and whistles" factory image would have supported the display from this board out of the box. Reading their response, one would think otherwise.
With that: is the dts file not included with their factory image?
How can I bake the dts file into my custom build as well?
Ticket Posted to tech support:
Description:
Product: MCIMXHDMICARD / EVB-IMX6SCMSX
Symptom: No output video
Operating System Image: L4.1.15_2.0.0-ga_images_SCM-MX6SX/xwayland/ fsl-image-qt5-imx6sxscm-1gb-evb.sdcard
Synopsis: Following the instructions contained in SCMIMX6LRNUG_L4.1.15.pdf (SCM-i.MX 6 Series Yocto Guide Rev. L4.1.15-2.0.0-ga, 04/2017) on page 6, section 5.1.2 (HDMI Display) does not result in HDMI display output using EVB-IMX6SCMSX with attached MCIMXHDMICARD on Demo image L4.1.15_2.0.0-ga_images_SCM-MX6SX/xwayland/ fsl-image-qt5-imx6sxscm-1gb-evb.sdcard
U-boot commands supplied:
U-Boot > setenv mmcargs 'setenv bootargs console=${console},${baudrate} ${smp}
root=${mmcroot} video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
U-Boot > run bootcmd
Output log capture detailing commands supplied via U-Boot to enable HDMI display out:
-------------- Begin Log -----------------------------
platform caam_sm: [0056] e9 ce 98 90 ee 21 bf a8
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 192-bit black key in blob:
platform caam_sm: [0000] 40 20 8b 8c 63 c1 0d d6
platform caam_sm: [0008] 91 83 e9 50 00 a4 8c 32
platform caam_sm: [0016] 53 05 1a 5c f6 1b d1 07
platform caam_sm: [0024] 07 c0 a7 1b 79 64 43 da
platform caam_sm: [0032] 7b 53 0a 83 9b d5 cf e8
platform caam_sm: [0040] de f5 65 dc fe 3d 40 3d
platform caam_sm: [0048] 1d eb 53 3a 11 f3 dd 22
platform caam_sm: [0056] 45 98 58 77 93 3b d1 70
platform caam_sm: [0064] d3 95 5a e1 ce 03 74 e8
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 256-bit black key in blob:
platform caam_sm: [0000] c8 c7 1c d1 32 c9 48 1e
platform caam_sm: [0008] 63 d9 aa 97 1e bb 73 1b
platform caam_sm: [0016] 2f fd a0 4c 1e 13 f7 18
platform caam_sm: [0024] c4 96 ed 63 12 48 5c 5c
platform caam_sm: [0032] e1 5b 3a c9 87 fe ac 28
platform caam_sm: [0040] 64 80 b2 eb 49 f1 a5 b9
platform caam_sm: [0048] 32 92 82 d9 6b ef 35 a1
platform caam_sm: [0056] bd 16 39 c5 6c 6d 5b fb
platform caam_sm: [0064] ed 0e b4 8c fe fb d3 de
platform caam_sm: [0072] 2a 51 d0 ca bb 32 34 60
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: restored 64-bit black key:
platform caam_sm: [0000] 06 21 2e 54 ed 41 55 33
platform caam_sm: [0008] 42 cb 37 11 6a 52 ec 2e
platform caam_sm: restored 128-bit black key:
platform caam_sm: [0000] d0 29 3d de 02 9f 1b 99
platform caam_sm: [0008] e5 72 b0 7b 82 9f 20 a3
platform caam_sm: restored 192-bit black key:
platform caam_sm: [0000] d7 b4 59 57 a4 14 37 01
platform caam_sm: [0008] 9c cf 98 12 dd 85 db f5
platform caam_sm: [0016] a1 a9 a5 94 66 36 c9 b9
platform caam_sm: [0024] 50 34 8e 64 7b 91 12 0b
platform caam_sm: restored 256-bit black key:
platform caam_sm: [0000] 88 d4 7b 75 ea 10 98 3f
platform caam_sm: [0008] fc e5 87 88 9c a3 4d 4d
platform caam_sm: [0016] b6 b5 ea e4 79 74 e6 df
platform caam_sm: [0024] 04 d2 a7 bf 2d ac 9f 8f
snvs-secvio 20cc000.caam-snvs: can't get snvs clock
snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
wm8962 3-001a: customer id 0 revision F
fsl-asrc 2034000.asrc: driver registered
input: WM8962 Beep Generator as /devices/soc0/soc/2100000.aips-bus/21f8000.i2c/i
2c-3/3-001a/input/input5
imx-wm8962 sound: wm8962 <-> 202c000.ssi mapping ok
imx-spdif sound-spdif: snd-soc-dummy-dai <-> 2004000.spdif mapping ok
NET: Registered protocol family 26
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
dhd_module_init in
input: gpio-keys as /devices/soc0/gpio-keys/input/input7
snvs_rtc 20cc000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01 00:00:02 U
TC (2)
VGEN2: disabling
can-stby: disabling
can-en: disabling
PSU-5V0: disabling
usb_otg1_vbus: disabling
VCC_SD3: disabling
ALSA device list:
#0: wm8962-audio
#1: imx-spdif
EXT3-fs (mmcblk2p2): error: couldn't mount because of unsupported optional featu
res (240)
EXT2-fs (mmcblk2p2): error: couldn't mount because of unsupported optional featu
res (244)
EXT4-fs (mmcblk2p2): recovery complete
EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 424K (80aee000 - 80b58000)
INIT: version 2.88 booting
Starting udev
udevd[173]: starting version 3.1.5
random: udevd urandom read with 22 bits of entropy available
galcore: clk_get 2d core clock failed, disable 2d/vg!
Galcore version 5.0.11.41671
3-003c supply DOVDD not found, using dummy regulator
ov5640_read_reg:write reg error:reg=300a
camera ov5640 is not found
FAT-fs (mmcblk2p1): Volume was not properly unmounted. Some data may be corrupt.
Please run fsck.
EXT4-fs (mmcblk2p2): re-mounted. Opts: (null)
bootlogd: cannot allocate pseudo tty: No such file or directory
Populating dev cache
tar: dev/disk/by-label/Bootx20imx6sx: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
udev-cache: update failed!
ALSA: Restoring mixer settings...
No state is present for card imxspdif
Found hardware: "imx-spdif" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card imxspdif
Tue Mar 14 07:00:17 UTC 2017
INIT: Entering runlevel: 5
Configuring network interfaces... fec 2188000.ethernet eth0: Freescale FEC PHY d
river [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=2188000.ethernet:03, irq=-1
)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
done.
Starting system message bus: dbus.
Starting Connection Manager
Starting Dropbear SSH server: dropbear.
Starting rpcbind daemon...done.
starting statd: done
Starting advanced power management daemon: No APM support in kernel
(failed.)
Starting atd: OK
exportfs: can't open /etc/exports for reading
NFS daemon support not enabled in kernel
Starting system log daemon...0
Starting kernel log daemon...0
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ]
Starting Telephony daemon
Starting Linux NFC daemon
Starting crond: OK
Running local boot scripts (/etc/rc.local).
Freescale i.MX Release Distro 4.1.15-2.0.0 imx6sxscm-1gb-evb /dev/ttymxc2
imx6sxscm-1gb-evb login: root
root@imx6sxscm-1gb-evb:~# random: nonblocking pool is initialized
-------------- End Log -----------------------------
Hi Matthew,
As the i.MX6SX doesn’t have HDMI module, the HDMI functionality is not available out-of-the-box. Actually, the MCIMXHDMICARD is a converter from parallel LCD to HDMI output, that’s why it is required to select a different DTB file to use it. In most of the cases, multiple DTB files are included on the FAT partition of the bootable SD card of the demo BSP, and it is just required to select it from Uboot.
You could take a look at the following links:
https://community.nxp.com/thread/381077
https://community.nxp.com/docs/DOC-328196
Hope this will be useful for you.
Best regards!
/Carlos
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------