The ConnectCore MP13 is shipped without a default operating system loaded. Only the ARM Trusted Firmware, OPTEE, and U-Boot are flashed in the device. This step demonstrates how to install Digi Embedded Yocto in your ConnectCore MP13.
1. Establish a serial connection with your device
Open a serial connection with the device. You can use any serial terminal program such as Tera Term, Minicom, CoolTerm, or HyperTerminal.
PuTTY terminal program is not recommended due to an incompatibility with the USB/serial driver. |
Open a serial connection with 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. Download the firmware
To access firmware images, please fill out the following form to provide some information so we can better understand your project needs.
If the form doesn’t load after a few seconds, you may need to refresh the page. Contact Digi Support Services if you are not able to access the firmware images. |
3. Program the firmware
There are multiple methods of programming the firmware to the target:
-
Use the Universal Update Utility (UUU) through a USB connection to your development PC.
-
Use a microSD card to install the firmware directly in the target.
-
Use USB mass storage to install the firmware directly in the target.
Program the firmware using UUU
-
Decompress the zip file in a directory of your choice.
-
Download the latest Universal Update Utility (UUU), a software tool from NXP.
UUU version should be 1.5.11 or higher. -
Place the
uuu
executable in a directory in your PATH, such as/usr/bin
. -
Install
udev
rules to allow any user to runuuu
to access the USB port:$ sudo sh -c "uuu -udev >> /etc/udev/rules.d/70-uuu.rules" $ sudo udevadm control --reload
-
Connect a micro USB cable to your development PC and the other end to the target USB OTG connector.
-
Reset the device by pressing the reset button on the board and immediately press any key in the serial terminal to stop the auto-boot process. The U-Boot bootloader prompt displays:
NOTICE: CPU: STM32MP135F Rev.Z NOTICE: Model: Digi International ConnectCore MP13 Development Kit NOTICE: BL2: v2.6-stm32mp1-r2.1(release):dub-2021.10-r4.2(8fdd4435) NOTICE: BL2: Built : 14:43:31, Sep 14 2023 NOTICE: BL2: Booting BL32 optee optee: OP-TEE: revision 3.16 (43350dda) U-Boot dub-2021.10-r4.2 (Sep 14 2023 - 14:42:17 +0000) CPU: STM32MP135F Rev.Z DRAM: 256 MiB optee optee: OP-TEE: revision 3.16 (43350dda) Clocks: - MPU : 650 MHz - AXI : 266.500 MHz - PER : 24 MHz - DDR : 533 MHz WDT: Started with servicing (32s timeout) NAND: 256 MiB MMC: STM32 SD/MMC: 1 In: serial Out: serial Err: serial Model: Digi International ConnectCore MP13 Development Kit ConnectCore MP13 SOM variant 0x01: 256 MiB DDR3, Wi-Fi, Bluetooth Board version 2 Boot: NAND Net: eth0: eth1@5800a000Get shared mii bus on eth2@5800e000 , eth1: eth2@5800e000 Normal Boot Hit any key to stop autoboot: 0 =>
Information in the console log may vary. -
On the target, in U-Boot, execute the following command:
=> fastboot 0
-
On your development PC, change to the directory where you extracted the ZIP file:
$ cd <zip-folder>
-
Run the
install_linux_fw_uuu.sh
script with-h
parameter to check the syntax:$ ./install_linux_fw_uuu.sh -h ############################################################ # Linux firmware install through USB OTG # ############################################################ Usage: ./install_linux_fw_uuu.sh [options] Options: -a <atf-filename> Arm-trusted-firmware filename. Auto-determined by variant if not provided. -b Activate bootcount mechanism (3 boot attempts). -d Install firmware on dualboot partitions (system A and system B). (Implies -b). -f <fip-filename> FIP filename. Auto-determined by variant if not provided. -h Show this help. -i <dey-image-name> Image name that prefixes the image filenames, such as 'dey-image-qt', 'dey-image-webkit', 'core-image-base'... Defaults to 'core-image-base' if not provided. -n No wait. Skips 10 seconds delay to stop script. -t Install TrustFence artifacts.
-
To program the default image files (core-image-base):
$ ./install_linux_fw_uuu.sh
If your SOM has a U-Boot v2021.10-r3 or older, the install process programs the new U-Boot but fails immediately after booting it. This is due to the reworked NAND partition layout on U-Boots newer than v2021.10-r3. Press Ctrl+C on your host to cancel the script, run
fastboot 0
again on the target, and retry.For more information, check Storage layout
-
Once the firmware is installed, the device boots automatically. The default username is root with no password.
Program the firmware using uSD card
-
Decompress the zip file.
-
Place the decompressed files in the root of a FAT-formatted microSD card and insert it in the microSD socket of the board.
-
Reset the device by pressing the reset button on the board and immediately press any key in the serial terminal to stop the auto-boot process. The U-Boot bootloader prompt displays:
NOTICE: CPU: STM32MP135F Rev.Z NOTICE: Model: Digi International ConnectCore MP13 Development Kit NOTICE: BL2: v2.6-stm32mp1-r2.1(release):dub-2021.10-r4.2(8fdd4435) NOTICE: BL2: Built : 14:43:31, Sep 14 2023 NOTICE: BL2: Booting BL32 optee optee: OP-TEE: revision 3.16 (43350dda) U-Boot dub-2021.10-r4.2 (Sep 14 2023 - 14:42:17 +0000) CPU: STM32MP135F Rev.Z DRAM: 256 MiB optee optee: OP-TEE: revision 3.16 (43350dda) Clocks: - MPU : 650 MHz - AXI : 266.500 MHz - PER : 24 MHz - DDR : 533 MHz WDT: Started with servicing (32s timeout) NAND: 256 MiB MMC: STM32 SD/MMC: 1 In: serial Out: serial Err: serial Model: Digi International ConnectCore MP13 Development Kit ConnectCore MP13 SOM variant 0x01: 256 MiB DDR3, Wi-Fi, Bluetooth Board version 2 Boot: NAND Net: eth0: eth1@5800a000Get shared mii bus on eth2@5800e000 , eth1: eth2@5800e000 Normal Boot Hit any key to stop autoboot: 0 =>
Information in the console log may vary. -
Check the U-Boot version on the console boot banner. If the version is
dub-2021.10-r2.1
or older, manually update the fsbl1 and fip-a partitions first. You can skip this step if you have a newer U-Boot version:=> update fsbl1 mmc 0 tf-a-ccmp13-dvk-nand.stm32 => update fip-a mmc 0 fip-ccmp13-dvk-optee.bin => reset
After the device reboots, press any key in the serial terminal to stop the auto-boot process.
-
To install the default firmware images (core-image-base) into the internal NAND, run the following command:
=> run install_linux_fw_sd
To program other images, set the variable
image-name
to the DEY image name (such asdey-image-webkit
orcore-image-base
) before running the script.=> setenv image-name core-image-base => run install_linux_fw_sd
If your SOM has a U-Boot v2021.10-r3 or older, the install process programs the new U-Boot but fails immediately after booting it. This is due to the reworked NAND partition layout on U-Boots newer than v2021.10-r3. Execute
run install_linux_fw_sd
again on the target to retry the command with the new U-Boot.For more information, check Storage layout
-
Once the firmware is installed, the device boots automatically. The default username is root with no password.
During installation, error messages appear when the installation process attempts to override MAC addresses. These messages are expected.
## Resetting to default environment oldval: 00:40:9D:7D:17:9A defval: 00:04:f3:ff:ff:fa ## Error: Can't overwrite "ethaddr" himport_r: can't insert "ethaddr=00:04:f3:ff:ff:fa" into hash table oldval: 00:40:9D:7D:17:9B defval: 00:04:f3:ff:ff:fb ## Error: Can't overwrite "eth1addr" himport_r: can't insert "eth1addr=00:04:f3:ff:ff:fb" into hash table oldval: 00:40:9D:7D:17:9C defval: 00:04:f3:ff:ff:fc ## Error: Can't overwrite "wlanaddr" himport_r: can't insert "wlanaddr=00:04:f3:ff:ff:fc" into hash table oldval: 00:40:9D:7D:17:9D defval: 00:04:f3:ff:ff:fd ## Error: Can't overwrite "btaddr" himport_r: can't insert "btaddr=00:04:f3:ff:ff:fd" into hash table
Program the firmware using USB mass storage
Follow these steps to install Yocto in the device:
-
Decompress the zip file.
-
Place the decompressed files in the root of a FAT-formatted USB mass storage and insert it in the USB host connector of the board.
-
Reset the device by pressing the reset button on the board and immediately press any key in the serial terminal to stop the auto-boot process. The U-Boot bootloader prompt displays:
NOTICE: CPU: STM32MP135F Rev.Z NOTICE: Model: Digi International ConnectCore MP13 Development Kit NOTICE: BL2: v2.6-stm32mp1-r2.1(release):dub-2021.10-r4.2(8fdd4435) NOTICE: BL2: Built : 14:43:31, Sep 14 2023 NOTICE: BL2: Booting BL32 optee optee: OP-TEE: revision 3.16 (43350dda) U-Boot dub-2021.10-r4.2 (Sep 14 2023 - 14:42:17 +0000) CPU: STM32MP135F Rev.Z DRAM: 256 MiB optee optee: OP-TEE: revision 3.16 (43350dda) Clocks: - MPU : 650 MHz - AXI : 266.500 MHz - PER : 24 MHz - DDR : 533 MHz WDT: Started with servicing (32s timeout) NAND: 256 MiB MMC: STM32 SD/MMC: 1 In: serial Out: serial Err: serial Model: Digi International ConnectCore MP13 Development Kit ConnectCore MP13 SOM variant 0x01: 256 MiB DDR3, Wi-Fi, Bluetooth Board version 2 Boot: NAND Net: eth0: eth1@5800a000Get shared mii bus on eth2@5800e000 , eth1: eth2@5800e000 Normal Boot Hit any key to stop autoboot: 0 =>
Information in the console log may vary. -
To install the default firmware images (core-image-base) into the internal NAND, run the following command:
=> run install_linux_fw_usb
To program other images, set the variable
image-name
to the DEY image name (such asdey-image-webkit
orcore-image-base
) before running the script.=> setenv image-name core-image-base => run install_linux_fw_usb
If your SOM has a U-Boot v2021.10-r3 or older, the install process programs the new U-Boot but fails immediately after booting it. This is due to the reworked NAND partition layout on U-Boots newer than v2021.10-r3. Execute
run install_linux_fw_usb
again on the target to retry the command with the new U-Boot.For more information, check Storage layout
-
Once the firmware is installed, the device boots automatically. The default username is root with no password.
During installation, error messages appear when the installation process attempts to override MAC addresses. These messages are expected.
## Resetting to default environment oldval: 00:40:9D:7D:17:9A defval: 00:04:f3:ff:ff:fa ## Error: Can't overwrite "ethaddr" himport_r: can't insert "ethaddr=00:04:f3:ff:ff:fa" into hash table oldval: 00:40:9D:7D:17:9B defval: 00:04:f3:ff:ff:fb ## Error: Can't overwrite "eth1addr" himport_r: can't insert "eth1addr=00:04:f3:ff:ff:fb" into hash table oldval: 00:40:9D:7D:17:9C defval: 00:04:f3:ff:ff:fc ## Error: Can't overwrite "wlanaddr" himport_r: can't insert "wlanaddr=00:04:f3:ff:ff:fc" into hash table oldval: 00:40:9D:7D:17:9D defval: 00:04:f3:ff:ff:fd ## Error: Can't overwrite "btaddr" himport_r: can't insert "btaddr=00:04:f3:ff:ff:fd" into hash table