VPeter, I'm a few steps lower than a NOOB. Is it correct if I search for the file uEnv.txt . Where can I find this file? And the change Code: video=mxcfb0:dev=hdmi Or clould you please give me a short procedure? much obliged
Yes, to use Kodi with LVDS you should change the uEnv.txt file (in the root dir) (different from UdooBuntu, where we use uboot). It should be: Code: video=mxcfb0:dev=ldb,1366x768M@60,if=RGB24,bpp=32 Let me know if this works for you.
I just reinstalled openElec 5. like discribed in the first thread. But Your talking KODI. A bit confusing for me. It's no prob wich I install, as long something would work.... Do I performthis action via a serial connectien? Code: U-Boot 2013.10-rc4 (Feb 28 2015 - 11:48:39) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: UDOO DRAM: 1 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 146 bytes read in 7 ms (19.5 KiB/s) Importing environment from mmc (uEnv.txt)... Checking if uenvcmd is set ... Running default loadimage ... 7024832 bytes read in 314 ms (21.3 MiB/s) 32300 bytes read in 16 ms (1.9 MiB/s) Booting from mmc ... Kernel image @ 0x12000000 [ 0x000000 - 0x6b30c0 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800ae2b Starting kernel ... My HDMI connectio to the TV is not connected. fyi. (You would take my hand an guide me please)
Put SD card in USB reader and put it on some Windows machine (I assume you are using Windows). Open file uEnv.txt on sd card and edit this file according to info mikelangeloz provided. Then you should see output on your screen.
You are correct I use Windows. Do You mind if I start all over again? I'm sorry for you'r patience. Ik make a SD card ready. Format in fat32 with SDFormatter. Then I put an "udoo_quad_android_v4.4.2-1.0" file on it. Then I can start the UDOO Quad. So far so good? (thanks)
Quit right, sorry for my mistake. I put the image Code: OpenELEC-imx6.arm-5.0.4-udoo_quad.img On my SD card. I see the proper file A complete replacement of this file of just overwrite the correct data.... LDVS screen stays dead.... When I run Lubuntu, the screen works as it schould be... I'm willing to follow every lead to get this "thing" working....
Original file: Code: mmcargs=setenv bootargs 'boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0' New File Code: mmcargs=setenv bootargs 'boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=ldb,1366x768M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0'
Thats the serial output Code: U-Boot 2013.10-rc4 (Feb 28 2015 - 11:48:39) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: UDOO DRAM: 1 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 144 bytes read in 7 ms (19.5 KiB/s) Importing environment from mmc (uEnv.txt)... Checking if uenvcmd is set ... Running default loadimage ... 7024832 bytes read in 314 ms (21.3 MiB/s) 32300 bytes read in 16 ms (1.9 MiB/s) Booting from mmc ... Kernel image @ 0x12000000 [ 0x000000 - 0x6b30c0 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800ae2b Starting kernel ... Black screen...
Just for the fun of it, I connected my HD tv on..... And with very bad synchro, i see the startup Opelenec. But my LVDS UDOO screen stays black!
Hi all I found this image a few days ago and I absolutley LOVE it!!!! This is exactly what Ive been searching for I got one request: thet arduino reset problem... I would love too use the arduino on the board as well but I am a bit a noob when it comes to recompiling this image myself... For now I'm using the gpios directly using the imx.6 which also works but I would really like to use the sam3x as well I'm currently running v 5.0.6 (When I run openelecs update to 5.0.8 it crashes...) Best Regards Lukas lbsfilm.at
Can u run OpenElec on the LVDS screen or on you'r HDMI screen? Does the audio comes from HDMI or via the audio output?
@s00500: The issue with arduino reset problem is known. I already started working on it but as you maybe seen I stopped working on imx6 support for Udoo (and TBS Matrix). Last image is v5.0.6 and probably there will be no more from me. My intention from the start was pushing all the required changes to openelec repository. Also some other changes for other imx6 hardware (tbs matrix, wandboard, also cubox-i, ..). To at least having all the sources in one place. And the image can be build by me if there is no official image provided. It was all agreed with Stephan (main developer) in last december. But then merge newer happen. Also no response from Stephan. No idea why not. So I gave up because don't have much interest anymore if I don't have nothing in return - not even satisfaction of seeing my work included. Also I didn't see much moral support for this on IRC or Github. I know this will affect lot of users but reality is hard. And I did start look first on myself and then others. Usually I don't gave up on such things but everything is first time. @ivan: HDMI works and audio come from it. No analog audio support. No idea for LVDS screen. I don't have it and don't have any intention to buy it to test or make openelec working with it. Because above applies to this issue also.
I'm awere of all the effort you put in this project. I'm you very grateful for it. But, if the UDOO Team/Owners don't give you support, your nowhere. The Add that Udoo "contains" 6 Raspberries is a fraud. What I'm trying to do is looking for a proper HDMI-adaptor for this screen. (more costs). Peter, I'm not a programmer. My goal was to pusch Udoo Team in action. But they fell in sleep.... And it is hard to wake them up. They are focussed up there new kickstarter board. But, as for me..... I have my doubts is there is a market for. My ultimate goals war creating a CAR-XMBC-Udoo. Bummer. I do feel sorry if I offended you in any way. Don't take this blame for you, passed true the UDOO Team. Yours sincerely Ivan
How often can we expect updates? Right now in the first post is Version 5.0.4 and on the OpenElec Site 5.0.8 (and 5.95.1 beta). On Kickstarter and in the first few months we got promised there will be an XBMC/KODI support most probably through OpenElec (my preferred option) But we had to wait very long. Mark Ruffino made here the first (public) port and afterwards there where some Images direct from you vpeter. But it don't seems there will be any real support for my Udoo. I'm very dissapointed and most probably I'll going to get an much slower but better supported RasPi or something from Solidrun
If you would follow the progress I was making you would see I got nowhere. I was trying to put support for Udoo and TBS Matrix board into official OpenELEC. Some parts are there but not everything. After the december nothing was accepted anymore (5 months !!!). And also no official response. You can read more at https://github.com/OpenELEC/OpenELEC.tv/pull/3645 and at https://github.com/OpenELEC/OpenELEC.tv/issues/3653. Also on both forums. And at that time everything was agreed how to continue. So stop making my own images is my way of protest. As I explain on TBS forum I know this affects you users but what else can I do. I don't have much in return not even satisfaction of including my work. So I just gave up for now. Sorry for that. If this situation changes you can expect my contribution again.
Dear all, it's sad hearing of your "departure" vpeter. I've never been active in this topic, but your contribution is manifest and I say thank you in behalf of the whole UDOO Team. You have been crucial for the XBMC development for UDOO. Regarding our work, at the moment we are focusing on: 1) Analog audio driver for UDOO Dual/Quad 2) Kernel 3.14 for UDOO Dual/Quad For what we've heard, however, Stephan doesn't work for XBMC anymore, since he stopped answering us too months ago.
I didn't "depart" - I'm just on hold until stuff is included in openelec repository. If will not be included then this means I'm off indefinitly. In the mean time I just focused on some other personal projects. About Stephan: he is still making commits which means still working on openelec.
Hi vpeter Many thanks for the update and your work. My post wasn't aimed at you. It is more a Thing of the whole makers of Udoo who promised us something they didn't make true. In the eraly stages I was in contact with some devs from OpenElec and they said to me they are happy to help when they get some Boards and maybe an Dev who will help them. Afterwards they got paid from solidrun to giv their CuBox i an better support. I had hoped Udoo will do the same.
