As a replacement of System V init, systemd has been supported by Yocto long time ago. Let’s take a look at how to implement a Yocto recipe for systemd services.

The default BSP provided by NXP requires login in UART after booting up, which seems “unfriendly” to some users.

Quick fix for error that sdkmanager throw exception when trying to call sdkmanager –license and sdkmanager –list.

This is a demo page for cool html5 canvas demos. Try to click them!
Beware of performance issues if you trying to access those pages through mobile devices. :)
Fire Ball
Black Hole

This is a short post give a sample of Yocto recipe which fetches source codes from git server.

Using TFTP(Trivial File Transfer Protocol) and NFS(Network File System) to load kernel and rootfs can help to reduce operations of flash write efficiently, which can make you EVK board live longer…

This summary is based on Alexey‘s version, with some modifications according to my experiment.

Yocto has much more strict rules than buildroot, one more QA Issue I met today is when I trying to install some regular files into rootfs by cmake install.

Last week I met an issue when I trying to include a shared lib(built by cmake) written by me into Yocto project, which has already been verified in buildroot.
The root cause is recipe trying to directly install a *.so lib into target filesystem, which doesn’t meet Yocto QA request. Lib should be installed with version number(i.e. libabc.so.0.0.3), then use a soft link(i.e. libabc.so) link to it.

We already started to use cmake instead of writing Makefile by our own in buildroot. Let’s see how to have a cmake package in Yocto.

The normal way that using yocto to do kernel development is really painful… Maybe try out-of-tree build is a better choice.