Skip to end of metadata
Go to start of metadata

Building NXP/Embedian’s Yocto Kirkstone BSP Distribution

Eric Lee

version 1.0a, 08/08/2023



This document describes how Embedian builds a customized version of NXP’s i.MX7 official Yocto Kirkstone BSP release for Embedian's SMARC-FiMX7 product platform. The approach is to pull from Embedian's public facing GIT repository and build that using bitbake. The reason why we use this approach is that it allows co-development. The build output is comprised of binary images, feed packages, and an SDK for SMARC-FiMX7 specific development.


NXP makes their i.MX series official bsp build scripts available via the following GIT repository:


Freescale community BSP release build script is available via the following repository: 


It is this repository that actually pulls in the meta-imx/meta-bsp project to perform the Linux BSP builds for NXP's i.MX7 ARM Cortext-A7 chips.  

Generating SSH Keys

 We recommend you use SSH keys to establish a secure connection between your computer and Embedian Gitlab server. The steps below will walk you through generating an SSH key and then adding the public key to our Gitlab account. 

Step 1. Check for SSH keys

First, we need to check for existing ssh keys on your computer. Open up Git Bash and run:

Check the directory listing to see if you have a file named either or If you don't have either of those files go to step 2. Otherwise, you already have an existing keypair, and you can skip to step 3.

Step 2. Generate a new SSH key

To generate a new SSH key, enter the code below. We want the default settings so when asked to enter a file in which to save the key, just press enter.

Step 3. Add your SSH key to Embedian Gitlab Server

Copy the key to your clipboard.

Go to Embedian Git Server. At Profile Setting --> SSH Keys --> Add SSH Key 

Paste your public key and press "Add Key" and your are done.

Overview of the meta-embedian Yocto Layer

The supplied meta-embedian Yocto compliant layer has the following organization:

|-- conf
|   |-- layer.conf
|   |-- machine
|       |-- include
|       |   |--
|       |-- pitximx8mp2g.conf
|       |-- pitximx8mp4g.conf
|       |-- pitximx8mp6g.conf
|       |-- smarcimx8qm8g.conf
|       |-- smarcimx8qm4g.conf
|       |-- smarcimx8mp6g.conf
|       |-- smarcimx8mp4g.conf
|       |-- smarcimx8mp2g.conf
|       |-- smarcimx8mq4g.conf
|       |-- smarcimx8mq2g.conf
|       |-- smarcimx8mm4g.conf
|       |-- smarcimx8mm2g.conf
|       |-- smarcfimx7d2g.conf
|       |-- smarcfimx7d.conf
|       |-- smarcfimx7s.conf
|       |-- smarcfimx6qp2g.conf
|       |-- smarcfimx6qp1g.conf
|       |-- smarcfimx6q2g.conf
|       |-- smarcfimx6q1g.conf
|       |-- smarcfimx6dl1g.conf
|   |   `-- smarcfimx6solo.conf
|-- recipes-bsp
|   |-- u-boot
|       `--
|   |-- imx-atf
|       `-- imx-atf_2.6.bbappend
|       |   |-- imx-atf
|       |   |   `-- imx8mm-atf-uart4.patch
|   |-- imx-sc-firmware
|       `-- imx-sc-firmware_%.bbappend
|       |   |-- imx-sc-firmware
|       |   |   |-- mx8qm-smarc-8g-scfw-tcm.bin
|       |   |   `-- mx8qm-smarc-4g-scfw-tcm.bin

|   |-- alsa-state
|       |   |-- alsa-state
|       |   |   `-- asound.state
|       `-- alsa-state.bbappend
|   |-- pm-utils
|       `-- pm-utils_%.bbappend
|   |-- imx-mkimage
|       `-- imx-boot_1.0.bbappend

