This topic explains how to boot Digi Embedded Yocto images without updating the firmware on the internal eMMC. This is helpful during the development phase, as it preserves the original firmware on the SOM.

Open a serial connection

You must open a serial connection to communicate with your device.

  1. Open a serial connection using any terminal program such as Tera Term, Minicom, Coolterm, or HyperTerminal. This documentation demonstrates using Minicom to work with the device command line.

    Use the following settings:

    Parameter Value

    Port

    Serial port where the device is connected

    Baud rate

    115200

    Data bits

    8

    Parity

    None

    Stop bits

    1

    Flow control

    None

  2. Reset the device by pressing the reset button on the board. Then immediately press any key in the serial terminal to stop the auto-boot process. The U-Boot bootloader prompt displays:

    NOTICE:  CPU: STM32MP257F?? Rev.B
NOTICE:  Model: Digi International ConnectCore MP25 Development Kit
NOTICE:  BL2: v2.8-stm32mp2-beta-r1.0(release):65cda4fe7(65cda4fe)
NOTICE:  BL2: Built : 08:14:45, Jul 12 2024
NOTICE:  BL2: Booting BL31
NOTICE:  BL31: v2.8-stm32mp2-beta-r1.0(release):65cda4fe7(65cda4fe)
NOTICE:  BL31: Built : 08:14:50, Jul 12 2024

U-Boot 2022.10-stm32mp25-beta-r1-gc5d85ac8567-dirty (Jul 12 2024 - 11:27:03 +0200)
CPU: STM32MP257F?? Rev.B
Model: Digi International ConnectCore MP25 Development Kit
ConnectCore MP25 SOM variant 0x01: 0 Bytes DDR4, Wi-Fi, Bluetooth
  Board version 1
Boot:  MMC
DRAM:  1 GiB
optee optee: OP-TEE: revision 3.19 (e66a2a51)
Core:  374 devices, 31 uclasses, devicetree: board
WDT:   Started watchdog with servicing (32s timeout)
MMC:   STM32 SD/MMC: 0, STM32 SD/MMC: 2
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: eth2@482d0000
Normal Boot
Hit any key to stop autoboot:  0
=>

Boot the system from network

This shows how to transfer the images to the target via TFTP or NFS, and mount an NFS root file system.

This requires that you set up your PC workstation as explained in Set up native Linux PC.

1. Prepare the device artifacts

  1. Get the Digi Embedded Yocto firmware images to boot from network:

    • The kernel file: Image.gz.

    • The device tree: ccmp25-dvk.dtb.

    • Any device tree overlays files that apply to your hardware: <device-tree-overlay-file>.dtbo (see Pre-compiled device tree overlays).

    • The compressed root file system: <rootfs-file>.rootfs.tar.bz2.

    1. After building the Digi Embedded Yocto firmware, you can find the image files inside the project directory at:

      <project_folder>/tmp/deploy/images/ccmp25-dvk

    2. You can download Digi provided pre-built images from:

  2. Untar the root file system tarball (*.rootfs.tar.bz2) in the NFS exported directory of your development workstation. See Set up native Linux PC.

    $ sudo tar xvfp image.rootfs.tar.bz2 -C /exports/nfsroot-ccmp25_dvk

  3. Copy the kernel *.bin file to the TFTP exported directory of your development workstation.

    $ sudo cp <kernel-file>.bin /tftpboot

  4. Copy the device tree *.dtb file to the TFTP exported directory of your development workstation.

    $ sudo cp <device-tree-file>.dtb /tftpboot

  5. (Optional) Copy any device tree overlay *.dtbo files that apply to your variant to the TFTP exported directory of your development workstation.

    $ sudo cp <device-tree-overlay-file>.dtbo /tftpboot

2. Configure your device’s network settings

  1. Get a dynamic IP for your target:

    => setenv autoload no
=> dhcp

    or you can set a static IP:

    => setenv ipaddr 192.168.115.222

  2. Configure the IP of the development workstation with TFTP and NFS servers installed. See Set up native Linux PC:

    => setenv serverip 192.168.115.1

3. Boot from network

Boot from TFTP+NFS

  1. Set the directory with the rootfs to mount. This directory is the one exported via NFS in your development workstation. See Set up an NFS server.

    => setenv rootpath /exports/nfsroot-ccmp25_dvk

  2. Specify the device tree (*.dtb) file name. This is the name of the *.dtb file you copied to the TFTP exported directory of your development workstation.

    => setenv fdt_file <device-tree-file>.dtb

  3. (Optional) Use a comma-separated list to specify the device tree overlay (*.dtbo) files you want to apply. These are the names of the *.dtbo files you copied to the TFTP exported directory of your development workstation.

    => setenv overlays <overlay1>.dtbo,<overlay2>.dtbo

  4. Establish the kernel file (*.bin) name. This is the name of the *.bin file you copied to the TFTP exported directory of your development workstation.

    => setenv imagegz <kernel-file>.bin

  5. Save the changes.

    => saveenv

  6. Boot from TFTP.

    => dboot linux tftp

    You can make these changes persistent by writing the following command:

    => setenv bootcmd 'dboot linux tftp'
=> saveenv

The target now loads the kernel and device tree from the TFTP server and the root file system from the NFS server.

Boot entirely from NFS

To avoid using TFTP for kernel and device tree files and boot everything from NFS, copy the kernel *.bin and device tree *.dtb files to the NFS-exported directory of your development workstation (instead of to the TFTP directory). See Set up an NFS server.

=> dboot linux nfs

Boot from microSD card

U-Boot can start a complete Digi Embedded Yocto system from a microSD card. To boot a system from a microSD card, follow these steps:

1. Create a bootable microSD card from a Digi Embedded Yocto image

Refer to Boot from microSD card for instructions on creating a bootable microSD card.

2. Boot Digi Embedded Yocto from the microSD card

  1. Power off the device.

  2. Insert the microSD card into the microSD card holder (bottom side of the board).

  3. Change the boot source configuration to boot from the microSD card. To do so, set the boot mode micro-switches as follows:

    • BOOT.1: ON

    • BOOT.2: ON

    • BOOT.3: OFF

    • BOOT.4: OFF

  4. Power on the device. Digi Embedded Yocto boots from the microSD card.