AnsweredAssumed Answered

HDMI not working on imx6q sabre auto AI

Question asked by Suhas Kaundinya on Mar 30, 2018
Latest reply on Apr 9, 2018 by Suhas Kaundinya

Hello,

 

I am using imx6q sabre auto ai board.

I have just flashed the android oreo images onto an sdcard and tried to boot it to an lvds 10" display and it is working fine.

But when I tried to boot it using HDMI display, there is no output on either the screen or the linux console.

While booting, in the u-boot prompt, I gave the following commands.

 

=> setenv bootcmd boota mmc1

=> setenv bootargs console=ttymxc0,115200 androidboot.console=ttymxc0 consoleblank=0 vmalloc=128M init=/init          video=mxcfb0:dev=hdmi,1280x800M@60,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off       androidboot.hardware=freescale cma=448M galcore.contiguousSize=33554432 androidboot.selinux=permissive

=> saveenv

 

When I tried to boot the same for dual displays, lvds worked fine but not hdmi.

I connected an adb cable to see the log and I found the follwoing:

 

01-01 00:11:24.251   290   290 I display : try dev:/dev/dri/card0
01-01 00:11:24.252   290   290 E display : Failed to set atomic cap -1
01-01 00:11:24.252   290   290 I display : entry:fb1 get fb1
01-01 00:11:24.252   290   290 I display : fb1 is overlay device
01-01 00:11:24.252   290   290 I display : entry:fb0 get fb0
01-01 00:11:24.253   290   290 I display : fb0 is hdmi
01-01 00:11:24.253   290   290 I display :  device
01-01 00:11:24.253   290   290 I display : fb0 device plugin
01-01 00:11:24.310   290   290 W display : xres         = 1280 px
01-01 00:11:24.310   290   290 W display : yres         = 720 px
01-01 00:11:24.310   290   290 W display : fps          = 60.00 Hz
01-01 00:11:24.310   290   290 W display : bpp          = 32
01-01 00:11:24.310   290   290 W display : r            =  0:8
01-01 00:11:24.310   290   290 W display : g            =  8:8
01-01 00:11:24.310   290   290 W display : b            = 16:8

 

I can see that y-resolution is 720 even though I gave 800 in the kernel command line.

Is there any other place from where it might be taking that resolution?

Suggest me on this.

 

BR,

Suhas R

Outcomes