|-- recipes-core
|   |-- busybox
|       `-- busybox_%.bbappend
|       |   |-- busybox
|       |   |   |-- ftpget.cfg
|       |   |   `-- defconfig
|   |-- base-files
|       `-- base-files_%.bbappend
|       |   |-- base-files
|       |   |   |-- issue
|       |   |   `--
|   |-- systemd
|       `-- systemd-serialgetty.bbappend
|       |   |-- systemd-serialgetty
|       |   |   |-- disable-serialgetty.service
|       |   |   `--
|   |-- packagegroups
|       `-- packagegroup-core-tools-testapps.bbappend
|   |-- psplash
|       `-- psplash_git.bbappend
|       |   |-- files
|       |   |   |-- 0001-psplash-Change-colors-for-the-Embedian-Yocto-logo.patch
|       |   |   |-- psplash-poky.png
|       |   |   `-- psplash-bar.png
|   |-- udev
|       |   |-- files
|       |   |   |   `-- usb-power.rules  
|       `-- udev-rules-imx.bbappend

|-- recipes-kernel
|   |-- linux
|       `--
`-- scripts
|   `-- emb_mk_yocto_sdcard

Notes on 
meta-embedian layer content


This folder contains the machine definitions for all Embedian's platform and backup repository in Embedian. These select the associated kernel, kernel config, u-boot, u-boot config, and tar.bz2 image settings.


This folder contains recipes used to build DAS U-boot for all Embedian's platform.


This folder contains recipes used to change console port for Embedian's i.MX8MM platform.


This folder contains system control firmware binary for Embedian's i.MX8QM platform.


This folder contains sgtl5000 sound chip default state for all Embedian's platform.


This folder contains imx-mkimage tool for Embedian's i.MX8MQ, i.MX8MM, i.MX8QM, i.MX8MP platform.


This folder remove telnetd from bysybox for all Embedian's platform.  


This folder customized Yocto boot psplash for all Embedian's platform.


Contains the recipes needed to build for all Embedian's platform Linux kernels.

Setting Up the Tools and Build Environment

To build the latest NXP i.MX7 meta-bsp, you first need an Ubuntu 20.04 or 22.04 LTS installation. Since bitbake does not accept building images using root privileges, please do not login as a root user when performing the instructions in this section. 

Once you have Ubuntu 20.04 or 22.04 LTS running, install the additional required support packages using the following console command:

$ sudo apt-get install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev python3-subunit pylint mesa-common-dev zstd liblz4-tool file locales xterm rsync curl lz4 libssl-dev pv device-tree-compiler libghc-gnutls-dev

$ sudo locale-gen en_US.UTF-8


To get the BSP you need to have 'repo' installed and use it as:

Install the 'repo' utility:

$ mkdir ~/bin
$ curl > ~/bin/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ PATH=${PATH}:~/bin 

Download the BSP Yocto Project Environment.

$ mkdir ~/kirkstone-release

$ cd ~/kirkstone-release

$ repo init -u -b imx-linux-kirkstone -m imx-5.15.71-2.2.0.xml

$ repo sync

Download the Embedian Yocto build script and meta layer.


$ wget

$ chmod 444

$ cd sources

$ git clone meta-embedian -b kirtstone-5.15.71_2.2.0

$ cd ~/kirkstone-release

$ DISTRO=fsl-imx-fb MACHINE=smarcfimx7d source -b build-fb 

Choose "y" to accept EULA.
This script will create and bring you to ~/kirkstone-release/build-fb directory.




The last line of the above script

$ DISTRO=<distro name> MACHINE=<machine name> source -b <build dir>

  1. <distro name> 
    • fsl-imx-x11 - Only X11 graphics
    • fsl-imx-wayland - Wayland weston graphics

    • fsl-imx-xwayland - Wayland graphics and X11. X11 applications using EGL are not supported

    • fsl-imx-fb - Frame Buffer graphics - no X11 or Wayland

  2. <machine name>

    • smarcfimx7s - if your board is solo core i.MX7 and 512MB DDR3L.

    • smarcfimx7d - if your board is dual core i.MX7 and 1GB DDR3L.

    • smarcfimx7d2g - if your board is dual core i.MX7 and 2GB DDR3L.

The default console debug port is SER3.

In this document, we will use smarcfimx7d as the example of machine name. Users need to change different machine name if you have different SMARC card variants.

Building the target platforms

 To build Embedian/Freescale Yocto BSP, use the following commands:

$ MACHINE=smarcfimx7d bitbake -k fsl-image-qt6-validation-imx
$ MACHINE=smarcfimx7d bitbake -k fsl-image-validation-imx



