Home/Support/Support Forum/ConnectCore 6UL with WVGA LCD Application Kit
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

ConnectCore 6UL with WVGA LCD Application Kit

0 votes
I have a ConnectCore6UL SBC, and the 10" WVGA LCD Application Kit. By default, the display does not show any activity.
Where would I change the settings (kernel and/or U-Boot) to bring up the graphical display?
asked Jan 5, 2017 in Linux by kaltschu New to the Community (0 points)

Please log in or register to answer this question.

1 Answer

0 votes
what image are you booting? does it have graphics? LCD should work using stock images
Download the firmware images from this location: ftp://ftp1.digi.com/support/digiembeddedyocto/2.0/r4/images/82004060_1P.zip

or images from here:
ftp://ftp1.digi.com/support/digiembeddedyocto/2.0/r4/images/82004059_1P/ccimx6ulsbc/x11/

rest your u-boot environment and note your video variable.
Touch Screen does not work. It will not support the touch interface due to and i2c address conflict between the audio chip and the touch controller. For that reason digi is working on a new video adapter board that changes the address of the touch interface.
answered Jan 5, 2017 by LeonidM Veteran of the Digi Community (3,165 points)
None of the image files bring up the display, with either the RGB parallel or LVDS cable connected.
did you try to reset your u-boot environment?
env default –a
save
reset

if that doesn't help, please cope and paste your "video" variable
printenv video
I updated uboot, linux, and rootfs from the microSD card.

There is no "video" environment variable in either U-Boot or Linux.


=> printenv
arch=arm
baudrate=115200
board=ccimx6ulsbc
board_id=135
board_name=ccimx6ulsbc
board_version=2
boot_fdt=yes
bootargs_linux=cma=96M
bootargs_nand_linux=setenv bootargs console=${console},${baudrate} ${bootargs_linux} ${mtdparts} ubi.mtd=${mtdlinuxindex} ubi.mtd=${mtdrootfsindex} root=ubi1_0 rootfstype=ubifs rw ${bootargs_once} ${extra_bootargs}
bootargs_nfs=if test ${ip_dyn} = yes; then bootargs_ip="ip=dhcp";else bootargs_ip="ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off";fi;
bootargs_nfs_linux=run bootargs_nfs;setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=/dev/nfs ${bootargs_ip} nfsroot=${serverip}:${rootpath},v3,tcp ${bootargs_once} ${extra_bootargs}
bootargs_recovery=setenv bootargs console=${console},${baudrate} ${bootargs_linux} ${mtdparts} ubi.mtd=${mtdlinuxindex} ubi.mtd=${mtdrecoveryindex} ubi.mtd=${mtdrootfsindex} ubi.mtd=${mtdupdateindex} ${bootargs_once} ${extra_bootargs}
bootargs_tftp=if test ${ip_dyn} = yes; then bootargs_ip="ip=dhcp";else bootargs_ip="ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off";fi;
bootargs_tftp_linux=run bootargs_tftp;setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=/dev/nfs ${bootargs_ip} nfsroot=${serverip}:${rootpath},v3,tcp ${bootargs_once} ${extra_bootargs}
bootcmd=if run loadscript; then setexpr bs_ivt_offset ${filesize} - 0x4020;if hab_auth_img ${loadaddr} ${bs_ivt_offset}; then source ${loadaddr};fi; fi;
bootdelay=1
btaddr=00:40:9D:98:B1:0D
console=ttymxc4
cpu=armv7
eth1addr=00:40:9D:98:B1:0B
ethact=FEC0
ethaddr=00:40:9D:98:B1:0A
ethprime=FEC
fdt_addr=0x83000000
fdt_file=zImage-imx6ul-ccimx6ulsbc.dtb
fdt_high=0xffffffff
initrd_addr=0x83800000
initrd_file=uramdisk.img
initrd_high=0xffffffff
install_linux_fw_sd=if load mmc 0 ${loadaddr} install_linux_fw_sd.scr;then source ${loadaddr};fi;
ipaddr=192.168.42.30
linux_file=dey-image-qt-x11-ccimx6ulsbc.boot.ubifs
loadaddr=0x80800000
loadscript=if test -z "${mtdbootpart}"; then setenv mtdbootpart linux;fi;if ubi part ${mtdbootpart}; then if ubifsmount ubi0:${mtdbootpart}; then ubifsload ${loadaddr} ${script};fi;fi;
module_variant=0x02
mtdbootpart=linux
mtdids=nand0=gpmi-nand
mtdlinuxindex=3
mtdparts=mtdparts=gpmi-nand:3m(bootloader),1m(environment),1m(safe),14m(linux),14m(recovery),128m(rootfs),-(update)
mtdrecoveryindex=4
mtdrootfsindex=5
mtdupdateindex=6
netmask=255.255.0.0
recovery_file=recovery.img
recoverycmd=setenv mtdbootpart recovery;boot
rootfs_file=dey-image-qt-x11-ccimx6ulsbc.ubifs
rootpath=/exports/nfsroot-ccimx6ulsbc
script=boot.scr
serverip=192.168.42.1
soc=mx6
stderr=serial
stdin=serial
stdout=serial
uboot_file=u-boot.imx
vendor=digi
wlanaddr=00:40:9D:98:B1:0C
zimage=zImage-ccimx6ulsbc.bin

