OpenEmbedded/Yocto for UDOO Boards

Good news !

 

I tested NTP client and it works like a charm. You just have to configure a list of time servers in the /etc/ntp.conf file. Otherwise, meta-networking also contains the ntimed package which is a lightweight NTP client.

I see SPI and CAN bus options in the udooneo.conf file but nothin in the udooqdl.conf one. Does your layer support SPI and CAN for UDOO Quad/Dual?

 

Well this is not the best approach but this is the cleanest approach today I guess. I plan to implement a 6LoWPAN network using the Microchip's MRF24J40MA IEEE 802.15.4 transceiver module with the UDOO Quad and I need SPI communication for this. I'll move forward to UDOO Neo but for other hardware considerations I have to use the Quad before.

 

Yes I noticed that disadvantage of patching. Anyway, I'll probably enable both CAN and SPI as CAN could be an alternative for 802.15.4.

 

Hi cyrilf, can you precise here how you have added ntp to yocto please ? I'm also interrested by this please ?
Otherwise, for can and spi i have some patch here for secoA62 (it would be working also for quad).

 

Simply add "ntp" to your IMAGE_INSTALL.

Edit:

I don't have the wlan0 interface on the UDOO Neo, even after configuring the wpa_supplicant.conf file. I have to run manually

Code:

ifup wlan0

to see it.

If I try ifup -a:

Code:

# ifup -a
ifup: interface lo already configured
ifup: interface eth0 already configured

wlan0 is not listed.

Any idea?

 

I found the solution. Just add

Code:

auto wlan0

before

Code:

iface wlan0 inet dhcp

in the meta-udoo/recipes-core/init-ifupdown/init-ifupdown/<machine>/interfaces file.
It enables it for

Code:

ifup -a

command at start up.

 

meta-fsl-demos and other meta-fsl layers (except meta-fsl-arm but for how long?) have been deleted. It seems now that meta-freescale and meta-freescale-distro (optional demo layer) and other meta-freescale-* layers have replaced them. Let see here.

 

I'm looking to add patches for SPI and CAN buses and I wonder how do you write your patches without adding the kernel sources to your repo?

 

use quilt to do that. For example, if you need make a patch for the kernel go to yocto/neoBuild/tmp/work/udooneo-poky-linux-gnueabi/linux-udooboard/3.14-56-r0/git.
open a shell
$quilt new name-of-my-patch.patch
$quilt add "name of the file that you want to pacth"

make your modification directly on the file that you want to change
$bitbake -ccomplile -f linux-udooboard

check if you have that you want ...
when you are satisfy, update your patch with
$quilt refresh

copy your patch in your layer and it to your recipe.

 

Thanks for your advice. I'll try it as soon as possible to add SPI and CAN support for the UDOO Quad.

 

I wrote some patches to enable SPI and CAN for the UDOO Quad. Here the is the SPI patch and here the CAN bus patch.
I didn't try them directly but I looked at the kernel logs to see if everything is fine. Unfortunately, there is errors with the pinmux.

There is no mention of pin 114 and pin 64 on the UDOO Quad pinout.

PS: maybe it could be smarted to write custom .dts files with include to override UDOO kernel .dts like imx6dl-udoo-lvds7.dts do for LCD drivers support for example.

 

I am trying to create a Yocto image with Qt support for the seco-a-62-j duallite.
Thanks to the work of @graugans and @modjo has done and shared with the community I was able to build the image and compile Qt5.6 into it together with the SDK, it boots and the HDMI is working.
I'm wondering how I can get the LVDS output working and if it is already working. I did read @modjo was struggling with it. But couldn't find if it is solved in the mean time.

I also want to know which branch I should use for the meta-qt5 layer. I'm on the jansa/krogoth at the moment