fsl-image-validation-imx provides a gui image without QT6. 

fsl-image-qt6-validation-imx provides a Qt6 image for X11, wayland or FB backends depending on your distro name.

If your machine name is smarcfimx7s and your gui image is without QT6 , the following command gives you as an example.

$ MACHINE=smarcfimx7s bitbake -k fsl-image-validation-imx

The first build takes time.


Once it done, you can find all required images under ~/kirkstone-release/<build directory>/tmp/deploy/images/<machine name>/

You may want to build programs that aren’t installed into a root file system so you can make them available via a feed site (described below.) To do this you can build the package directly and then build the package named package-index to add the new package to the feed site.


The following example builds the tcpdump program and makes it available on the feed site:

$ MACHINE=smarcfimx7d bitbake tcpdump
$ MACHINE=smarcfimx7d bitbake package-index

Once the build(s) are completed you’ll find the resulting images, rpm and licenses in folder ~/kirkstone-release/<build directory>/tmp/deploy.

deploy/images/<machine name>/* 

This folder contains the binary images for the root file system and the Embedian SMARC-FiMX7 specific version of the boot file, Image and device tree file. Specifically the images are:

deploy/images/<machine name>/u-boot.imx

This is bootloader file binary for SMARC-FiMX7

deploy/images/<machine name>/zImage

The kernel Image for SMARC-FiMX7.  

deploy/images/<machine name>/<device tee file>

Selecting display configuration is a matter of selecting an appropriate DTB file under deploy/images/<machine name>/<device tee file>

All available DTB files are listed in the table below.

DTB NameDescription
imx7s-smarc.dtbDevice tree blob for i.mx7 solo core configuration.
imx7d-smarc-wvga.dtbDevice tree blob for i.mx7 dual core configuration.

deploy/images/<machine name>/fsl-image-validation-imx-<machine name>.*

Embedian root file system images for software development on Embedian’s SMARC-FiMX7 platforms without QT6.

deploy/images/<machine name>/fsl-image-qt6-validation-imx-<machine name>.*

Embedian root file system images for software development on Embedian’s SMARC-FiMX7  with QT6.


 This folder contains all the packages used to construct the root file system images. They are in deb format (similar format to Debian packages) and can be dynamically installed on the target platform via a properly  constructed feed file. Here is an example of the feed file (named base- feeds.conf) that is used internally at Embedian to install upgrades onto a SMARC-FiMX7 platform without reflashing the file system:

src/gz all http://<ip address>/all

src/gz cortexa7t2hf-neon http://<ip address>/cortexa7t2hf-neon

src/gz cortexa7t2hf-neon-mx7d http://<ip addresss>/cortexa7t2hf-neon-mx7d

src/gz smarcfimx7d http://<ip addresss>/smarcfimx7d

A database of all licenses used in all packages built for the system.

Setup SD Card Manually

For these instruction, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.

$ export DISK=/dev/mmcblk0

Erase SD card:

$ sudo dd if=/dev/zero of=${DISK} bs=1M count=160

Create Partition Layout: Leave 1MB offset for boot file.

With util-linux v2.26, sfdisk was rewritten and is now based on libfdisk.


$ sudo sfdisk --version
sfdisk from util-linux 2.34

Create Partitions:

sfdisk >=2.26.x

$ sudo sfdisk ${DISK} <<-__EOF__

Format Partitions:

for: DISK=/dev/mmcblk0
$ sudo mkfs.vfat -F 16 ${DISK}p1 -n boot
$ sudo mkfs.ext4 ${DISK}p2 -L rootfs
for: DISK=/dev/sdX
$ sudo mkfs.vfat -F 16 ${DISK}1 -n boot
$ sudo mkfs.ext4 ${DISK}2 -L rootfs

Mount Partitions:

On some systems, these partitions may be auto-mounted...

$ sudo mkdir -p /media/boot/
$ sudo mkdir -p /media/rootfs/
for: DISK=/dev/mmcblk0
$ sudo mount ${DISK}p1 /media/boot/
$ sudo mount ${DISK}p2 /media/rootfs/
for: DISK=/dev/sdX
$ sudo mount ${DISK}1 /media/boot/
$ sudo mount ${DISK}2 /media/rootfs/

Install Bootloader

If SPI NOR Flash is not empty

The u-boot.imx is pre-installed in SPI NOR flash at factory default. SMARC-FiMX7 is designed to always boot up from SPI NOR flash and to load zImage, device tree blob and root file systems based on the setting of BOOT_SEL. If users need to fuse their own u-boot or perform u-boot upgrade. This section will instruct you how to do that.

Copy u-boot.imx to the first boot partition of your SD card. 

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>/

$ sudo cp -v u-boot.imx /media/boot/u-boot.imx
Fuse u-boot.imx to the SPI NOR flash.

Stop at U-Boot command prompt (Press any key when booting up). Copy and Paste the following script under u-boot command prompt. 

u-boot command prompt

U-Boot# mmc rescan; mmc dev; load mmc 0:1 0x90800000 u-boot.imx; sf probe; sleep 2; sf erase 0 0xc0000; sf write 0x90800000 0x400 c0000

If SPI NOR Flash is empty

In some cases, when SPI NOR flash is erased or the u-boot is under development, we need a way to boot from SD card first. Users need to shunt cross the TEST# pin to ground. In this way, SMARC-FiMX7 will always boot up from SD card.

Copy u-boot.imx to the SD card 

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>/

$ sudo dd if=u-boot.imx of=${DISK} bs=512 seek=2 
  1. If your u-boot hasn't been finalized and still under development, it is recommended to shunt cross the test pin and boot directly from SD card first. Once your u-boot is fully tested and finalized, you can fuse your u-boot to SPI NOR flash.
  2. When TEST# pin of SMARC-FiMX7 is not shunt crossed, it will always boot up from SPI NOR flash. U-boot will read the BOOT_SEL configuration and determine where it should load zImage and device tree blob. When TEST# is shunt crossed (pull low), it will always boot up from SD card.

uEnv.txt based bootscript

Create "uEnv.txt" boot script: ($ vim uEnv.txt)


mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext4 rootwait fixrtc
mmcargs=setenv bootargs console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} ${optargs}
uenvcmd=run loadzimage; run loadfdt; run mmcboot

Copy uEnv.txt to the boot partition:


$ sudo cp -v ~/uEnv.txt /media/boot/

Install Kernel zImage

Copy Image to the boot partition:

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>/

$ sudo cp -v zImage /media/boot

Install Kernel Device Tree Binary

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>/

$ sudo mkdir -p /media/boot/dtbs

$ sudo cp -v imx7d-smarc.dtb /media/boot/dtbs/imx7d-smarc.dtb
$ sudo cp -v imx7s-smarc.dtb /media/boot/dtbs/imx7s-smarc.dtb

All available DTB files are listed in the table below.

DTB NameDescription
imx7s-smarc.dtbDevice tree blob for i.mx7 solo core configuration.
imx7d-smarc-wvga.dtbDevice tree blob for i.mx7 dual core configuration.


Install Root File System

Copy Root File System:

Yocto Built Rootfs:

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>/

$ sudo tar jxvf <filename.tar.bz2> -C /media/rootfs


  1. SMARC-FiMX7 always boots up to SPI flash first. The firmware in SPI flash is factory pre-installed from Embedian. It will read the BOOT_SEL configuration that defined by SMARC specification on your carrier board and load u-boot.bin from the partition one of the device (could be SD card, eMMC, GBE,..etc) that you selected to memory.
  2. MAC address is factory pre-installed at on board I2C EEPROM at offset 60 bytes. It starts with Embedian's vendor code 10:0D:32. u-boot will read it and pass this parameter to kernel.
  3. The kernel modules is included in the Yocto rootfs.

Remove SD card:

$ sync
$ sudo umount /media/boot
$ sudo umount /media/rootfs

Setup SD Card Automatically

This section tells you how to set up an SD card automatically. It mainly uses a script to do all the steps in the above section.

$ cd ~/kirkstone-release

$ sudo MACHINE=smarcfimx7d sources/meta-embedian/scripts/emb_mk_yocto_sdcard/ /dev/sdX


The default output display is HDMI. If you need to use other device tree output, change "DISPLAY" parameters in the script.

Shunt cross TEST# pin to ground and set the BOOT_SEL to ON OFF OFF. The module will boot up from SD card.  

Feed Packages 

You need to setup Apache2 web server on your development host machine first.

The Apache server default web page directory is /var/www/html .We need to populate it with a link pointing to our deb package repository.


sudo ln -s /path/to/build-yocto/tmp/deploy/deb /var/www/html/deb

The following procedure can be used on a Embedian SMARC-FiMX7 device to download and utilize the feed file show above to install the tcpdump terminal emulation program:

# vim /etc/apt/sources.list.d/yocto.list

Only keep the following four lines:

deb https://<ip address>/all ./

deb http://<ip address>/cortexa7t2hf-neon ./

deb http://<ip address>/cortexa7t2hf-neon-mx7d ./

deb http://<ip address>/smarcfimx7d ./


# apt-get update

# apt-get upgrade

# apt-get install tcpdump


Writing Bitbake Recipes

In order to package your application and include it in the root filesystem image, you must write a BitBake recipe for it.

When starting from scratch, it is easiest to learn by example from existing recipes. 

Example HelloWorld recipe using autotools

For software that uses autotools (./configure; make; make install), writing recipes can be very simple:


DESCRIPTION = "Hello World Recipe using autotools"
SECTION = "console/utils"
PRIORITY = "optional"
PR = "r0"
S = "${WORKDIR}/git"
inherit autotools


SRC_URI specifies the location to download the source from. It can take the form of any standard URL using http://, ftp://, etc. It can also fetch from SCM systems, such as git in the example above.

PR is the package revision variable. Any time a recipe is updated that should require the package to be rebuilt, this variable should be incremented.

inherit autotools brings in support for the package to be built using autotools, and thus no other instructions on how to compile and install the software are needed unless something needs to be customized.

S is the source directory variable. This specifies where the source code will exist after it is fetched from SRC_URI and unpacked. The default value is ${WORKDIR}/${PN}-${PV}, where PN is the package name and PV is the package version. Both PN and PV are set by default using the filename of the recipe, where the filename has the format

Example HelloWorld recipe using a single source file

This example shows a simple case of building a helloworld.c file directly using the default compiler (gcc). Since it isn’t using autotools or make, we have to tell BitBake how to build it explicitly.


DESCRIPTION = "HelloWorld"
SECTION = "examples"
SRC_URI = "file://helloworld.c"
S = "${WORKDIR}"
do_compile() {
    ${CC} ${CFLAGS} ${LDFLAGS} helloworld.c -o helloworld
do_install() {
    install -d ${D}${bindir}
    install -m 0755 helloworld ${D}${bindir}


In this case, SRC_URI specifies a file that must exist locally with the recipe. Since there is no code to download and unpack, we set S to WORKDIR since that is where helloworld.c will be copied to before it is built.

WORKDIR is located at ${OETREE}/<build directory>/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/<package name and version> for most packages. If the package is machine-specific (rather than generic for the cortexa7t2hf architecture), it may be located in the smarcfimx7t2hf-poky-linux-gnueabi subdirectory depending on your hardware (this applies to kernel packages, images, etc).

do_compile defines how to compile the source. In this case, we just call gcc directly. If it isn’t defined, do_compile runs make in the source directory by default.

do_install defines how to install the application. This example runs install to create a bin directory where the application will be copied to and then copies the application there with permissions set to 755.

D is the destination directory where the application is installed to before it is packaged.

${bindir} is the directory where most binary applications are installed, typically /usr/bin.

For a more in-depth explanation of BitBake recipes, syntax, and variables, see the Recipe Chapter of the OpenEmbedded User Manual.

Setup eMMC Manually

Setting up eMMC usually is the last step at development stage after the development work is done at your SD card or NFS environments. From software point of view, eMMC is nothing but a non-removable SD card on board. For SMARC-FiMX7, the SD card is always emulated as /dev/mmcblk0 and on-module eMMC is always emulated as /dev/mmcblk2. Setting up eMMC now is nothing but changing the device descriptor. 

This section gives a step-by-step procedure to setup eMMC flash. Users can write a shell script your own at production to simplify the steps.

First, we need to backup the final firmware from your SD card or NFS.

Prepare for eMMC binaries from SD card (or NFS):

Insert SD card into your Linux PC. For these instructions, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.

For these instruction, we are assuming: DISK=/dev/mmcblk0, "lsblk" is very useful for determining the device id.

$ export DISK=/dev/mmcblk0

Mount Partitions:

On some systems, these partitions may be auto-mounted...

$ sudo mkdir -p /media/boot/
$ sudo mkdir -p /media/rootfs/
for: DISK=/dev/mmcblk0
$ sudo mount ${DISK}p1 /media/boot/
$ sudo mount ${DISK}p2 /media/rootfs/
for: DISK=/dev/sdX
$ sudo mount ${DISK}1 /media/boot/
$ sudo mount ${DISK}2 /media/rootfs/


Copy Image to rootfs partition:

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>

$ sudo cp -v zImage /media/rootfs/home/root

Copy uEnv.txt to rootfs partition:

Copy and paste the following contents to /media/rootfs/home/root ($ sudo vim /media/rootfs/home/root/uEnv.txt)

mmcroot=/dev/mmcblk2p2 ro
mmcrootfstype=ext4 rootwait fixrtc
mmcargs=setenv bootargs console=${console} root=${mmcroot} rootfstype=${mmcrootfstype} ${optargs}
uenvcmd=run loadzimage; run loadfdt; run mmcboot

Copy device tree blob to rootfs partition:

~/kirkstone-release/<build dir>/tmp/deploy/images/<machine name>

$ sudo cp -v imx7s-smarc.dtb /media/rootfs/home/root/imx7s-smarc.dtb

$ sudo cp -v imx7d-smarc.dtb /media/rootfs/home/root/imx7d-smarc.dtb 

Copy real rootfs to rootfs partition:

$ pushd /media/rootfs
$ sudo tar cvfz ~/smarcfimx7-emmc-rootfs.tar.gz .
$ sudo mv ~/smarcfimx7-emmc-rootfs.tar.gz /media/rootfs/home/root
$ popd

Remove SD card:

$ sync
$ sudo umount /media/boot
$ sudo umount /media/rootfs

Copy Binaries to eMMC from SD card:

Insert this SD card into your SMARC-FiMX7 device.

Now it will be almost the same as you did when setup your SD card, but the eMMC device descriptor is /dev/mmcblk2 now. Booting up the device.

$ export DISK=/dev/mmcblk2

Erase eMMC:

$ sudo dd if=/dev/zero of=${DISK} bs=1M count=160

Create Partition Layout:

$ sudo sfdisk ${DISK} <<-__EOF__

Format Partitions:

$ sudo mkfs.vfat -F 16 ${DISK}p1 -n boot
$ sudo mkfs.ext4 ${DISK}p2 -L rootfs

Mount Partitions:

$ sudo mkdir -p /media/boot/
$ sudo mkdir -p /media/rootfs/
$ sudo mount ${DISK}p1 /media/boot/
$ sudo mount ${DISK}p2 /media/rootfs/

Install binaries for partition 1

Copy uEnv.txt/zImage/*.dtb to the boot partition

$ sudo cp -v zImage uEnv.txt /media/boot/

Install Kernel Device Tree Binary

$ sudo mkdir -p /media/boot/dtbs
$ sudo cp -v imx7d-smarc.dtb /media/boot/dtbs/

Install Root File System

$ sudo tar -zxvf smarcfimx7-emmc-rootfs.tar.gz -C /media/rootfs


Unmount eMMC:

$ sync
$ sudo umount /media/boot
$ sudo umount /media/rootfs


Switch your Boot Select to eMMC and you will be able to boot up from eMMC now.

Setup eMMC Automatically 

Boot up the module from SD card and run the following script. The Yocto images will be written into on-module eMMC.

$ /dev/mmcblk2 >/dev/null 2>&1

 Shutdown the device. Set TEST# pin floating and set the BOOT_SEL to OFF ON ON. The module will boot up from on-module eMMC. 

version 1.0a, 08/08/2023

Last updated 2023-08-23

  • No labels