# \[INCOMPLETE\] i.MX 6ULL EVK **URL:** \ **Category:** Yocto Project\ **Tags:** rocko, nxp\ **Created:** [May 28, 2019, 9:13am UTC](https://hub.mender.io/t/incomplete-i-mx-6ull-evk/635 "2019-05-28T09:13:08Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![brianPTL](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@brianPTL](https://hub.mender.io/u/brianPTL)\ **Post date:** [May 28, 2019, 9:13am UTC](https://hub.mender.io/t/incomplete-i-mx-6ull-evk/635/1 "2019-05-28T09:13:08Z")
The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is a board-specific complement to the official documentation. # Device description The i.MX 6ULL EVK is a market-focused development tool based on the i.MX 6ULL applications processor. The i.MX6 ULL processor is part of an efficient and cost-optimized product family that features an advanced implementation of a single Arm® Cortex®-A7 core operating at speeds of up to 900 MHz. This EVK enables an LCD display and audio playback as well as many connectivity options. It is designed to showcase the most commonly used features of the processor in a small, low-cost package and to facilitate software development with the ultimate goal of faster time to market through the support of the Linux® operating system. ![MCIMX6ULL-EVK-BD](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/a38d8bbb4abe433511521f47a18f06f58d124610.jpeg) URL: [https://www.nxp.com/support/developer-resources/evaluation-and-development-boards/i.mx-evaluation-and-development-boards/evaluation-kit-for-the-i.mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK](https://www.nxp.com/support/developer-resources/evaluation-and-development-boards/i.mx-evaluation-and-development-boards/evaluation-kit-for-the-i.mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK) # 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 | | --- | --- | --- | | rocko (imx-4.9.88-2.0.0\_ga) | :test_unknown: | :test_unknown: | **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/devices/yocto-project/bootloader-support/u-boot/integration-checklistt?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 Create a directory for your `mender-imx6ull` setup to live in and clone the meta information. ```auto mkdir mender-imx6ull && cd mender-imx6ull ``` Initialize repo manifest from NXP: ```auto repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-rocko -m imx-4.9.88-2.0.0_ga.xml ``` Download and Initialize repo manifest for our Mender layers ```auto wget --directory-prefix .repo/manifests https://raw.githubusercontent.com/brianleePTL/meta-mender-community/rocko/meta-mender-nxp-imx6ull/scripts/imx-4.9.88-2.0.0_demo_mender.xml repo init -m imx-4.9.88-2.0.0_demo_mender.xml ``` Fetch layers in manifest: ```auto repo sync ``` ## Setup build environment: Initialise the build environment: ```auto DISTRO=fsl-imx-fb MACHINE=imx6ull14x14evk . fsl-setup-mender.sh -b build ``` ### Configure Mender server URL (optional) This section is not required for a successful build but images that are generated by default are only suitable for usage with the Mender client in [Standalone deployments](https://docs.mender.io/architecture/standalone-deployments?target=_blank), due to lack of server configuration. You can edit the `conf/local.conf` file to provide your Mender server configuration, ensuring the generated images and Mender Artifacts are connecting to the Mender server that you are using. There should already be a commented section in the generated `conf/local.conf` file and you can simply uncomment the relevant configuration options and assign appropriate values to them. Build for Hosted Mender: ```auto # To get your tenant token: # - log in to https://hosted.mender.io # - click your email at the top right and then "My organization" # - press the "COPY TO CLIPBOARD" # - assign content of clipboard to MENDER_TENANT_TOKEN # MENDER_SERVER_URL = "https://hosted.mender.io" MENDER_TENANT_TOKEN = "" ``` Build for Mender demo server: ```auto # https://docs.mender.io/getting-started/create-a-test-environment # # Update IP address to match the machine running the Mender demo server MENDER_DEMO_HOST_IP_ADDRESS = "192.168.0.100" ``` ### Building the image You can now proceed with building an image: ```auto bitbake core-image-minimal ``` Replace `core-image-minimal` with your desired image target. ### Using the build output After a successful build, the images and build artifacts are placed in `build/tmp/deploy/images/imx6ull14x14evk/` . - `build/tmp/deploy/images/imx8mqevk/core-image-minimal-imx6ull14x14evk.sdimg` - `build/tmp/deploy/images/imx8mqevk/core-image-minimal-imx6ull14x14evk.mender` The disk image `.sdimg` 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/artifacts/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/architecture/mender-artifacts?target=_blank) 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 only in [Standalone deployments](https://docs.mender.io/architecture/standalone-deployments?target=_blank). # References - The sources of the Yocto integration can be found in [meta-mender-community/meta-mender-nxp-imx6ull](https://github.com/brianleePTL/meta-mender-community/tree/rocko/meta-mender-nxp-imx6ull) * * * _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:** ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)\ **Post date:** [May 11, 2020, 7:04am UTC](https://hub.mender.io/t/incomplete-i-mx-6ull-evk/635/2 "2020-05-11T07:04:45Z")
Hello, I’m following this mender tutorial to enable mender OTA update agent in out iMX 6UL EVK from NXP. It builds silently in the above mentioned configuration but when i try to boot up my device it gets stuck at “Starting kernel” phase. The detailed log is attached as follows, ```auto =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.05.04 19:32:09 =~=~=~=~=~=~=~=~=~=~=~= U-Boot 2017.03-imx_v2017.03_4.9.88_2.0.0_ga+gb76bb1bf9f (May 04 2020 - 18:50:27 +0530) CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz) CPU: Industrial temperature grade (-40C to 105C) at 43C Reset cause: POR Model: Freescale i.MX6 ULL 14x14 EVK Board Board: MX6ULL 14x14 EVK DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment Display: TFT43AB (480x272) Video: 480x272x24 In: serial Out: serial Err: serial switch to partitions #0, OK mmc1 is current device Net: Error: ethernet@020b4000 address not set. No ethernet found. Normal Boot Hit any key to stop autoboot: 3 0 => hs aaaa elp aa boot mendaa a a base bdinfo bmode bmp boot bootd bootefi bootelf bootm bootp bootvx bootz clocks clrlogo cmp coninfo cp crc32 ... => base bdinfo bmode bmp boot bootd bootefi bootelf bootm bootp bootvx bootz clocks clrlogo cmp coninfo cp crc32 ... => m md mdio mii mm mmc mmcinfo mtest mw => m md mdio mii mm mmc mmcinfo mtest mw => m md mdio mii mm mmc mmcinfo mtest mw => m bootd ## Error: "findtee" not defined switch to partitions #0, OK mmc1 is current device switch to partitions #0, OK mmc1 is current device reading boot.scr **Unable to read file boot.scr** reading zImage 8129768 bytes read in 376 ms (20.6 MiB/s) Booting from mmc ... reading imx6ull-14x14-evk.dtb **Unable to read file imx6ull-14x14-evk.dtb** Kernel image @ 0x80800000 [0x000000 - 0x7c0ce8] Starting kernel ... ``` Any help would much be appreciated. Thanks in advance. ---
**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:** [May 11, 2020, 5:38pm UTC](https://hub.mender.io/t/incomplete-i-mx-6ull-evk/635/3 "2020-05-11T17:38:50Z")
It looks like you are getting quite a bit of noise on your terminal. We have seen this interrupt the boot on other platforms leaving the system at the U-Boot prompt. In your case it appears to be interacting even more poorly with the boot sequence. I think you need to resolve that first and then see what, if any, symptoms remain. Drew ---
**Author:** ![danie](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/danie/32/620_2.png) [@danie](https://hub.mender.io/u/danie)\ **Post date:** [May 12, 2020, 7:54am UTC](https://hub.mender.io/t/incomplete-i-mx-6ull-evk/635/4 "2020-05-12T07:54:54Z")
Hey, Thanks for your reply but sorry for my miserable log, actually that contains commands I tried executing. The actual **problem** from my POV is the **missing DTB** (imx6ull-14x14-evk.dtb) ```auto Unable to read file boot.scr Unable to read file imx6ull-14x14-evk.dtb ``` The uninterupted log is as follows, ```auto U-Boot 2017.03-imx_v2017.03_4.9.88_2.0.0_ga+gb76bb1bf9f (May 12 2020 - 13:04:44 +0530) CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz) CPU: Industrial temperature grade (-40C to 105C) at 37C Reset cause: POR Model: Freescale i.MX6 ULL 14x14 EVK Board Board: MX6ULL 14x14 EVK DRAM: 512 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment Display: TFT43AB (480x272) Video: 480x272x24 In: serial Out: serial Err: serial switch to partitions #0, OK mmc1 is current device Net: Error: ethernet@020b4000 address not set. No ethernet found. Normal Boot Hit any key to stop autoboot: 3 2 1 0 ## Error: "findtee" not defined switch to partitions #0, OK mmc1 is current device switch to partitions #0, OK mmc1 is current device reading boot.scr **Unable to read file boot.scr** reading zImage 8123752 bytes read in 373 ms (20.8 MiB/s) Booting from mmc ... reading imx6ull-14x14-evk.dtb **Unable to read file imx6ull-14x14-evk.dtb** Kernel image @ 0x80800000 [0x000000 - 0x7bf568] Starting kernel ... ``` When I dig into the contents of efi partition, I got the following: ```auto => ls mmc 1 efi/ 37763 imx6ul-14x14-evk-btwifi.dtb 37100 imx6ul-14x14-evk-csi.dtb 37228 imx6ul-14x14-evk-emmc.dtb 37654 imx6ul-14x14-evk-gpmi-weim.dtb 37347 imx6ul-14x14-evk-usb-certi.dtb 37104 imx6ul-14x14-evk.dtb 8123752 zimage 7 file(s), 1 dir(s) ``` ---
**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:** [May 13, 2020, 6:52pm UTC](https://hub.mender.io/t/incomplete-i-mx-6ull-evk/635/5 "2020-05-13T18:52:02Z")
Mender normally loads the file from your root filesystem partition rather than the EFI partition. That way we can have proper redundancy. I will guess that the _imx6ull-14x14-evk.dtb_ doesn’t exist there either since it is not in the EFI partition. How is that DTB name getting set? Mender sets a static one with the bitbake variable MENDER\_DTB\_NAME but some platforms require a bit of extra processing by the bootloader to dynamically determine the correct one. Drew