Hi Graugans, i have a problem. To not break the sync with meta-udoo recipe i removed from udoo-image-qt5.bb the qt5 modules that i have added. I migrate this modules to local.conf : https://gist.github.com/modjo756/e867b4b3784fcb8d4d3f After this i make : $ repo sync $ MACHINE=udooqdl bitbake -ccleanall udoo-image-qt5 $ MACHINE=udooqdl bitbake udoo-image-qt5 and after some times i have this errors during qtwebengine do_compile: https://gist.github.com/modjo756/eee8286c7c74cbb3a2a6 Exception: Failed to extract compiler version for args: ['target', 'assembler'] Project ERROR: -- running gyp_qtwebengine failed -- i make research on meta qt5 and find this but i'm not sure this is the same problems : https://github.com/meta-qt5/qtwebengine/commit/324eab1b148df1e8330b2dbbd114ab696c163e46 i found this -not yocto but talk about dependencies) : http://gpupowered.org/node/31 Before i migrate the qt5 modules to local.conf my image compile fine ! do you saw on my local.conf some mistakes (i also added gcc g++ binutils ... to my image) ?
@modjo better use packagegroup-core-sdk instead of defining all g++ fiends separate in your local.conf. You can use CORE_IMAGE_EXTRA_INSTALL in your local.conf to append stuff. It is maybe better to only append stuff which is not yet in the image. Can you please try to remove the "tmp/" in your build folder and retry maybe some stuff got mixed up....
Thanks for your tips, can you just say me how i can add this to my local.conf : CORE_IMAGE_EXTRA_INSTALL = " packagegroup-core-sdk" to replace this : gcc g++ binutils libgcc libgcc-dev libstdc++ libstdc++-dev libstdc++-staticdev \ autoconf automake ccache chkconfig glib-networking glibmm \ packagegroup-core-buildessential pkgconfig \ boost cmake zlib glib-2.0 \
@modjo I just remembered your question while I saw the button on the board.... The hardware dev guide states the following in table 2-8: I made some tests when you shut-down the board by executing Code: root@udooqdl:~# halt A short press on the button powers up the board again. I can not confirm, that a long press ~5 causes a force OFF . Further investigation need regarding how to detect a button press in ON state to power down the device. Maybe @Andrea Rovai or @Francesco can give some advice....
Hi Graugans, i have just trying to replace g++ ... by CORE_IMAGE_EXTRA_INSTALL = " packagegroup-core-sdk" to local.conf. It seems to be work ! But i already have the same problem with qtwebengine ! (i'm trying with neo who is on another build in my pc, webengine not build before and same error ) perhaps they have an update to meta qt5 or another that cause this issue !
Okay, looks like there is some driver handling this But it looks like it is not activated in the devicetree for quad/dual...
Thanks for all, i'm making a clean (temp, cache ...) of neo image and relaunch a bitbake to see if it's better !
Thanks for the replay... -> Wifi I test the wifi interface and now all works, wpa-driver nl80211 in /etc/networks/interfaces do the trick! The meta-udoo need to be update with this default. Fore the wpa_supplicant.conf you can use also this command: wpa_passphrase mySSID myPSW > /etc/wpa_supplicant.conf -> test HDMI Udoo Quad on LG22EA53 1920x1080 UDOObuntu_quad_v1.1 .. works UDOObuntu_qdl_v2.0rc1 .. not work Yocto Jethro udoo-image-full-cmdline .. not work -> udoo/core-image- sorry, my mistake
@0Temp I solved my issues by setting resolution to 720p I described the way how I did here May I suggest that you as-well report your issues in the HDMI thread so official UDOO staff knows there are multiple users suffering from this problem. Related to WiFi I prepare a fix for the "/etc/network/interfaces" stuff. for wpa_supplicant maybe connman is an option.
Thx, This is real strange with the machine dependant stuff. I will bring this to the Yocto Mailing list. It looks like there are a lot questions related to Qt5 on the ML at the moment. There will be a small update related to Qt5 for meta-udoo because at the moment Qt5 is a fixed requirement to build I will add some magic so the bbappend will only be needed in case of meta-qt5 is present. Next thing is to propose the backport upstream.
udooneo qt5 full boot but impossible to use ssh !? eth0 is up and i can ping to it (and it to other) but when i try ssh i have this error : modjo@Linux-corei5:~$ ssh root@192.168.1.18 ssh: connect to host 192.168.1.18 port 22: Connection refused the ip is good, i don't know why now it didn't work ...
I will test this when I test the wifi. For the quad I already have a update of /etc/network/interface Gesendet von meinem Nexus 4 mit Tapatalk
Sorry, was bussy with some family triggered projects. I had no time to touch the UDOOs... When connected by serial and execution of ps you should see a dropbear or openssh running. If not please check for dropbear or openssh in /etc/init.d and if you have one of them in the path... Gesendet von meinem Nexus 4 mit Tapatalk
Hi graugans, you don't need to apologize ... Otherwise, i re-write the image on the sd card and now i have ssh ... In other way, tested to program the cortex M4 with arduino (since PC) and this don't work (work's fine with udoobuntu2) do you know the reason and an idea to turn it on ?
