# Technexion PICO-PI-IMX7 **URL:** \ **Category:** Yocto Project\ **Tags:** yocto, sumo, imx7, nxp, pico-imx7, technexion, thud, dunfell\ **Created:** [November 24, 2018, 12:59pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136 "2018-11-24T12:59:44Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![jorisoffouga](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/jorisoffouga/32/64_2.png) [@jorisoffouga](https://hub.mender.io/u/jorisoffouga)\ **Post date:** [November 24, 2018, 12:59pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/1 "2018-11-24T12:59:44Z")
The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is a board-specific complement to the official documentation. # Board description PICO-PI-IMX7 is the Starting Kit for Android Things The i.MX 7Dual delivers high-performance processing for low-power requirements with a high degree of functional integration. The i.MX 7Dual features an advanced implementation of two ARM®Cortex®-A7 cores, which operate at speeds of up to 1.2 GHz, as well as the ARM® Cortex®-M4 core. The Pico variant is pin-compatible with the Intel® Edison for sensors and low-speed I/O, but also adds additional expansion possibilities for multimedia and connectivity, giving you cutting edge technology that can easily be expanded and implemented for IoT designs. ![pico](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/5e522b13daa4be096a43b40cbbf688f715c59dbe.jpeg) URL:[https://shop.technexion.com/pico-pi-imx7.html](https://shop.technexion.com/pico-pi-imx7.html) # Test results The Yocto Project releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other [Yocto Project releases](https://wiki.yoctoproject.org/wiki/Releases?target=_blank): | Yocto Project | Build | Runtime | | --- | --- | --- | | sumo (2.5) | :test_works: | :test_works: | | thud (2.6) | :test_works: | :test_works: | | warrior (2.7) | :test_works: | :test_works: | | zeus (3.0) | :test_works: | :test_works: | | dunfell (3.1) | :test_works: | :test_works: | **Build** Means that the Yocto Project build using this Mender integration completes without errors and outputs images. **Runtime** Means that Mender has been verified to work on the board. For U-Boot-based boards, the [integration checklist](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot/integration-checklist?target=_blank) has been verified. # Getting started ## Prerequisites - A supported Linux distribution and dependencies installed on your workstation/laptop as described in the [Yocto Mega Manual](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#detailed-supported-distros) - NOTE. Instructions depend on which Yocto version you intend to use. - Google repo tool [installed](https://hub.mender.io/t/google-repo/58/2) and in your `PATH`. ## Configuring the build ### Setup Yocto environment Set the Yocto Project branch you are building for: ```auto # set to your branch, make sure it is supported (see table above) export BRANCH="dunfell" ``` Create a directory for your `mender-nxp` setup to live in and clone the meta information. ```auto mkdir mender-nxp && cd mender-nxp ``` Initialize repo manifest: ```auto repo init -u https://github.com/mendersoftware/meta-mender-community \ -m meta-mender-nxp/scripts/manifest-nxp.xml \ -b ${BRANCH} ``` Fetch layers in manifest: ```auto repo sync ``` ## Setup build environment Initialize the build environment: ```auto source setup-environment nxp ``` **NOTE!** You need to accept the Freescale EULA at ‘../sources/meta-freescale/EULA’. Please read it and in case you accept it, add: ``` ACCEPT_FSL_EULA = "1" ``` in your local.conf. ### Building the image You can now proceed with building an image: ```auto MACHINE=imx7d-pico bitbake core-image-base ``` Replace `core-image-base` with your desired image target. ### Using the build output After a successful build, the images and build artifacts are placed in `tmp/deploy/images/imx7d-pico/`. - `tmp/deploy/images/imx7d-pico/core-image-base-imx7d-pico.sdimg` - `tmp/deploy/images/imx7d-pico/core-image-base-imx7d-pico.mender` - `tmp/deploy/images/SPL` - `tmp/deploy/images/u-boot-dtb.img` The disk image (with `.sdimg` suffix) is used to provision the device storage for devices without Mender running already. Please proceed to [the official documentation on provisioning a new device](https://docs.mender.io/system-updates-yocto-project/provisioning-a-new-device?target=_blank) for steps to do this. On the other hand, if you already have Mender running on your device and want to deploy a rootfs update using this build, you should use the [Mender Artifact](https://docs.mender.io/overview/artifact) files, which have `.mender` suffix. You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client [standalone mode](https://docs.mender.io/artifact-creation/standalone-deployment). #### Flash instructions Based on the output artifacts described above we need to flash the SPL, u-boot.imx and core-image-base-imx7d-pico.sdimg separately to fully provision an device and for it to work with Mender. Required software on the host PC: - imx\_usb\_loader: [GitHub - boundarydevices/imx\_usb\_loader: USB & UART loader for i.MX5/6/7/8 series](https://github.com/boundarydevices/imx_usb_loader) - dfu-util - libusb ```auto git clone https://github.com/boundarydevices/imx_usb_loader ``` ```auto cd imx_usb_loader && make ``` **Loading U-Boot via USB Serial Download Protocol** Note: This method is convenient for development purposes. If the eMMC has already a U-Boot flashed with DFU support then the user can go to step 2 below in order to update U-Boot. Put pico board in Serial Boot Loader mode (refer to the PICO-iMX7D Quick Start Guide page 18 ([https://www.nxp.com/docs/en/user-guide/PICO-IMX7D-USG.pdf](https://www.nxp.com/docs/en/user-guide/PICO-IMX7D-USG.pdf)) Connect a USB to serial adapter between the host PC and pico. Connect a USB cable between the OTG pico port and the host PC. Open a terminal program such as minicom. Copy SPL and u-boot.img to the imx\_usb\_loader folder. Load the SPL binary via USB: ```auto $ sudo ./imx_usb SPL ``` Load the u-boot.img binary via USB: ```auto $ sudo ./imx_usb u-boot-dtb.img ``` Then U-Boot starts and its messages appear in the console program. Use the default environment variables: ```auto => env default -f -a ``` ```auto => saveenv ``` **Flashing Image into the eMMC** From the u-boot : ```auto => ums 0 mmc 0 ``` From the host : ```auto sudo dd if=core-image-base-imx7d-pico.sdimg of=/dev/sdX bs=1M ; sudo sync ``` After flashing use ctrl-c to get out of ums. **Flashing U-Boot into the eMMC** Run the DFU agent so we can flash the new images using dfu-util tool: ```auto => dfu 0 mmc 0 ``` Flash SPL and u-boot.img into the eMMC running the following commands on a PC: ```auto $ sudo dfu-util -D SPL -a spl ``` ```auto $ sudo dfu-util -D u-boot-dtb.img -a u-boot ``` The following message should be seen on the U-Boot prompt after a successful upgrade: ```auto #DOWNLOAD …​ OK Ctrl+C to exit …​ ``` Remove power from the pico board. Put pico board into normal boot mode. Power up the board and the new updated U-Boot should boot from eMMC. # References - The sources of the Yocto integration can be found in [meta-mender-community/meta-mender-nxp](https://github.com/mendersoftware/meta-mender-community/tree/dunfell/meta-mender-nxp) * * * _If this post was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!_ ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [November 24, 2018, 9:08pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/2 "2018-11-24T21:08:56Z")
Thanks for sharing and contributing. Actually shouldn’t name of board should be wandaboard (just renamed from other vendor?). I looked to both of then and they look very similar, anyway I can be wrong. ---
**Author:** ![jorisoffouga](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/jorisoffouga/32/64_2.png) [@jorisoffouga](https://hub.mender.io/u/jorisoffouga)\ **Post date:** [November 24, 2018, 10:19pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/3 "2018-11-24T22:19:13Z")
It’s a pleasure to contribute 😊, wanderboard is one of the redistributors of the pico pi imx7 ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [November 25, 2018, 9:55am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/4 "2018-11-25T09:55:24Z")
OK I see. Thanks for clarification. ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 15, 2019, 9:04am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/5 "2019-08-15T09:04:54Z")
14 posts were split to a new topic: [Issues with Technexion PICO-PI-IMX7 Yocto environment](https://hub.mender.io/t/issues-with-technexion-pico-pi-imx7-yocto-environment/938) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 15, 2019, 8:57am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/19 "2019-08-15T08:57:16Z")
5 posts were split to a new topic: [Device hangs during boot - Technexion PICO-PI-IMX7 - Yocto](https://hub.mender.io/t/device-hangs-during-boot-technexion-pico-pi-imx7-yocto/934) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 15, 2019, 9:02am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/24 "2019-08-15T09:02:06Z")
6 posts were split to a new topic: [Second CPU core missing - Technexion PICO-PI-IMX7 - Yocto](https://hub.mender.io/t/second-cpu-core-missing-technexion-pico-pi-imx7-yocto/936) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 15, 2019, 9:03am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/30 "2019-08-15T09:03:31Z")
5 posts were split to a new topic: [Bluetooth on Technexion PICO-PI-IMX7](https://hub.mender.io/t/bluetooth-on-technexion-pico-pi-imx7/937) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 15, 2019, 9:10am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/35 "2019-08-15T09:10:39Z")
A post was split to a new topic: [License error on Technexion PICO-PI-IMX7](https://hub.mender.io/t/license-error-on-technexion-pico-pi-imx7/939) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [September 27, 2019, 9:04am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/36 "2019-09-27T09:04:32Z")
19 posts were split to a new topic: [Problems with imx\_usb on PICO-PI-IMX/](https://hub.mender.io/t/problems-with-imx-usb-on-pico-pi-imx/1081) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 20, 2020, 8:16am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/37 "2020-10-20T08:16:33Z")
8 posts were split to a new topic: [Issues with the PICO-PI-IMX7](https://hub.mender.io/t/issues-with-the-pico-pi-imx7/2693) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [October 20, 2020, 8:17am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/38 "2020-10-20T08:17:49Z")
@jorisoffouga, this has been a very popular board here. Any plans to update this to zeus or dunfell? ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [June 11, 2021, 12:18am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/40 "2021-06-11T00:18:25Z")
Hi, I stay trying put ligpiod v.1.6 in my yocto (imx7d-pico) But I need hardknott. I stay trying copy and change sources/meta-openembedded/meta-oe looking for github version 1.6 but got the following error (which can also be seen in the screen below); ERROR: Layer openembedded-layer is not compatible with the core layer which only supports these series: dunfell (layer is compatible with hardknot ![Captura de tela de 2021-06-10 21-05-08](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/7/733d07e4d78f1bbb1635f963fb397e9f36127b64.png) ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [June 11, 2021, 1:02am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/41 "2021-06-11T01:02:48Z")
That’s expected. Mender currently support only dunfell. If you need a newer branch you’ll need to do some porting. Drew ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [June 11, 2021, 6:58pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/42 "2021-06-11T18:58:16Z")
@drewmoseley I have available time and I need this. Please give me the step by step for me to porting Pls ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [June 13, 2021, 12:28am UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/43 "2021-06-13T00:28:05Z")
Yocto dunfell have issue: ERROR: u-boot-fslc-v2020.04+gitAUTOINC+88c58453be-r0 do\_patch: Command Error: ‘quilt --quiltrc /home/neuberfran/mender-nxp5/build/tmp/work/imx7d\_pico-poky-linux-gnueabi/u-boot-fslc/v2020.04+gitAUTOINC+88c58453be-r0/recipe-sysroot-native/etc/quiltrc push’ exited with 0 Output: Applying patch 0001-ARM-Pico-Pi-i.MX7D-support-to-mender.patch patching file configs/pico-pi-imx7d\_defconfig Hunk #1 succeeded at 18 with fuzz 1 (offset 4 lines). Hunk #2 FAILED at 35. Hunk #3 FAILED at 64. 2 out of 3 hunks FAILED – rejects in file configs/pico-pi-imx7d\_defconfig patching file include/configs/pico-imx7d.h Hunk #1 FAILED at 173. Hunk #2 succeeded at 168 (offset -23 lines). 1 out of 2 hunks FAILED – rejects in file include/configs/pico-imx7d.h Patch 0001-ARM-Pico-Pi-i.MX7D-support-to-mender.patch does not apply (enforce with -f) ERROR: Logfile of failure stored in: /home/neuberfran/mender-nxp5/build/tmp/work/imx7d\_pico-poky-linux-gnueabi/u-boot-fslc/v2020.04+gitAUTOINC+88c58453be-r0/temp/log.do\_patch.1506384 ERROR: Task (/home/neuberfran/mender-nxp5/build/…/sources/meta-freescale/recipes-bsp/u-boot/u-boot-fslc\_2020.04.bb:do\_patch) failed with exit code '1 ---
**Author:** ![texierp](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/texierp/32/45_2.png) [@texierp](https://hub.mender.io/u/texierp)\ **Post date:** [June 13, 2021, 6:26pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/44 "2021-06-13T18:26:40Z")
@neuberfran Yes seems normal, this board has not been tested with `dunfell` release (see Test results section) ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [June 14, 2021, 2:03pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/45 "2021-06-14T14:03:03Z")
Yeah, unfortunately there is not a simple step-by-step for resolving patch failures. You will need to try to manually apply it using `git am` and `patch` and then inspect the reject files that show the patch hunks that cannot be applied. You will need to figure out how to make an equivalent change for the failed hunks in the current versions of the files. ---
**Author:** ![texierp](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/texierp/32/45_2.png) [@texierp](https://hub.mender.io/u/texierp)\ **Post date:** [June 18, 2021, 8:25pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/46 "2021-06-18T20:25:51Z")
@neuberfran FYI, I just open a PR for dunfell, see [pico-pi-imx7d: bump to dunfell by texierp · Pull Request #232 · mendersoftware/meta-mender-community · GitHub](https://github.com/mendersoftware/meta-mender-community/pull/232) Also, the commit in [1] is also needed [1] - [u-boot-mender: Ignore case when checking variables in mender\_Kconfig\_… by texierp · Pull Request #1398 · mendersoftware/meta-mender · GitHub](https://github.com/mendersoftware/meta-mender/pull/1398) ---
**Author:** ![neuberfran](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/neuberfran/32/369_2.png) [@neuberfran](https://hub.mender.io/u/neuberfran)\ **Post date:** [June 27, 2021, 7:19pm UTC](https://hub.mender.io/t/technexion-pico-pi-imx7/136/47 "2021-06-27T19:19:38Z")
@drewmoseley @mirzak @jorisoffouga @mirzak Issue in 27/june/2021 When I try dunfell =\> ERROR: u-boot-fslc-v2020.04+gitAUTOINC+88c58453be-r0 do\_patch: Command Error: ‘quilt --quiltrc /home/neuberfran/mender-nxp3/build/tmp/work/imx7d\_pico-poky-linux-gnueabi/u-boot-fslc/v2020.04+gitAUTOINC+88c58453be-r0/recipe-sysroot-native/etc/quiltrc push’ exited with 0 Output: Applying patch 0001-ARM-Pico-Pi-i.MX7D-support-to-mender.patch patching file configs/pico-pi-imx7d\_defconfig Hunk #1 succeeded at 18 with fuzz 1 (offset 4 lines). Hunk #2 FAILED at 35. Hunk #3 FAILED at 64. 2 out of 3 hunks FAILED – rejects in file configs/pico-pi-imx7d\_defconfig patching file include/configs/pico-imx7d.h Hunk #1 FAILED at 173. Hunk #2 succeeded at 168 (offset -23 lines). 1 out of 2 hunks FAILED – rejects in file include/configs/pico-imx7d.h Patch 0001-ARM-Pico-Pi-i.MX7D-support-to-mender.patch does not apply (enforce with -f) ERROR: Logfile of failure stored in: /home/neuberfran/mender-nxp3/build/tmp/work/imx7d\_pico-poky-linux-gnueabi/u-boot-fslc/v2020.04+gitAUTOINC+88c58453be-r0/temp/log.do\_patch.793240 ERROR: Task (/home/neuberfran/mender-nxp3/build/…/sources/meta-freescale/recipes-bsp/u-boot/u-boot-fslc\_2020.04.bb:do\_patch) failed with exit code '1 ![Captura de tela de 2021-06-27 16-18-35](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/d/d48a2967dd4ca8292460a358faddf50150c18e59.png) [Next page](https://hub.mender.io/t/technexion-pico-pi-imx7/136.md?page=2)