@cyrilf , yes you need to source the environnement to avoid the error with cmake. Did you configure your mobile device (in qtcreator) to deploy directly on the card ? Like Graugans describe here ? In this way you didn't need to use scp (i never use it, i do all my deploy with qtcreator). I suppose you are using udooquad for your test, can you check that the module galcore is loaded with lsmod in your card ? In my case i never have this issue for the moment (is the card boot on lvds7 or hdmi ?) !
I do not use cmake but qmake. I configured the device in QtCreator but I cannot figure out where does QtCreator deploy the executable... I work with de UDOO Neo and I do have the galcore module loaded. The diplay is a LVDS7 screen. I tried with the Qt WebKit examples and it display the app on the screen. Some of them are buggy but they show. Edit: I'm able to deploy the app by adding those lines to the .pro file: Code: target.path = /home/root/$$TARGET INSTALLS += target appFiles.files = *.qml appFiles.path = /home/root/$$TARGET INSTALLS += appFiles But I'm still at the same point. Nothin appears on the screen.
I was able to run an example from here : https://github.com/meta-qt5/qtwebengine/tree/b5.4/examples/webenginewidgets/fancybrowser It uses Qt WebEngine (so it's supported) so I'll use it as the base for my future developments.
Hi all, i need to build a lib --> openZwave (on the card, in my case udooqdl) libudev.h. I have this error during the build : /home/root/openzwave-1.4.164/cpp/hidapi/linux/hid.c:44:21: fatal error: libudev.h: No such file or directory I have tried to add udev to my local.conf but this not resolve the problem. How i can add it to my build ?
The easiest is to create a new layer and add an own recipe for this library. If you want to build it outside you'll have to add the udev library to the toolchain. I'll send you an example later. Sorry I used the wrong posting for answer Gesendet von meinem FP2 mit Tapatalk
We are bitbaking an udooqdl image. It tries to bring uboot from git://github.com/udooboard/uboot-imx.git;branch=2015.04.imx but this link is broken (we read previous posts about this problem). Does anyone know what is the link to the actual udoo uboot? Thanks
You shouldn't use 2015.imx branch for UDOO Quad. This branch is broken. Use the 2015.10.fslc-qdl branch instead.
I have troubles to run this example on my UDOO Neo (LVDS7). The UI is displayed but the WebEngine cannot load the web page (www.google.com). The MainWindow::finishLoading() function is never called. This is the case for any URL.
I am working on a solution for the u-boot problems. I hope I've sorted this out soon. But at the moment I am a bit short in time.
I'm also working to use the mainline u-boot and mainline kernel with a friend who was able to build a fully working system from those sources using Buildroot. The UDOO u-boot is actually an old instance of u-boot with patches to fit the new one capabilities (like uEnv.txt compatiblity), not a real fork of the mainline u-boot. @graugans: I updated my meta-udoo layer to improve the structure of the recipes for u-boot and the kernel (still using the UDOO repositories): https://gitlab.com/cyrilfr/meta-udoo According to this thread, it seems that the ecspi patch no longer works for the UDOO neo. Or maybe I'm missing something. For the Qt5 app, I moved back from Qt WebEngine to Qt WebKit.
For WPA2 only networks I got this working. Also you can edit Code: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 update_config=1 network={ ssid="TOP-SECRET" scan_ssid=1 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="<Insert your top secret key here>" } If you do not want to place your unencrypted password in this file you can run this command Code: wpa_passphrase TOP-SECRET <Insert your top secret key here> This will echo something like Code: psk=e48c6b7904d4a314cb1f26336ad79468bacb288b477c4cef05190f5ec0e And replace above with. Please notice there are no double quotes Code: network={ ssid="TOP-SECRET" .... psk=e48c6b7904d4a314cb1f26336ad79468bacb288b477c4cef05190f5ec0e }
Hi, everyone Yesterday I pushed an update to my u-boot changes I would like to discuss. I do use the FSL u-boot 2016.07+fsl from meta-fsl-arm + UDOO Patches For Quad/Dual and Neo I rebased the patches from @Francesco ( Francesco Montefoschi ) The rebasing of the A62 Patch set is still work in progress The UDOO team seems to get rid of the FAT32 boot partition @Francesco is this right? So I added support to load the kernel and device tree from the rootfs directly. uEnv.txt still in progress For SD-Card image creation I switched to the newer wic approach. Because the FSL SD-Card image class is designed to use a FAT32 boot partition. I am looking forward to here your thoughts on this.
Hi, That are very good improvements I've read that @Francesco is working on a true official U-Boot 2016 release. Personally I'll wait on that instead of moving to FSL U-Boot as I don't have special issue with the current release (2015.04). As you can see, I updated the kernel patches for SPI and CAN buses to fit the last commits on the UDOO kernel repository.
Nice work Graugans, i will test this week (if i have the time) a build. Could you explain how to use the new tool wic please ?
It is not a real problem. But it is hopefully a bit more stable and less branch changing . And I try to lower recipe count. As a next step Seco A62 will be integrated as well. So one more recipe less Gesendet von meinem FP2 mit Tapatalk
Hey we have our own subsection now Thx to @Andrea Rovai So we can create a new topic on each new question and do not need to maintain a single thread.