Hi all! This topic gathers users with HDMI issues on their UDOO, typically a blank black screen or, in few cases, wrong sizing. I want to let you know that the team is working to solve and patch these issues, where possible (read: software related issues). If your are experiencing problems with the HDMI output, follow our troubleshooting procedure: How can I solve my HDMI issues? If you need more help please post the results here before asking for support so we can better understand what's going on with your UDOO.
Hi, I also have a blank screen. Luckly I could test it on an other hdmi device which worked. My thoughts are that the initial 1920x1024@60 gives the problem, because I'm in Europe on 1920x1024@50. Just a thought. My rPi does work...so maybe you can compare the difference. Thanks.
Hello. I have the wrong sizing problem. I have a 1600x900@60 screen and the udoo is working at 1920x1020, so the os is a bit off the screen. I "fixed" the problem with an option on my screen, but the image is pretty bad. I hope you can fix that problem on a future update Gianluca.
I have a black screen too. Using Dell monitor, native resolution 1920x1200. I see in Xorg.0.log: [ 18.060] (--) VIVANTE(0): Virtual size is 1920x1080 (pitch 1920) [ 18.060] (**) VIVANTE(0): Built-in mode "current": 148.5 MHz, 67.5 kHz, 60. 0 Hz [ 18.060] (II) VIVANTE(0): Modeline "current"x0.0 148.50 1920 2008 2052 220 0 1080 1084 1089 1125 +hsync +vsync -csync (67.5 kHz) [ 18.060] (==) VIVANTE(0): DPI set to (96, 96)
In case you need the logs. For linux: http://pastebin.com/hixmAHCS For Android: http://pastebin.com/Hcq7FtPH
TV remains blank Hello there i also have the same issue. I have connected the udoo quad to my tv. nothing. then I have downloaded the newest android and unbuntu --> nothing displayed. I can connect to the unbuntu via Winscp and there I can see that the OS is working. any tips or hints what the issue could be? cheers B ps. Id suggest that in your how to guide you also just give the plain file name of the log. i found the kern .log found at /var/log is the pace to find the information. Now onward. i checked tht log and there is no hdmi-error but I exchanged my cable for another and used one that I know works still no picture. as my TV works other devices using the same cables work and the only thing that is not displaying anything is the Udoo, well I figure that it has the problem.. So I figure that I am also one of those people that need to get that HDMI patch. cheers B
I have blank screen when booting on my Asus 24" monitor, but normal display and complete boot when attached to my Sharp TV. My speculation is that the supplied Ubuntu does not like the EDID data coming back from the monitor. My monitor prefers resolution of 1920x1200. Raspbian, and ARM Archlinux work fine with this on Raspberry. The Android supplied with UDOO has similar behavior (to UDOO Ubuntu).
i have wrong size problem. i don't know the resolution of TV, and the Linux show the 1920x1080. please see the picture in thread:http://www.udoo.org/forum/viewtopic.php?f=2&t=213
I have wrong size/flickering problems: 1) On Motorola AT&T Laptop Dock Lapdock for ATRIX 4G 11.6" (1366x768 50 Hz) very bad display: little overscan/flicker/ bad display. On HDMI raspberry no problem at all, diplay was very good. With UDOO quad I get Warning message: Could not apply the stored configurationfor monitors none of the selected modes were compatible with the possible modes: Trying modes for CRTC 231 CRTC 231: trying mode 1920x1080 @60Hzwith output at 1366x768@60Hz (pass 0) Trying modes for CRTC 231 CRTC 231: trying mode 1920x1080 @60Hzwith output at 1366x768@60Hz (pass 1) 2) On Asus 24T1E (1920x1080 50Hz) overscan problem on HDMI 1 & 2, no way to adjust HDMI parametrs from monitor menu With UDOO quad I get Warning message: Could not apply the stored configurationfor monitors none of the selected modes were compatible with the possible modes: Trying modes for CRTC 231 CRTC 231: trying mode 1920x1080 @60Hzwith output at 1920x1080@60Hz (pass 0) Trying modes for CRTC 231 CRTC 231: trying mode 1920x1080 @60Hzwith output at 1920x1080@60Hz (pass 1) 3) Samsung TV 46" serie 8000 (TV UE46ES8000Q) (1920x1080 50Hz) initially overscan but with menu adjust (adapt to display) all is ok. The problem is that I cannot use main TV but I need to use both Asus 24" and specially 11.6" Atrix display. Is there possible to adjust from Ubuntu HDMI display parameters (resolution, automatic adjust) in any way ?
Ok, one thing I AM seeing with mine (drove me utterly nuts tonight...) I have mine set up as follows: Card #1 - set up with Ubuntu Card #2 - also set up with Ubuntu, but with the uboot set to mount / off of my SATA SSD drive (/dev/sda1) So, last night everything was working great, was booting off Card #2 to the SATA drive, got Java and Processing working. Did a clean shutdown. Today I get home from work, go to boot up, plug the PSU in, and nothing...... Go into the boot monitor and it's just hanging after detecting the USB devices... Power down, pop out Card #2, put in Card #1 - boots up fine. Shutdown clean, pop out Card #1, put in card #2, change boot config to mount / from the card. - Boots up fine. Reboot, change the uBoot to use the SATA again, nothing. Hangs right after detecting the USB devices. Power down. Unplug my USB Keyboard and USB mouse. Power up again with Card #2 and SATA, with uboot using the SATa for /. This time it hangs "waiting on device /dev/sda1" Power down. Plug in the keyboard. Power back up - Everything boots up fine!!! WTF??????? Now I'm utterly confused! Why woudl the keyboard be ok, but the mouse not off the SATA but both plugged in be find when coming off the SD card? I'm using the Udoo provided PSU.
Trying out udoo dual on dell U2412m monitor. Blank screen at first and then the monitor tells taht the current input timing is not supported bu the monitor display. Please change your input timing to 1920x1200x60Hz or any other monitor listed timing as per the monitr specifications. Well, it should also work on FHD 1920x1080. On the debug mode the board seems to get a bit scared of the screen, so it says: [ 1.089407] MIPI DSI driver module loaded [ 1.093588] mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi [ 1.100091] mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0x1a:0xa0:0xc1 [ 1.107110] fbcvt: 1920x1080@60: CVT Name - 2.073M9 [ 1.117889] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines [ 1.136158] imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~ 5), 5F(6,7) [ 1.169550] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines [ 1.195039] Console: switching to colour frame buffer device 160x64 [ 1.243183] mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver ldb [ 1.249612] _regulator_get: get() with no identifier [ 1.258242] imx-sdma imx-sdma: loaded firmware 1.1 [ 1.265826] fbcvt: 1920x1080@60: CVT Name - 2.073M9 [ 1.272148] imx-sdma imx-sdma: initialized [ 1.415520] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines And that's about it for the screen'n'stuff. I'll also format a card for the quad and try if it's any different. Meanwhile - could anyone tell me, wtf is up with the card and is there any option to set the required resolution via console? Edit: Forgot to mention the connection - HDMI to DVI-D cable is used.
There is an Env variable. You're aware of how to stop the boot process and change Env variables? We were talking someone through a resolution issue the other night (they had a strange res on their Pico projector. 854x480 iirc). There are utils to fetch the EDID information manually from a display and then you can put that into the X11 config. However it seems the utils has been depreciated on Linux so we didn't finish off the exercise. However it does feel to me (personal opinion) that the EDID isn't being handled well in all cases but no one (in the community) has yet got to the bottom of the issue nor a fix as yet but we've only just started down this path.
Tried on another screen (dell u2212hm) with a native 1920x1080 resolution. Still the same issue. The debug output is exatly the same. The same issue on quad model, too. No idea on changing env variables. How do I do it?
A quick summary is: * Ensure UDOO board is off * Connect a micro USB cable to the Serial Port (that's the one nearest the corner). It's official name is CN6 (and as the Serial port is shared, J18 jumper should be connected). * On your PC/Mac/Whatever run your favourite Terminal software. See the 'Getting Started' guide (section 7.2, pages 38 onwards for more details) * Turn UDOO on - you should soon see your Terminal software displaying lots of stuff as the UDOO boots. * Press 'any key' to stop the boot process when prompted to do so. * Type printenv Post your result back as a reply
Here it goes: bootdelay=3 baudrate=115200 ipaddr=192.168.1.103 serverip=192.168.1.101 netmask=255.255.255.0 loadaddr=0x10800000 rd_loadaddr=(0x10800000 + 0x300000) netdev=eth0 ethprime=FEC0 uboot=u-boot.bin kernel=uImage nfsroot=/opt/eldk/arm bootargs_base=setenv bootargs console=ttymxc0,115200 bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm bootargs_mmc=setenv bootargs ${bootargs} ip=dhcp root=/dev/mmcblk0p1 rootwait bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 3; mmc read ${loadaddr} 0x800 0x2000; bootm ethact=FEC0 videomode=video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 bootargs=console=ttymxc1,115200 root=/dev/mmcblk0p1 rootwait rw fixrtc rootflags=barrier=1 mem=768M arm_freq=996 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 boot_dev=mmc dev 2; ext2load mmc 2:1 10800000 /boot/uImage memory=mem=768M bootdev=mmc dev 2; ext2load mmc 2:1 root=root=/dev/mmcblk0p1 option=rootwait rw fixrtc rootflags=barrier=1 setvideomode=setenv videomode video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 lvdsres1= lvdsres2= cpu_freq=arm_freq=996 run_from_nfs=0 setbootargs_nfs=setenv bootargs console=ttymxc1,115200 root=/dev/nfs nfsroot=${ip_server}:${nfs_path} nolock,wsize=4096,rsize=4096 ip=${ip_local} ${memory} ${cpu_freq} ${videomode} setbootargs=setenv bootargs console=ttymxc1,115200 ${root} ${option} ${memory} ${cpu_freq} ${videomode} setbootdev=setenv boot_dev ${bootdev} 10800000 /boot/uImage bootcmd=run setvideomode; if test "${run_from_nfs}" = "0"; then run setbootargs; else run setbootargs_nfs; fi; run setbootdev; run boot_dev; bootm 10800000 stdin=serial stdout=serial stderr=serial Environment size: 1720/8188 bytes
Ok, well assuming the monitor connected is a 1920x1080 and supports 60Hz refresh then it seems fine at boot time. Is your issue with the CLI or a GUI or does it not get that far?
Arche, are you trying this with one of the preloaded cards from the Kickstarter, or a card you write the image to? Is this the latest 1.2 image? If not I would suggest imaging the card with the 1.2 release and try again.
Well, the first monitor I tried to connect was 1920x1200, but supports also 1080. The second one today was 1920x1080. I ordered just the boards as I already have some SD-cards and cables laying around so the images came from udoo website yesterday. Should be fresh. I accessed the console via USB cable and Tera Term. Haven't seen any output to screen as of yet. First it's blank and then it complains about the video timing being off. I myself started wondering if the fault could lie in a) both the screens I tested were IPS. Not wide gamut, though, so shouldn't be an issue really. But still. b) both screens have DisplayPort so I had to use HDMI to DVI-D cable to connect. Or anything else?
