Hi,
I have IMX6Q SABRE SDB bouard.
I am using pre-build android image to get Dual display working on IMX6Q. (android 13.4.1).
I want to get dual display output with HDMI and LCD display.
Following bootargs i have used. But I am not able to get any success. I got output in ant one display not on both.
setenv bootargs console=ttymxc0,115200 video=mxcfb0:dev=lcd,800x480M@60,if=RGB24,bpp=32 video=mxcfb1:dev=hdmi,1920x1080M@60 video=mxcfb2=off fbmem=28M
Any sugettions for my issue.
Thanks,
John
Solved! Go to Solution.
Regarding "HDMI + LCD", Please try "setenv bootargs console=ttymxc0,115200 video=mxcfb0: lcd,CLAA-WVGA@60,if=RGB565,bpp=32 video=mxcfb1: dev=hdmi,1920x1080M@60 video=mxcfb2:off fbmem=5M,28M".
Hi! How to set hdmi display on or off depending on the situation dynamically?
Did you met this problem?
Navigationbar not display well on hdmi, when lvds+hdmi dual display.
In android4.4.
Following the Advanced User Guide I was able to share my UI on HDMI display:
(I´m using LVDS, please try using WVGA and let me know if works the same way)
1 -
setenv bootargs console=ttymxc0,115200 init=/init rw video=mxcfb0:dev=ldb,LDB-XGA,if=RGB666
fb0base=0x27b00000
video=mxcfb1:dev=hdmi,1920x1080M@60 fbmem=10M,28M vmalloc=400M
2- Start the Advanced display setting by clicking HDMI notification in the Status bar.
3- Enable the HDMI display by clicking the "Enable Display", which will make the Android UI show in both LVDS and
HDMI display.
Please, let me know the result
Hello,
I downloaded the source code for Sabre-SD board, jelly bean android OS.
I am able to build the code and boot it also.
But when i am trying to do dual boot with LVDS as primary display and HDMI as secondary display i am unable to get anything on either of the displays, the following are the boot-args being used to enable dual display :
setenv bootargs console=ttymxc0,115200 init=/init rw video=mxcfb0:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb1:dev=hdmi,1920x1080M@60 fbmem=10M,28M vmalloc=400M
Please let me know what else have to be done.
In JB4.2.2 Quick Start, you can get the command for Dual display:
3.4.3 Booting with Dual Displays: LVDS and HDMI Displays
In the U-Boot prompt, set the U-Boot environment variables as shown below:
U-Boot > setenv bootcmd booti mmc3
U-Boot > setenv bootargs console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M
init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=hdmi,1920x1080M@60,bpp=32
video=mxcfb2:off fbmem=10M androidboot.hardware=freescale
U-Boot > saveenv
If you find it can not work, please check your boot log and see whether the display is detected
I've gotten this to work. But I want to not mirror the same contents to both displays.
I want to have two separate and different contents on each display. How?
- Eric
I will not be able to test it myself until next Wednesday - I'm sorry -
Did you tried the command lines separated? (once for LVDS, once for HDMI?)
Could you, please, check the User Guide in order to see the command line you need to include (it's something related with setprop.dualXXX) in order to get dual display enabled on Android?
Can you please try with
video=mxcfb0:dev=ldb,LDB-XGA,if=RGB666 ldb=dul0 to boot up on LVDS and then you change. Please keep posted whether it fixes the problem.
I want to get dual display one with HDMI and LCD.
Regarding "HDMI + LCD", Please try "setenv bootargs console=ttymxc0,115200 video=mxcfb0: lcd,CLAA-WVGA@60,if=RGB565,bpp=32 video=mxcfb1: dev=hdmi,1920x1080M@60 video=mxcfb2:off fbmem=5M,28M".
Is it even possible to have two displays show different output in Android? I don't think Google supports that, but I'd love to be proven wrong.
I'd actually want one framebuffer to span across two LVDS panels. Can it be done with i.MX6?
Thanks,
-Ben
JellyBean 4.2 supports multiple display. Different contents can be supported.
where can i found JellyBean ?
You can contact sales or marketing to get Jelly Bean information.
Try this for LCD "setenv bootargs console=ttymxc0,115200 video=mxcfb0: lcd,CLAA-WVGA@60,if=RGB565,bpp=32 video=mxcfb1: dev=hdmi,1920x1080M@60 video=mxcfb2: off fbmem=5M,28M".
If it doesn't work, please send out the logs.
Ticket was already create for this issue, SR 1-1006680555.
It was assigned and follow up will be provided in the SR.