I got my gui to work on my tv. However after following the setenv commands its on 640X480 rather than 1920X1800 any suggestions?
In relation to my last reply ubuntu showed up on 2/4 of the screen. | |##| | the hashtags show the screen picture and the | are the black sides next to the image. However on android the picture only goes over on only a inches or two. I need to figure out how to customize the resolution.
I know this is a long thread now, but it is a case of reading backwards from this point as here you find all our knowledge on fixing this issue, step by step.
So I loaded the latest image in hopes of getting a picture on my ASUS HDMI monitor, it actually gave me a picture without any modifications, accept it is still the fuzzy green picture, my monitor accepts 1920x1080@60 per its specs. Any ideas how to clean up the picture now that I have one? Thanks
Hi, I got the same issue with my Panasonic TV. It works fine with a normal HDMI Display. For Linaro 11.x: Setting the videomode with the M and D parameter, at least gives me an image but as already mentionned by andrewhennessy, only in vga settings (640x480). I tried to look up the different HDMI Setting for my tv but changing the parameters didn't change a lot. (Changed Frequency, resolution and the optional parameters.) The only thing I didn't know how to set, was the horizontal and vertical frequency. Anybody has an idea how to set those two explicit? For Linaro 12.x: Setting videomode has no effect. As I saw in the boot variables, the setvideomode never gets called. Trying to add that call in a step, resulted in an Udoo not starting anymore. :roll: :lol: My knowledge in Linux Hardware Errors debugging isn't very great, does anybody have some sources fur further reading? Thx in advance.
That is true, now video command is integrated with console ,baudrate, etc. in mmcargs In u-boot command prompt, Code: printenv mmcargs output will be, Code: mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot} ${hdmi_patch} fbmem=24M video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 To add a custom resolution, Eg. 1024x768, 85Hz Code: setenv mmcargs 'setenv bootargs console=${console},${baudrate} root=${mmcroot} ${hdmi_patch} fbmem=24M video=mxcfb0:dev=hdmi,1024x768M@85,bpp=32' save the settings Code: saveenv
Hi all, i have a panasonic tv plasma 42 in. and on boot i get black video. Followed your instruction and made all check. Finally i got the "No size specified (using byte-data access)". Now what? Pls help. i don't have any clue about how going any further to start using Udoo board. Thank you max
Struggling to detect my monitor DELL U2412 and finally got it working. Error message on the monitor was "The current input timing is not supported by the monitor display...." Error from Udoo console "Error: HDMI is not ready!" Tried fixes on this thread, however UDOO kept on defaulting back to auto-detected panel HDMI Display: HDMI (1024x768) What worked for me was the information below posted by Lifeboat_Jim viewtopic.php?f=19&t=589&p=4657&hilit=display+hdmi#p4657 "in the latest uboot. don't forget you can 'editenv mmcargs' which makes it easy, then 'saveenv' and 'boot'." Screendump from my console, once I've set the correct resolution monitor worked :mrgreen: U-Boot 2013.10-rc3-svn109 (Nov 27 2013 - 17:36:22) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: UDOO DRAM: 1 GiB MMC: FSL_SDHC: 0 auto-detected panel HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 UDOO board => editenv mmcargs edit: setenv bootargs console=${console},${baudrate} root=${mmcroot} ${hdmi_patch} fbmem=24M video=mxcfb0:dev=hdmi,1920x1200M@60,bpp=32 UDOO board => saveenv Saving Environment to MMC... Writing to MMC(0)... done UDOO board => boot Hope the information is useful to somebody!
Ok so... The first time I booted my Udoo Quad, a couple of weeks ago, into Ubuntu 11, it all went fine and the video should up on the display. Today I burn the Android image onto the SD card, boot... and run up into this HDMI issue. I tried patching, to no avail. I tried burning Ubuntu 12, to no avail. I tried re-burning Ubuntu 11, to no avail. I also brought the display back to factory settings, to no avail. What the hell? In 2013 it was working!!! What went wrong? BTW, no "edid" information pops up in the log ( I scrolled through, and typed "dmesg | grep edid" just to make sure) via serial debug monitor. Furthermore, this is the edid info printout... I think I deleted the U-Boot env variables set while patching (by leaving the value blank when using setenv), but am not sure. Code: ubuntu@imx6-qsdl:~$ sudo i2cdump -f -y 1 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 00 ff ff ff ff ff ff 00 22 f0 32 30 01 01 01 01 ........"?20???? 10: 24 17 01 03 80 33 1d 78 2a e2 95 a2 55 4f 9f 26 $????3?x*???UO?& 20: 11 50 54 a1 08 00 d1 c0 81 c0 81 80 95 00 a9 c0 ?PT??.???????.?? 30: b3 00 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c ?.?????:??q8-@X, 40: 45 00 fd 1e 11 00 00 1a 00 00 00 fd 00 32 4c 18 E.???..?...?.2L? 50: 5e 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 48 ^?.? ...?.H 60: 50 20 32 33 78 69 0a 20 20 20 20 20 00 00 00 ff P 23xi? .... 70: 00 33 43 4d 33 33 36 30 42 52 31 0a 20 20 01 6e .3CM3360BR1? ?n 80: 02 03 14 b2 49 90 9f 04 13 03 02 12 11 01 65 03 ????I?????????e? 90: 0c 00 10 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 ?.?.?:??q8-@X,E. a0: fd 1e 11 00 00 1e 02 3a 80 d0 72 38 2d 40 10 2c ???..??:??r8-@?, b0: 45 80 fd 1e 11 00 00 1e 01 1d 00 72 51 d0 1e 20 E????..???.rQ?? c0: 6e 28 55 00 fd 1e 11 00 00 1e 01 1d 00 bc 52 d0 n(U.???..???.?R? d0: 1e 20 b8 28 55 40 fd 1e 11 00 00 1e 8c 0a d0 8a ? ?(U@???..????? e0: 20 e0 2d 10 10 3e 96 00 fd 1e 11 00 00 18 00 00 ?-??>?.???..?.. f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9c ...............?
:: UPDATE :: OK, in my case the HDMI problem was caused (it appears) by the USB dongle for keyboard and mouse: I had plugged it in the lower USB port. Apparently when a USB mouse is missing (in my case, I guess, because it wasn't plugged in the right port), the board gives HDMI problems? Anyhow, I successfully booted in Ubuntu 11. Am currently burning Android back to the SD card!
Hello fellow UDOO – users, I want to use my UDOO with a Panasonic TV via HDMI. Now everything that I try, results in a blank screen. I then checked the manual (shock) and found that the TV does HDMI in the resolution 1080/60i,50i 1080/60p,50p,24p So far when looking at what is posted here as HDMI it is always 1920x1080. And looking at theXorg.0.log even says: Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p1 rootwait rw fbmem=24M video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 So therefor I have to assume that the whole setup is not correct, there is no scan for the correct resolution. So that opens the question as to where can I set this parameter? Thnx B
Hi guys, I had also a problem with my Dell U2412M - no life sign on screen. I solved it by connecting the Udoo to my A/V Receiver (Onkyo 818), who converts any incoming HDMI signal to the fitting format for my TV. That worked immediately.. now I need to change the settings that makes it run with my Dell screen... Regards, Mario
I everybody I have an overscan issue on my samsung tv. It doesnt support the change of scan option so I have to solve it via software. I tried xrand but it didn't work for me how can I set underscan to compensate overscan? ( I'm using linaro image from this site) Thanks for your attention
I hope this does not upset people on here.. But I unboxed my Udoo plug it into the mains via a 12volt 2 amp power supply Unwrapped the HDMI cable that i purchased from the Udoo shop and then plugged it into my old Panasonic TH-50PV500B Switched it on and I got the desk top in about 20 seconds and it all seems to work fine. Now i am just lucky or is it my 50"and its resolution that had helped here ?? I know some of you guys are having problems, just wondered if mine working would shed some light on any thing?. just thought i would show its not all doom and gloom
Hi there, So I'm also getting this annoying "The current input timing is not supported by the monitor display. Please change your input timing to 1920x1080 60Hz" message, Monitor model - Dell u2312hm (with dvi input) It appears that I have the same issue as dnetman99. Who I believe didn't get any solution. so last lines of booting are: Code: [6.521326] ERROR: v4l2 capture: slave not found! [ 6.529041] ERROR: v4l2 capture: slave not found! [ 8.067030] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines Ubuntu 12.04 LTS udoo ttymxc1 my env - http://pastebin.com/qF9A2m9G Any help would be appreciated. P.S A small background story: because of a faulty discrete video card, I could not use my notebook as an external monitor, so I bought udoo to power it up, both of them are idle now
I have changed resolution to 1280x1024M@60 and it works now. I still wonder what's wrong with full HD.
I have exactly the same problem as you... OS is up and running but I get exactly the same errors: Code: [6.521326] ERROR: v4l2 capture: slave not found! [ 6.529041] ERROR: v4l2 capture: slave not found! [ 8.067030] imx-ipuv3 imx-ipuv3.0: WARNING: adapt panel end blank lines Any help? I'm using a Hanns-G HL229 monitor with an DVI Adapter
Hanns-G HL229 I don't know if these error messages have anything to do with display issue, I'm waiting for the answer too. Have you tried setting a resolution to lower one? As I said for me it works on 1280x1024M@60. I suspect an issue could be with DVI monitors, Hope someone from community will help us...
Haven't had any free time to tinker for quite a while but now at last I can report a win. Totally. And udoo is awesome!! Also - to make life easier for you, guys, here's how you can get Dell U2412M up and running. Step by step. Or at least, that's how I finally did it. Confirmed working: Ubuntu studio 12.04, HDMI to DVI cable (will update here if I find out something new.) 1. Tinkered with edid files. Got the info off the monitor with phoenix, checked it basically bit by bit. More information about edid from https://en.wikipedia.org/wiki/Extended_display_identification_data First I created a new file /etc/edid.txt and made it 127 characters long with nano editor (via serial connection) Code: nano /etc/edid.txt Then I downloaded shed (Simple Hex EDitor) to do the bit by bit edit Code: apt-get install shed shed /etc/edid.txt To save you from wasting the time on checking and getting the edid for the monitor, I'll add the files here. One for analog, another for digital. I used digital but there's another one if you need it. 2. Then I messed around with the env variables (you get there by interrupting boot on serial connection). got a messy 720x400 screen when putting in 1920x1200M@60 with no option to resize. Tried to set up another resolution with xrandr (running linux desktop at aforementioned resolution) but to no avail. Continued with the setenv. Final working setenv commands are (I replaced the needed stuff everywhere I found it...) Code: printenv check all the env variables, find parts that include HDMI and resolution. I found 3. For U2412M use 1920x1200@60 for video mode. So I ended up with 3 different setenv commands: Code: setenv bootargs console=ttymxc1,115200 root=/dev/mmcblk0p1 rootwait rw fbmem=24M video=mxcfb0:dev=hdmi,1920x1200@60,bpp=32 setenv mmcargs setenv bootargs console=ttymxc1,115200 root=/dev/mmcblk0p1 rootwait rw fbmem=24M video=mxcfb0:dev=hdmi,1920x1200@60,bpp=32 setenv videomode video=mxcfb0:dev=hdmi,1920x1200@60,bpp=32 And to make things permanent Code: saveenv And to continue with boot procedure Code: boot 3. I suppose that this should do it and the next time you should have your dell baby running like a champ. However if you find yourself in need of other resolutions - you have some options: Code: Dell U2412M supported resolutions Display Mode Horizontal Freq (kHz) Vertical Freq (Hz) Pixel Clock (MHz) Sync Polarity (Horizontal/Vertical) VESA, 720 x 400 31.5 70.0 28.3 -/+ VESA, 640 x 480 31.5 59.9 25.2 -/- VESA, 800 x 600 37.9 60.3 40.0 +/+ VESA, 1024 x 768 48.4 60.0 65.0 -/- VESA, 1280 x 1024 64.0 60.0 108.0 +/+ VESA, 1600 x 1200 75.0 60.0 162.0 +/+ VESA, 1680 x 1050 64.7 59.9 119.0 +/- VESA, 1920 x 1080 66.6 59.9 138.5 +/- VESA, 1920 x 1200 74.0 60.0 154.0 -/+ I found these values in the user manual downloaded from dell product support page - I suppose other dell screens will have their data marked up the same way and maybe some other manufacturers do the same thing And to create a new resolution you just need to fire up the terminal (in linux desktop mode on udoo, not via serial) and do it with xrandr. An excellent step-by-step guide can be found at https://wiki.archlinux.org/index.php/xrandr -I used that one to get the job done. However I still used the matching values from the table to create a new resolution - the cvt call returns some different data. Code: #1920x1200 59,88Hz(CVT2.30MA) hsync:74,56kHz; pclk 193.25 MHz Modeline "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync #1920x1080 59.96 Hz (CVT 2.07M9) hsync 67.16kHz; pclk:173.00MHz Modeline "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync Almost done - as at the time I hadn't finished with env tinkering and tried to solve the 720x400@70Hz issue. Didn't help, And after the env variables being set I didn't need that any more. But the info is here just in case you need it. 4. Fire up UDOO on the WUXGA resolution. Like a boss. Enjoy. Try to avoid jizzing in your pants. edit: 18.2.14 - corrected some typos, added some clarifications to differentiate actions done in serial debug mode and linux desktop.
