I seem to be having a different problem with the HDMI connection than everyone else here. I had a old 720p resolution monitor connected to my quad with a hdmi-dvi-d cable. Worked fine. Now I connected a newer 1080p monitor with a hdmi-hdmi cable, and can't get any picture at all. (monitor and cable works with a laptop without problem) dmesg | grep hdmi: [ 0.253369] mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 [ 0.253492] mxc_sdc_fb fb.23: registered mxc display driver hdmi IPU1_DISP0 [ 0.253506] mxc_sdc_fb fb.23: registered mxc display driver hdmi [ 2.042961] imx-audio-hdmi sound-hdmi.18: hdmi-hifi <-> hdmi_audio.3 mapping ok [ 2.126334] #1: imx-hdmi-soc [ 2.226646] mxc_hdmi 20e0000.hdmi_video: same edid [ 3.115011] mxc_hdmi 20e0000.hdmi_video: same edid I'm guessing the problem is the "same edid" lines. But I haven't been able to find anything on the internet on what the problem is, or how to fix it. edit: using UDOObuntu 2 beta 3 edit2: reburning the SD card and having the acer G237HL 1080p hdmi hooked up produces a black screen. Monitor does "wake up", but no picture. dmesg | grep hdmi [ 0.253367] mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 [ 0.253492] mxc_sdc_fb fb.23: registered mxc display driver hdmi IPU1_DISP0 [ 0.253505] mxc_sdc_fb fb.23: registered mxc display driver hdmi [ 2.042947] imx-audio-hdmi sound-hdmi.18: hdmi-hifi <-> hdmi_audio.3 mapping ok [ 2.118704] #1: imx-hdmi-soc dmerg | grep edid ,command produces no output. Very strange! I'll try some of the remedies suggested to others, again.
Disconnecting and reconnecting the 1080p hdmi monitor reproduces the "same edid" messages as previously. So the messages are not related to the other 720p monitor.
Update: downloaded and burned UDOObuntu 2 beta 2. Worked out of the box! But the nice stuff from beta 3 aren't there, of course. I'll open a ticket! Would be great to get beta 3 working.
Happy for you but point is, Beta 2 was based on a previous kernel. Anyway we are close to RC1 for UDOO Quad Maybe by the end of this week!
@Oskar I had similar issues. On UDOOBuntu beta2 all fine on any previous version black screen. Are you able to get EDID information from your Monitor? $ sudo i2cdump -f -y 1 0x50 OR root@udooqdl:~# find /sys -name "*edid*" /sys/devices/soc0/soc.0/20e0000.hdmi_video/edid root@udooqdl:~# cat /sys/devices/soc0/soc.0/20e0000.hdmi_video/edid | hexdump -C 00000000 00 ff ff ff ff ff ff 00 1e 6d 7e 58 7c 75 05 00 |.........m~X|u..|-C 00000010 08 16 01 03 80 33 1d 78 ea 5e a5 a2 55 4d a0 26 |.....3.x.^..UM.&| 00000020 11 50 54 21 08 00 b3 00 81 80 81 40 71 40 01 01 |.PT!.......@q@..| 00000030 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c |.......:..q8-@X,| 00000040 45 00 fe 22 11 00 00 1e 00 00 00 fd 00 38 3d 1e |E..".........8=.| 00000050 53 0f 00 0a 20 20 20 20 20 20 00 00 00 fc 00 49 |S... .....I| 00000060 50 53 32 33 35 0a 20 20 20 20 20 20 00 00 00 ff |PS235. ....| 00000070 00 53 65 72 69 61 6c 20 4e 75 6d 62 65 72 01 4f |.Serial Number.O| 00000080 02 03 1d f1 4a 90 04 03 01 14 12 05 1f 10 13 23 |....J..........#| 00000090 09 07 07 83 01 00 00 65 03 0c 00 10 00 02 3a 80 |.......e......:.| 000000a0 18 71 38 2d 40 58 2c 45 00 fe 22 11 00 00 1e 01 |.q8-@X,E..".....| 000000b0 1d 80 18 71 1c 16 20 58 2c 25 00 fe 22 11 00 00 |...q.. X,%.."...| 000000c0 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 fe 22 11 |....rQ.. n(U..".| 000000d0 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 fe |....... .-..>...| 000000e0 22 11 00 00 18 00 00 00 00 00 00 00 00 00 00 00 |"...............| 000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e6 |................| 00000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 In my case I could fix the display issue by reducing the video mode to 720p in uBoot => setenv video 'video=mxcfb0:dev=hdmi,1280x720@60,bpp=32' => saveenv => res Maybe it is worth to play arround with the modes in the UDOOBuntu Beta2 first. BTW the guys from UDOO made some nice trouble shooting guide on HDMI issues.
Gave up on the hdmi issue. Ordered a UDOO 15.6" touch screen instead, it's now running and working on rc1. We are going to use a 10", 12", 15" or some such size lvds touch screen for our X-EMS project anyway, so I don't want to put in more time on the hdmi issue now. We might want to run dual screens some time later though. Will definitely need the hdmi then, but not sure if there are issues with dual screen on linux or not.
Hi guys, I just received my Waveshare 7" touchscreen Display from Amazon. With It's resolution of 1024x600pixels (and a refresh rate of 43 hz -under windwos) i am having troubles on getting it to work with my Udoo Quad (kickstarter version) on the new Udoobuntu 2 rc1 (15.1.2016)... First off all i was wondering if the Udoo-Config-Application went missing and secondly i dont understand why i am betting a strange output in terminal on typing "xrandr" udooer@udoo:~$ xrandr Screen 0: minimum 240 x 240, current 1920 x 1080, maximum 8192 x 8192 DISP3 BG connected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm S:1920x1080p-60 60.0*+ S:1920x1080p-50 50.0 S:1920x1080i-60 30.0 S:1920x1080i-50 25.0 S:1920x1080p-24 24.0 S:1280x720p-60 60.0 S:1280x720p-50 50.0 S:720x576p-50 50.0 S:720x480p-60 59.9 V:640x480p-60 60.0 S:640x480p-60 59.9 I would like to add a new display configuration but what exactly is the name of my output device? I am seeing "DISP3" as well as "BG", but on doing the following in my terminal: udooer@udoo:~$ cvt 1024 600 43 # 1024x600 42.67 Hz (CVT) hsync: 26.37 kHz; pclk: 33.75 MHz Modeline "1024x600_43.00" 33.75 1024 1056 1152 1280 600 603 613 618 -hsync +vsyncfollowed by udooer@udoo:~$ xrandr --addmode DISP3 1024x600-43or udooer@udoo:~$ xrandr --addmode BG 1024x600-43 only results in xrandr: cannot find output "DISP3"What am i doing wrong? What's the real name of the Display Output? And how do i find it out/ create a new setting for xrandr?? In the end is this actually the right approach? Looking forward for your Help!!! Cheers ji p.s. the capacitive touch is working out of the box!! (so is the screen, both on windows, mac and even during startup of the udoo....After booting i only get white and black squares, which i believe is due to the incorrectly set refresh-rate
Hi guys, to be honest i was expecting more help from the forum (and the admins )... i just wanted to let you you know, that the basic approach with xrandr including generation of a new display mode is actually the way to go! I was able to get my waveshare 7" monitor working on the older udoobunut 12.04-distribution (didnt work out of the box...). Xrandr produced "default" as single screen and i added a resolution setting (using cvt and xrandr -addmode) to finally restart the udoo, resulting in a crisp image on my screen! I am still wondering what happened to the configuration tool on the new udoobuntu 2 and would greatly appreciate if a linux power user could try to run the xrandr command on their udoo to tell me what the terminal replies/ which "screen" i have to address with --addmode command to get things running on the newer distro. Since i was used to the older distro (i am a kickstarter backer), i am wondering if it´s just me or if udoobuntu two is actually slower on the gui-side (especially the animation on moving windows seems inferior) Last but not least, i want to thank the udon-team again for this great platform! I was away from it for quite some time, but i can definitely see, why i backed it! And i would do it again (missed the neo..) thanks and keep up the work! Cheers JI p.s.: In case anyone is interested, i managed to get the waveshare 7" display working by creating a new .conf file in the /etc/X11/xorg.conf.d ! Since i am not on the udon right now, i will add the file content later
Hi JI, Please do post your conf file! I'm trying to get this exact display working on the Quad running Android. Thanks!
Dear @ji11x38, I'm sorry if our support is not enough. I hope to give you some useful answer in short time.
Hi Andrea, Sorry, i would say my comment was actually badly written... I didn´t want to complain to much.. I love my udoo and I love communities and was just hoping that someone could pinpoint me in the right direction, while not actually think that i´d get a fast reply... i was just sarcastic on a slow reply. Since I managed to get stuff done, i am actually happy to share what i found out and would be grateful to get a feedback on the" xrandr" output the udoo gives(since i don't understand it ) and why it looks the way it does/ how to "talk" to the display-settings. @Matt: I will be home really late today and have lots of things to do (including getting up early tomorrow...) so i don´t know if i can upload the content of my .conf.... Anyways since you are using Android, i actually have no clue if this file is going to work... Does Android actually use a similar system including a window manager as X11? And if so, what is it´s name?/ Where does it store configs and the other stuff? (I am a android noob on the programming side and just curious about it! Didn't had the time to play around with ) Cheers ji p.s.: here we go a small how to on getting the waveshare 7" to run in udoobuntu: Create a file (e.g. 10-monitor.conf )in cd /home/udooer# cd /etc/X11/xorg.conf.d/ add those lines and create a file called "10-monitor.conf" Section "Monitor" Identifier "DISP3" Modeline "1024x600_43.00" 33.75 1024 1056 1152 1280 600 603 613 618 -hs$ Option "PreferredMode" "1024x600_43.00" EndSection Section "Screen" Identifier "Screen0" Monitor "DISP3" DefaultDepth 24 SubSection "Display" Modes "1024x600_43.00" EndSubSection EndSection Section "InputClass" Identifier "calibration" MatchProduct "3M 3M USB Touchscreen - EX II" Option "Calibration" "1853 14628 2589 14106" Option "SwapAxes" "1" EndSection restart the udoo (turn of the background light of the monitor during boot) and voila you should see your desktop on the screen (the touch might not work on the first boot, but in theorie it should work, too -> added the "callibration" and started the callibration-application in system tools)
Thanks for the info @ji11x38. Android doesn't use x11 - I'm not entirely sure what it does use to be honest. I was hoping your solution might give me some clues about how it might be solved on Android. All I've found so far are 3 config files under /etc/ display_mode_fb0.conf display_mode_fb2.conf display_mode_fb4.conf which as far as I know are loaded by the driver directly. To get any further I may have to download the Android sources to see what's going on under the hood... I'm a complete noob when it comes to displays tbh
hi, i am having some trouble with getting the right size for my little 5 inch HDMI lcd screen.. my start menu is falling out of my screen so its hard to get the right window to configure the reselution. next to that. when i am finaly at the right window its inpossable to calibrate the reselution to my 5 inch HDMI lcd screen. please help im kinda stuck.
There's no way I know you can rescale the windows unless you overscale the screen itself (if possible).
It looks like I found a solution, It at least works on my screen on the yocto build. (I am using the same kernel as UDOObuntu) After applying this patch the HDMI screen works fine for me: Code: Index: kernel-source/drivers/video/mxc/mxc_hdmi.c =================================================================== --- kernel-source.orig/drivers/video/mxc/mxc_hdmi.c +++ kernel-source/drivers/video/mxc/mxc_hdmi.c @@ -1813,10 +1813,11 @@ static void mxc_hdmi_edid_rebuild_modeli */ mode = &hdmi->fbi->monspecs.modedb[i]; - if (mxc_edid_mode_to_vic(mode) != 0) { - - dev_dbg(&hdmi->pdev->dev, "Added mode %d:", i); - dev_dbg(&hdmi->pdev->dev, + if (!(mode->vmode & FB_VMODE_INTERLACED) && + mode->xres <= 1920 && + mode->yres <= 1080 ) { + dev_info(&hdmi->pdev->dev, "Added mode %d:", i); + dev_info(&hdmi->pdev->dev, "xres = %d, yres = %d, freq = %d, vmode = %d, flag = %d\n", hdmi->fbi->monspecs.modedb[i].xres, hdmi->fbi->monspecs.modedb[i].yres, This is a rebased version of this patch. Maybe @Francesco can check this past an create a test kernel/image.
I hope this solves this issue. If not more debugging will be needed. Gesendet von meinem FP2 mit Tapatalk
If anyone wants to try my patch I've just uploaded a test image based on Yocto for the Quad/Dual boards. You can follow the instructions on the getting started guide to flash the SD-Card (after extracting the zip archive) if it works you'll see a splash screen like in this video Except with the UDOO logo. The first boot takes really long because the SD-Card is resized.
