This is a cache of https://www.96boards.org/documentation/consumer/dragonboard/dragonboard410c/build/open-embedded.md.html. It is a snapshot of the page at 2024-11-21T01:23:33.900+0000.
OpenEmbedded and Yocto Guide for Dragonboard410c - 96Boards

OpenEmbedded and Yocto

This page provides the Dragonboard410c specific instructions for flashing OpenEmbedded and Yocto images. For instructions on building the OE/Yocto images, please refer the generic OpenEmbedded guide.

Updating eMMC partitions and Bootloader

Build artifacts from your OE build will be flashed into the on-board eMMC (in contrast to some other boards which run their images from an SDcard). The OpenEmbedded BSP layer assumes that the Linux Bootloaders and eMMC partition layout are used on the board (not the android ones; by default DragonBoards come pre-configured with the android eMMC partition layout). You can download the latest Linux bootloader package for Dragonboard410c from here to your development host, it will be named something like dragonboard410c_bootloader_emmc_linux-<version>.zip.

Whether your board is using the android eMMC partition layout or the Linux partition eMMC layout, you will use the android fastboot utility on your development host for managing the board’s eMMC partitions. If you are using a relatively recent Linux distribution on your development host, it probably already has a package that includes the fastboot utility (it might be named something like android-tools or android-tools-fastboot) so go ahead and install it on your development host.

The procedure for booting Dragonboard410c into fastboot mode is given here. After getting into fastboot mode, update eMMC partition using the downloaded bootloader package by following instructions here

At this point your eMMC has the following partition layout:

  • /dev/mmcblk0p8 , aka boot is used for the boot image (kernel, device tree, initrd)
  • /dev/mmcblk0p10 , aka rootfs is used for the root file system

Flashing build artifacts

At the end of any successful build you will end up with the following artifacts (amongst others)

  • IMAGE-dragonboard-410c.ext4.gz and
  • boot-dragonboard-410c.img

Note: Replace IMAGE with the name of image you built. For example, if you built rpb-console-image then IMAGE will be rpb-console-image

These will be found in your tmp-rpb-glibc/deploy/images/dragonboard-410c directory.

After getting into fastboot mode, following commands can be used to flash built images onto Dragonboard410c’s eMMC.

$ gunzip IMAGE-dragonboard-410c.ext4.gz
$ sudo fastboot flash boot boot-dragonboard-410c.img
$ sudo fastboot flash rootfs IMAGE-dragonboard-410c.ext4