Ezurio provides a Yocto layer that includes support for the Sona TI radio. Platforms that use the Yocto build system can use this layer to do much of the integration automatically. This section gives a brief overview of the steps needed to include and use this layer. Please see the README file in the meta-summit-radio layer for more specific details.

The Ezurio Yocto layer is available on gitHub. Clone or copy this into your project sources directory.

Note: The default Github branch contains only a README file listing the branches that should be used for each radio release version. Be sure to use the branch corresponding to the radio release.

cd /my_project/sources/
git clone https://github.com/LairdCP/meta-summit-radio
git checkout <lrd-a.b.0.x>

The meta-summit-radio layer must be referenced in the conf/bblayers.conf file to be recognized by the build system. Due to a breaking syntax change in bitbake introduced in Yocto 3.4, the meta-summit-radio layer has two implementations. Add the appropriate line to your conf/bblayers.conf file depending on your version of Yocto:

BBLAYERS += "${BSPDIR}/sources/meta-summit-radio/meta-summit-radio"
OR
BBLAYERS += "${BSPDIR}/sources/meta-summit-radio/meta-summit-radio-pre-3.4"

Set the preferred provider for the wpa_supplicant to the Summit supplicant by appending the following lines to the build’s conf/local.conf file:

PREFERRED_PROVIDER_wpa-supplicant = "summit-supplicant-ti"
PREFERRED_PROVIDER_wpa-supplicant-cli = "summit-supplicant-ti-cli"
PREFERRED_PROVIDER_wpa-supplicant-passphrase = "summit-supplicant-ti-passphrase"

The Ezurio Yocto layer includes support for other Ezurio radio packages as well. Some of these are providers for the wireless-regdb-static package. However, the Sona TI351 should use the upstream wireless regulatory database. The PREFERRED_PROVIDER for wireless-regdb-static should be set to the upstream component when using Sona TI351 radio.

PREFERRED_PROVIDER_wireless-regdb-static = "wireless-regdb"

Add the backports, firmware, supplicant and any other desired packages to your Yocto image recipe.

IMAGE_INSTALL:append = " kernel-module-ti-backports"
IMAGE_INSTALL:append = " summit-supplicant-ti"
IMAGE_INSTALL:append = " ti351-firmware"

Warning: Do not use the IMAGE_INSTALL += “xxx” syntax in your conf/local.conf file to add components to your image. If you use the conf/local.conf file instead of modifying an image recipe, use the append syntax above (or the older syntax for Yocto versions prior to 3.4). Use of ‘IMAGE_INSTALL +=’ syntax in conf/local.conf can cause subtle issues in the final image that can be very difficult to debug.

Configure your kernel to ensure compatibility with the backports package, specifically ensuring that the wireless and Bluetooth subsystems are not built-in to the kernel. See the Backports section for details:

bitbake -c menuconfig virtual/kernel

Now you can bake your final image:

bitbake <image name>