Fido release of Yocto

So it's about time we posted a Fido image. For the impatient, here are two image files:

• For Nitrogen6X, BD-SL-i.MX6 (SABRE Lite), and Nitrogen6_Max boards: core-image-sato-dev-nitrogen6x.sdcard.gz
• For Nitrogen6_Lite boards: core-image-sato-dev-nitrogen6x-lite.sdcard.gz

These images are core-image-sato-dev with gstreamer, gpu tools, and gstreamer plugins. Also added in is a simple desktop icon launcher to test video input from cameras or our HDMI input daughterboard. To burn the image file to a sdcard, run this command assuming your sdcard is mounted on /dev/sdc sudo umount /dev/sdc* zcat core-image-sato-dev-nitrogen6x.sdcard.gz | sudo dd of=/dev/sdc bs=1M If you want to build this image on your own you'll need the local.conf and the bblayers.conf and this meta-boundary-example layer and this meta-browser layer that I used in my build. The image file will deploy to ~/bd-yocto/sato-dev/tmp/deploy/images/nitrogen6x/core-image-sato-dev-nitrogen6x.sdcard or nitrogen6x-lite/core-image-sato-dev-nitrogen6x-lite.sdcard depending on your board target. I assume you have bitbake and these packages installed. I assume you've downloaded the files above to ~/Downloads/ The MACHINE name for the nitrogen6x, nitrogen6_max, and sabrelite is MACHINE=nitrogen6x The MACHINE name for the nitrogen6x-lite is MACHINE=nitrogen6x-lite The nitrogen6_vm does not have a machine target for Yocto, contact us if you wish to build for that The SoloX board will have a machine target soon, this post will be updated when that happens Use the appropriate MACHINE name for your platform and edit the local.conf to reflect that. My example will be for the nitrogen6x. Then run these commands to start the build: ~$ mkdir ~/bd-yocto ~$ cd ~/bd-yocto ~/bd-yocto$ repo init -u https://www.github.com/Freescale/fsl-community-bsp-platform -b fido ~/bd-yocto$ repo sync ~/bd-yocto$ tar xf ~/Downloads/meta-boundary-example.tgz -C sources/ ~/bd-yocto$ tar xf ~/Downloads/meta-browser.tgz -C sources/ ~/bd-yocto$ MACHINE=nitrogen6x . setup-environment sato-dev ~/bd-yocto/sato-dev$ cp ~/Downloads/fido-nitrogen6x-local.conf conf/local.conf ~/bd-yocto/sato-dev$ cp ~/Downloads/fido-bblayers.conf conf/bblayers.conf ~/bd-yocto/sato-dev$ bitbake core-image-sato-dev Be warned, this image recipe calls out for building chromium which will take hours and will take ~12GB of RAM at the linking stage of compilation. If you'd like to get rid of chromium, simply remove it from the local.conf file. This image also includes the much easier-to-build firefox browser. For those with the HDMI Input Daugherboard, this image includes a separate device tree for the nitrogen6x that enables the HDMI input daughterboard and disables the cameras. If you'd like to use this image for that purpose, interrupt u-boot as it boots to drop into the u-boot console and run these commands: Hit any key to stop autoboot: 0 U-Boot > setenv dtbname imx6q-nitrogen6x-hdmi-input.dtb U-Boot > saveenv Saving Environment to SPI Flash... SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2 MiB Erasing SPI flash...Writing to SPI flash...done U-Boot > reset Then click on the Video Input Test icon on the desktop when it boots, seen below. This launcher also works for the ov5642 camera when the regular device tree file is used at boot. For those with the ov5640_mipi camera, click on the OV5640 MIPI Test Icon seen below.