Environment size: 2844/131067 bytes
does backlight turn on when the module boots? Below is my environment:
U-Boot dub-2015.04-r5.4+gdbf8184 (Nov 18 2016 - 18:56:44)

CPU:   Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 33C
Reset cause: POR
I2C:   ready
DRAM:  256 MiB
MCA:   HW_VER=1  FW_VER=0.12
PMIC:  PFUZE300 DEV_ID=0x30 REV_ID=0x11
NAND:  256 MiB
MMC:   FSL_SDHC: 0
In:    serial
Out:   serial
Err:   serial
ConnectCore 6UL SOM variant 0x02: Industrial Ultralite 528MHz, 256MB NAND, 256MB DDR3, -40/+85C, Wireless, Bluetooth
Board: ConnectCore 6UL SBC, version 2, ID 135
Net:   FEC0
Hit any key to stop autoboot:  0
=> printenv
arch=arm
baudrate=115200
board=ccimx6ulsbc
board_id=135
board_name=ccimx6ulsbc
board_version=2
boot_fdt=yes
bootargs_linux=cma=96M
bootargs_nand_linux=setenv bootargs console=${console},${baudrate} ${bootargs_linux} ${mtdparts} ubi.mtd=${mtdlinuxindex} ubi.mtd=${mtdrootfsindex} root=ubi1_0 rootfstype=ubifs rw ${bootargs_once} ${extra_bootargs}
bootargs_nfs=if test ${ip_dyn} = yes; then bootargs_ip="ip=dhcp";else bootargs_ip="ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off";fi;
bootargs_nfs_linux=run bootargs_nfs;setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=/dev/nfs ${bootargs_ip} nfsroot=${serverip}:${rootpath},v3,tcp ${bootargs_once} ${extra_bootargs}
bootargs_recovery=setenv bootargs console=${console},${baudrate} ${bootargs_linux} ${mtdparts} ubi.mtd=${mtdlinuxindex} ubi.mtd=${mtdrecoveryindex} ubi.mtd=${mtdrootfsindex} ubi.mtd=${mtdupdateindex} ${bootargs_once} ${extra_bootargs}
bootargs_tftp=if test ${ip_dyn} = yes; then bootargs_ip="ip=dhcp";else bootargs_ip="ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off";fi;
bootargs_tftp_linux=run bootargs_tftp;setenv bootargs console=${console},${baudrate} ${bootargs_linux} root=/dev/nfs ${bootargs_ip} nfsroot=${serverip}:${rootpath},v3,tcp ${bootargs_once} ${extra_bootargs}
bootcmd=if run loadscript; then setexpr bs_ivt_offset ${filesize} - 0x4020;if hab_auth_img ${loadaddr} ${bs_ivt_offset}; then source ${loadaddr};fi; fi;
bootdelay=1
btaddr=00:40:9D:98:A9:A5
console=ttymxc4
cpu=armv7
eth1addr=00:40:9D:98:A9:A3
ethact=FEC0
ethaddr=00:40:9D:98:A9:A2
ethprime=FEC
fdt_addr=0x83000000
fdt_file=zImage-imx6ul-ccimx6ulsbc.dtb
fdt_high=0xffffffff
filesize=5068000
initrd_addr=0x83800000
initrd_file=uramdisk.img
initrd_high=0xffffffff
install_linux_fw_sd=if load mmc 0 ${loadaddr} install_linux_fw_sd.scr;then source ${loadaddr};fi;
ipaddr=192.168.42.30
linux_file=dey-image-qt-x11-ccimx6ulsbc.boot.ubifs
loadaddr=0x80800000
loadscript=if test -z "${mtdbootpart}"; then setenv mtdbootpart linux;fi;if ubi part ${mtdbootpart}; then if ubifsmount ubi0:${mtdbootpart}; then ubifsload ${loadaddr} ${script};fi;fi;
module_variant=0x02
mtdbootpart=linux
mtddevname=bootloader
mtddevnum=0
mtdids=nand0=gpmi-nand
mtdlinuxindex=3
mtdparts=mtdparts=gpmi-nand:3m(bootloader),1m(environment),1m(safe),14m(linux),14m(recovery),128m(rootfs),-(update)
mtdrecoveryindex=4
mtdrootfsindex=5
mtdupdateindex=6
netmask=255.255.0.0
partition=nand0,0
recovery_file=recovery.img
recoverycmd=setenv mtdbootpart recovery;boot
rootfs_file=dey-image-qt-x11-ccimx6ulsbc.ubifs
rootpath=/exports/nfsroot-ccimx6ulsbc
script=boot.scr
serverip=192.168.42.1
soc=mx6
stderr=serial
stdin=serial
stdout=serial
uboot_file=u-boot.imx
vendor=digi
verifyaddr=88400000
wlanaddr=00:40:9D:98:A9:A4
zimage=zImage-ccimx6ulsbc.bin

Environment size: 2943/131067 bytes
=>
I see GUI when the board boots from images programmed with this:
ftp://ftp1.digi.com/support/digiembeddedyocto/2.0/r4/images/82004060_1P.zip
if you do not you might need to RMA your board
It boots into Linux but I get no back-light and no GUI.
are you able to test the LCD kid with another board? Are you connecting it to LVDS connector on cc6ul SBC? I suspect you have an issue either with the kit or the board. it should work with no tricks and it does work here for me. contact support and ask for RMA
I have a CC6 (not UL) SBC, which boots into the GUI on HDMI.  The LCD does not work there either.  I will request a replacement LCD.
...