Can't get X11 image working on i.MX 6Quad SABRE-SD

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Can't get X11 image working on i.MX 6Quad SABRE-SD

Jump to solution
1,936 Views
hansenmike
Contributor II

I am trying to build an image for the imx6qpsabresd board.  I follow the instructions in the "Freescale Yocto Project User's Guide (IMXLXYOCTOUG), rev. 0, 04/2016.

The image is created and I can copy to an SD card.  I use these settings:

$ DISTRO=fsl-imx-x11 MACHINE=imx6qpsabresd source fsl-setup-release.sh -b imx6qp_x11

then...

$ bitbake fsl-image-gui

(basically following sect. 5.6.1)

The board will boot through the USB console port, but I get nothing going to the connected HDMI display nor response to the connected keyboard.  Here is the display when I try startx from the console:

Freescale i.MX Release Distro 4.1.15-1.2.0 imx6qpsabresd /dev/ttymxc0

imx6qpsabresd login: root
root@imx6qpsabresd:~# startx
xauth:  file /home/root/.serverauth.1006 does not exist


X.Org X Server 1.18.0
Release Date: 2015-11-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-31-generic x86_64
Current Operating System: Linux imx6qpsabresd 4.1.15-1.2.0+g77f6154 #1 SMP PREEMPT Mon Dec 12 19:36:54 GMT 2016 armv7l
Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk2p2 rootwait rw
Build Date: 12 December 2016  10:15:34PM

Current version of pixman: 0.32.6
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Dec 13 19:56:39 2016
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/etc/X11/xinit/xinitrc: line 51: twm: command not found
/etc/X11/xinit/xinitrc: line 52: xclock: command not found
/etc/X11/xinit/xinitrc: line 53: xterm: command not found
/etc/X11/xinit/xinitrc: line 55: exec: xterm: not found
/etc/X11/xinit/xinitrc: line 54: xterm: command not found
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

root@imx6qpsabresd:~#

What is wrong? How do I get x11 running and be able to interact with it using the HDMI display and USB keyboard?

Perhaps other helpful boot messages:

U-Boot 2015.04imx_v2015.04_4.1.15_1.2.0_ga+gede7538 (Dec 13 2016 - 02:11:31)

CPU:   Freescale i.MX6QP rev1.0 at 792 MHz
CPU:   Temperature 32 C
Reset cause: POR
Board: MX6-SabreSD
I2C:   ready
DRAM:  1 GiB
PMIC:  PFUZE100 ID=0x10
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In:    serial
Out:   serial
Err:   serial
switch to partitions #0, OK
mmc1 is current device
Net:   FEC [PRIME]
Normal Boot
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
reading boot.scr
** Unable to read file boot.scr **
reading zImage
6618928 bytes read in 320 ms (19.7 MiB/s)
Booting from mmc ...
reading imx6qp-sabresd.dtb
47155 bytes read in 19 ms (2.4 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x64ff30 ]
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800e832
switch to ldo_bypass mode!

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.1.15-1.2.0+g77f6154 (osboxes@osboxes) (gcc version 5.2.0 (GCC) ) #1 SMP PREEMPT Mon Dec 12 19:36:54 GMT 2016
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Freescale i.MX6 Quad Plus SABRE Smart Device Board

Labels (1)
Tags (2)
1 Solution
1,145 Views
hansenmike
Contributor II

Yes. This info helped. I had to do this at the Uboot prompt:

setenv video 'mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'

setenv mmcargs 'setenv bootargs console=$,$ root=$ video=$'

saveenv

I had an incorrect OTG adapter. So now I can get a GUI and use keyboard and mouse over the OTG USB. Thank-you.

I have additional questions I will post separately.

Mike

View solution in original post

2 Replies
1,145 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Mike Hansen,

The image will boot using the LVDS port as default. If you have a LVDS display you should be able to see the GUI trough this port.

You may switch to the HDMI port for video using the u-boot parameters. You can find more information on the i.MX Linux Release Notes that accompany the BSP documentation. Please look for Table 10: Common kernel boot parameters.

You would need to set the environment variables within u-boot, which would look something like the following, depending on the desired resolution etc.

setenv video 'mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'

saveenv

As for the keyboard, it’s possible that it’s not working because the USB port available is an OTG port and you need either a compatible keyboard or an adapter or otherwise the keyboard won’t be enumerated correctly.

I hope this information helps!

0 Kudos
1,146 Views
hansenmike
Contributor II

Yes. This info helped. I had to do this at the Uboot prompt:

setenv video 'mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'

setenv mmcargs 'setenv bootargs console=$,$ root=$ video=$'

saveenv

I had an incorrect OTG adapter. So now I can get a GUI and use keyboard and mouse over the OTG USB. Thank-you.

I have additional questions I will post separately.

Mike