You must first set up your PC workstation to use Digi Embedded Yocto. Follow the instructions at Set up your development workstation.
1. Open a serial connection
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:
Serial port where the device is connected
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:
U-Boot dub-2017.03-r2.1-git+g3e65181 (Nov 05 2018 - 03:53:30 +0000) CPU: Freescale i.MX6QP rev1.0 996 MHz (running at 792 MHz) CPU: Automotive temperature grade (-40C to 125C) at 44C Reset cause: POR I2C: ready DRAM: 2 GiB MMC: FSL_SDHC: 0 (eMMC), FSL_SDHC: 1 In: serial Out: serial Err: serial Model: Digi International ConnectCore 6 QuadPlus Single Board Computer. ConnectCore 6 Plus SOM variant 0x01: Industrial QuadPlus-core 1GHz, 8GB eMMC, 2GB DDR3, -40/+85C, Wireless, Bluetooth, Kinetis Board: ConnectCore 6 Plus SBC, version 3, ID 160 Boot device: MMC4 PMIC: DA9063, Device: 0x61, Variant: 0x60, Customer: 0x00, Config: 0x56 Net: FEC [PRIME] Hit any key to stop autoboot: 0 =>
2. Prepare the device artifacts
Get the Yocto firmware images to boot from network:
After building the Yocto firmware, you can find the image files inside the project directory at:
You can download Digi provided pre-built images from:
For ConnectCore 6 Plus SBC:
Untar the root filesystem tarball (*.rootfs.tar.bz2) in the NFS exported directory of your development workstation. See Set up your development workstation.
~> sudo tar xvfp image.rootfs.tar.bz2 -C /exports/nfsroot-ccimx6qpsbc
Copy the kernel *.bin file to the TFTP exported directory of your development workstation.
~> sudo cp image.bin /tftpboot
Copy the device tree *.dtb file to the TFTP exported directory of your development workstation.
~> sudo cp image.dtb /tftpboot
Read the board_id and soc_family of your platform from U-Boot to find out the appropriate device tree file for your platform. For example:
=> printenv board_id board_id=129 => printenv soc_family soc_family=imx6q =>
The dtb file name of your device device tree for your platform follows the format: zImage—4.9-r0.2-<soc_family>-<platform>-id<board_id>-<date>.dtb
3. Configure your device’s network settings
Get a dynamic IP for your target:
=> setenv autoload no => dhcp
or you can set a static IP:
=> setenv ipaddr 192.168.115.222
Configure the IP of the development workstation with TFTP and NFS servers installed. See Set up your development workstation:
=> setenv serverip 192.168.115.1
4. Boot from network
Boot from TFTP+NFS
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-ccimx6qpsbc
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 image.dtb
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 zimage image.bin
Save the changes.
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 filesystem 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