# NXP imx8mm evk don't boot **URL:** \ **Category:** General Discussions\ **Tags:** yocto, sumo, nxp\ **Created:** [May 17, 2019, 3:35pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585 "2019-05-17T15:35:25Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jean](https://hub.mender.io/u/jean)\ **Post date:** [May 17, 2019, 3:35pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/1 "2019-05-17T15:35:25Z")
Hi All, I am trying to integrate meta-mender into a imx8mm (sumo branch) Yocto project for the NXP IMX8MM EVK and I encounter some issues. Here are my steps I made: repo init -u [https://source.codeaurora.org/external/imx/imx-manifest](https://source.codeaurora.org/external/imx/imx-manifest) -b imx-linux-sumo -m imx-4.9.123-2.3.0-8mm\_ga.xml DISTRO=fsl-imx-xwayland MACHINE=imx8mmevk source fsl-setup-release.sh -b build bitbake fsl-image-machine-test This generated a working sdcard image. Then I follow the Mender board integration documentation and include meta-mender into my Yocto project: git clone -b sumo git://github.com/mendersoftware/meta-mender IMX use u-boot-imx so I made the modification to support a fork of u-boot: Modify u-boot-imx\_2018.03.bb to include - require recipes-bsp/u-boot/u-boot-mender.inc - PROVIDES += “u-boot” - RPROVIDES\_${PN} += “u-boot” I checked that u-boot-imx default config for imx8mm has; - CONFIG\_BOOTCOUNT\_LIMIT=y - CONFIG\_BOOTCOUNT\_ENV=y Below my final local.conf: MENDER\_FEATURES\_ENABLE\_append = "mender-uboot mender-image-sd " MENDER\_FEATURES\_DISABLE\_append = "mender-grub mender-image-uefi " MENDER\_STORAGE\_DEVICE = “/dev/mmcblk1” MENDER\_STORAGE\_TOTAL\_SIZE\_MB = “15193” (value returned by the blockdev command for a 16Gb sdcard) MENDER\_UBOOT\_STORAGE\_DEVICE = “0” MENDER\_ARTIFACT\_NAME = “release-1” INHERIT += "mender-full " ARTIFACTIMG\_FSTYPE = “ext4” PREFERRED\_PROVIDER\_u-boot = “u-boot-imx” IMAGE\_BOOT\_FILES ?= “u-boot.bin” IMAGE\_FSTYPES\_remove += “sdcard.bz2” (To disable sdcard image generation) This configuration compile fine and generate a sdimg file. I “dd” the sdimg to sdcard, everything seems ok; 4 partitions, 2 rootfs with a boot directory containing the kernel, a boot partition with u-boot and a data partition. But the EVK doesn’t not boot. Nothing on the serial terminal. I suspect the bootloader is not well generated because imx needs a two level bootloader with a SPL and u-boot + some binaries. I found in [https://groups.google.com/a/lists.mender.io/forum/#!msg/mender/hyHk9a6C4K8/Qb3JoB9NBgAJ](https://groups.google.com/a/lists.mender.io/forum/#!msg/mender/hyHk9a6C4K8/Qb3JoB9NBgAJ) that a solution can be to generate a blob with u-boot, the SPL and all necessary binaries and to integrate it into the sdimg with MENDER\_IMAGE\_BOOTLOADER\_FILE = “${MENDER\_BOOTLOADER\_BLOB}”. But I don’t know how to do it. Anyone can help me? Thanks Regards, Jean ---
**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:** [May 17, 2019, 3:57pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/2 "2019-05-17T15:57:51Z")
Hi @jean, First of all welcome to Mender Hub. Second, we recently publish a reference integration for the imx8mqevk board, > [@NXP® i.MX 8MQuad Evaluation Kit](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567): > > The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is simply a board-specific complement to the official documentation. Board description The NXP® i.MX 8MQuad Evaluation Kit (EVK) provides a platform for rapid evaluation of the i.MX 8MQuad, i.MX 8MDual and i.MX 8MQuadLite Applications Processors, utilizing 2 to 4x Arm® Cortex®-A53s and 1x Cortex-M4 cores. It brings High-Performance with Low Power, Flexible options of Memory and High-Speed Interfaces as well as Industry-Leading Au… and there is also an demo manifest file in the i.MX BSP, [https://source.codeaurora.org/external/imx/imx-manifest/tree/README-mender?h=imx-linux-sumo](https://source.codeaurora.org/external/imx/imx-manifest/tree/README-mender?h=imx-linux-sumo) But to get to the bootloader configuration, for the `imx8mqevk` board we did the following, > And I suspect it would be something similar on the `imx8mmevk` ---
**Author:** ![jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jean](https://hub.mender.io/u/jean)\ **Post date:** [May 20, 2019, 1:05pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/3 "2019-05-20T13:05:45Z")
Hello Mirzak Thank for your quick reply and useful information. So I tried to use the demo manifest file in the IMX BSP but I still encounter some issues. here are my steps: - repo init -u [https://source.codeaurora.org/external/imx/imx-manifest](https://source.codeaurora.org/external/imx/imx-manifest) -b imx-linux-sumo -m imx-4.14.98-2.0.0\_demo\_mender.xml - repo sync - DISTRO=fsl-imx-xwayland MACHINE=imx8mqevk . fsl-setup-mender.sh -b build Then I adapt 0001-Add-Mender-support.patch, 0002-Improve-boot-startup-time.patch and meta-mender-imx/templates/local.conf to support IMX8MM instead of MX8MQ. Here is my final local.conf: ```auto INHERIT += "rm_work" MENDER_ARTIFACT_NAME = "release-1" INHERIT += "mender-full" DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" VIRTUAL-RUNTIME_initscripts = "" MENDER_FEATURES_DISABLE_append = " mender-grub mender-image-uefi" MENDER_FEATURES_ENABLE_append = " mender-uboot mender-image-sd" PREFERRED_PROVIDER_u-boot = "u-boot-imx" IMAGE_FSTYPES_remove = "tar.bz2 ext4 sdcard.bz2" IMAGE_BOOT_FILES_append = "u-boot-imx8mmevk.bin" MENDER_IMAGE_BOOTLOADER_FILE = "imx-boot-imx8mmevk-sd.bin" MENDER_IMAGE_BOOTLOADER_BOOTSECTOR_OFFSET = "66" do_image_sdimg[depends] += "imx-boot:do_deploy" IMAGE_INSTALL_append = " kernel-image kernel-devicetree" MENDER_STORAGE_DEVICE_imx8mmevk = "/dev/mmcblk1" ``` Compilation of u-boot-imx-2018.03 fails with this error: ```auto bitbake core-image-base aarch64-poky-linux-gcc --sysroot=/home/lserbetot/Developpement/imx-mender/build_imx8mm_mender/tmp/work/aarch64-poky-linux/u-boot-fw-utils-mender-auto-provided/1.0-r0/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/lserbetot/Developpement/imx-mender/build_imx8mm_mender/tmp/work/aarch64-poky-linux/u-boot-fw-utils-mender-auto-provided/1.0-r0=/usr/src/debug/u-boot-fw-utils-mender-auto-provided/1.0-r0 -fdebug-prefix-map=/home/lserbetot/Developpement/imx-mender/build_imx8mm_mender/tmp/work/aarch64-poky-linux/u-boot-fw-utils-mender-auto-provided/1.0-r0/recipe-sysroot= -fdebug-prefix-map=/home/lserbetot/Developpement/imx-mender/build_imx8mm_mender/tmp/work/aarch64-poky-linux/u-boot-fw-utils-mender-auto-provided/1.0-r0/recipe-sysroot-native= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -E -Wall -Wstrict-prototypes -Wno-format-security -fno-builtin -ffreestanding -fshort-wchar -O2 -fno-stack-protector -fno-delete-null-pointer-checks -g -fstack-usage -Wno-format-nonliteral -Werror=date-time -D __KERNEL__ -D __UBOOT__ -D __ARM__ -fno-pic -mstrict-align -ffunction-sections -fdata-sections -fno-common -ffixed-r9 -fno-common -ffixed-x18 -pipe -Iinclude -I./arch/arm/include -include ./include/linux/kconfig.h -nostdinc -isystem /home/lserbetot/Developpement/imx-mender/build_imx8mm_mender/tmp/work/aarch64-poky-linux/u-boot-fw-utils-mender-auto-provided/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../lib/aarch64-poky-linux/gcc/aarch64-poky-linux/7.3.0/include -DCONFIG_SPL_BUILD -DDO_DEPS_ONLY -dM ./include/common.h > spl/u-boot.cfg.tmp && { grep 'define CONFIG_' spl/u-boot.cfg.tmp > spl/u-boot.cfg; rm spl/u-boot.cfg.tmp; } || { rm spl/u-boot.cfg.tmp; false; } | In file included from include/config.h:11:0, | from ./include/common.h:21: | include/config_mender.h:73:5: error: #error CONFIG_SYS_MMC_ENV_DEV is not the same as MENDER_UBOOT_STORAGE_DEVICE. Either set it to the same value (check for example in the defconfig file), or make sure it is not defined at all. Make sure that: 1) All the instructions at docs.mender.io/devices/integrating-with-u-boot have been followed. 2) All required layers are included in bblayers.conf, including any board specific layers such as meta-mender- | # error CONFIG_SYS_MMC_ENV_DEV is not the same as MENDER_UBOOT_STORAGE_DEVICE. Either set it to the same value (check for example in the defconfig file), or make sure it is not defined at all. Make sure that: 1) All the instructions at docs.mender.io/devices/integrating-with-u-boot have been followed. 2) All required layers are included in bblayers.conf, including any board specific layers such as meta-mender- | ^ ~~~~ | In file included from include/config.h:11:0, | from ./include/common.h:21: | include/config_mender.h:73:5: error: #error CONFIG_SYS_MMC_ENV_DEV is not the same as MENDER_UBOOT_STORAGE_DEVICE. Either set it to the same value (check for example in the defconfig file), or make sure it is not defined at all. Make sure that: 1) All the instructions at docs.mender.io/devices/integrating-with-u-boot have been followed. 2) All required layers are included in bblayers.conf, including any board specific layers such as meta-mender- | # error CONFIG_SYS_MMC_ENV_DEV is not the same as MENDER_UBOOT_STORAGE_DEVICE. Either set it to the same value (check for example in the defconfig file), or make sure it is not defined at all. Make sure that: 1) All the instructions at docs.mender.io/devices/integrating-with-u-boot have been followed. 2) All required layers are included in bblayers.conf, including any board specific layers such as meta-mender- | ^ ~~~~ | In file included from include/config.h:11:0, | from ./include/common.h:21: | include/config_mender.h:73:5: error: #error CONFIG_SYS_MMC_ENV_DEV is not the same as MENDER_UBOOT_STORAGE_DEVICE. Either set it to the same value (check for example in the defconfig file), or make sure it is not defined at all. Make sure that: 1) All the instructions at docs.mender.io/devices/integrating-with-u-boot have been followed. 2) All required layers are included in bblayers.conf, including any board specific layers such as meta-mender- | # error CONFIG_SYS_MMC_ENV_DEV is not the same as MENDER_UBOOT_STORAGE_DEVICE. Either set it to the same value (check for example in the defconfig file), or make sure it is not defined at all. Make sure that: 1) All the instructions at docs.mender.io/devices/integrating-with-u-boot have been followed. 2) All required layers are included in bblayers.conf, including any board specific layers such as meta-mender- | ^ ~~~~ ``` I checked my bblayers.conf and meta-mender-imx is well included. bitbake -e core-image-base | grep “^MENDER\_UBOOT\_STORAGE\_DEVICE” returns MENDER\_UBOOT\_STORAGE\_DEVICE="". So I tried to add MENDER\_UBOOT\_STORAGE\_DEVICE = “0” to local.conf but the compilation error remains. Any idea about how to fix this compilation error? Thanks. Regards. Edit: @mirzak: add formatting of logs and code ---
**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:** [May 20, 2019, 1:22pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/4 "2019-05-20T13:22:35Z")
Just for reference this is what it looks like in my environment for `imx8mqevk`, ```auto bitbake u-boot -e | grep ^MENDER_UBOOT_STORAGE_DEVICE MENDER_UBOOT_STORAGE_DEVICE="1" MENDER_UBOOT_STORAGE_DEVICE_DEFAULT="" MENDER_UBOOT_STORAGE_DEVICE_DEFAULT_mender-ubi="dummy" MENDER_UBOOT_STORAGE_DEVICE_imx8mqevk="1" ``` And this is normally deducted from the `MENDER_STORAGE_DEVICE` variable and you rarely need to change this. There are two solutions, - make sure to remove any occurrences of `CONFIG_SYS_MMC_ENV_DEV` in you U-boot source for you board, this way `MENDER_UBOOT_STORAGE_DEVICE` will be used to define `CONFIG_SYS_MMC_ENV_DEV` during a Yocto build - make sure to set `MENDER_UBOOT_STORAGE_DEVICE` to the value that `CONFIG_SYS_MMC_ENV_DEV` has in your U-boot source for your board > I checked my bblayers.conf and meta-mender-imx is well included. bitbake -e core-image-base | grep “^MENDER\_UBOOT\_STORAGE\_DEVICE” returns MENDER\_UBOOT\_STORAGE\_DEVICE=“”. So I tried to add MENDER\_UBOOT\_STORAGE\_DEVICE = “0” to local.conf but the compilation error remains. I find it odd that it would be empty though. Also the error seems to be on the `u-boot-fw-utils-mender-auto-provided` recipe, do you get the same error if you run `bitbake u-boot`? ---
**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:** [May 20, 2019, 1:24pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/5 "2019-05-20T13:24:14Z")
> I find it odd that it would be empty though. Ah, it is empty if you run ``` bitbake core-image-base -e | grep ^MENDER_UBOOT_STORAGE_DEVICE` ``` but you should run: ```auto bitbake u-boot -e | grep ^MENDER_UBOOT_STORAGE_DEVICE ``` ---
**Author:** ![jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jean](https://hub.mender.io/u/jean)\ **Post date:** [May 20, 2019, 1:54pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/6 "2019-05-20T13:54:59Z")
Now my environment looks like the same as you: ```auto bitbake -e u-boot-imx | grep ^MENDER_UBOOT_STORAGE_DEVICE MENDER_UBOOT_STORAGE_DEVICE="1" MENDER_UBOOT_STORAGE_DEVICE_DEFAULT="" MENDER_UBOOT_STORAGE_DEVICE_DEFAULT_mender-ubi="dummy" MENDER_UBOOT_STORAGE_DEVICE_imx8mmevk="1" ``` I tried to run bitbake u-boot-imx and the compilation error is the same. CONFIG\_SYS\_MMC\_ENV\_DEV seems to be initialized with 0 and MENDER\_UBOOT\_STORAGE\_DEVICE equal to 1. I will try your first solution, removing all occurrences of CONFIG\_SYS\_MMC\_ENV\_DEV for the source code of u-boot. Thanks. Regards. ---
**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:** [May 20, 2019, 1:56pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/7 "2019-05-20T13:56:36Z")
> [@jean](#): > > I will try your first solution, removing all occurrences of CONFIG\_SYS\_MMC\_ENV\_DEV for the source code of u-boot. You do not need to remove it **all** occurrences, just the ones present for you board, e.g in your defconfig and board header. ---
**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:** [May 20, 2019, 1:58pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/8 "2019-05-20T13:58:36Z")
Also if it is initialized in U-boot as `0` this might mean that your SD card interface is 0 in U-boot, which means that you might need to adjust this, ```auto MENDER_STORAGE_DEVICE_imx8mmevk = "/dev/mmcblk1" ``` to ```auto MENDER_STORAGE_DEVICE_imx8mmevk = "/dev/mmcblk0" ``` Because this is what this variable is supposed to do, to make sure that the U-boot environment ends up on the correct device. ---
**Author:** ![jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jean](https://hub.mender.io/u/jean)\ **Post date:** [May 20, 2019, 2:19pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/9 "2019-05-20T14:19:24Z")
I found CONFIG\_SYS\_MMC\_ENV\_DEV only in my board header. I change it to match with MENDER\_UBOOT\_STORAGE\_DEVICE i.e. 1. Now u-boot-imx compiles well. But I get a Warning about the KERNEL\_DEVICETREE in the u-boot-imx-2018.03-r0 do\_provide\_mender\_defines: ```auto WARNING: u-boot-imx-2018.03-r0 do_provide_mender_defines: Found more than one dtb specified in KERNEL_DEVICETREE. Only one should be specified. Choosing the last one. ``` I thinked this issue comes from the cross compilation of u-boot-fw-utils and needs to add [https://github.com/mendersoftware/meta-mender-community/blob/sumo/meta-mender-renesas/recipes-bsp/u-boot/patches/default-gcc.patch](https://github.com/mendersoftware/meta-mender-community/blob/sumo/meta-mender-renesas/recipes-bsp/u-boot/patches/default-gcc.patch) but my tools/Makefile and tools/env/Makefile seems to be already with the right command: ```auto override HOSTCC = $(CC) ``` Any idea to fix this issue? Thanks. Note: When I run a sdcard image without mender, I can see that SDCard is referenced as /dev/mmblck1 and eMMC as /dev/mmcblck2. So from my point of view, /dev/mmcblk1 seems to be the right value for mender. ---
**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:** [May 20, 2019, 2:26pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/10 "2019-05-20T14:26:13Z")
> [@jean](#): > > WARNING: u-boot-imx-2018.03-r0 do\_provide\_mender\_defines: Found more than one dtb specified in KERNEL\_DEVICETREE. Only one should be specified. Choosing the last one. This is safe to ignore for now.[[MEN-2494] - Mender and CFEngine (by Northern.tech) Jira](https://tracker.mender.io/browse/MEN-2494) But do you get any additional build errors or was it just the warning? ---
**Author:** ![jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jean](https://hub.mender.io/u/jean)\ **Post date:** [May 20, 2019, 2:30pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/11 "2019-05-20T14:30:10Z")
The compilation succeed without errors or warning and the board now boot. So much thanks for your help Mirzak. But there is still an error on Linux kernel boot: ```auto u-boot=> run bootcmd switch to partitions #0, OK mmc0 is current device **Unable to read file boot.scr** **Unrecognized filesystem type** Booting from net ... ``` The above issue comes from the mender\_uboot\_root variable in u-boot. It is set to “mmc 1:2” which is the second partition of the eMMC instead of “mmc 0:2” which is the SDcard partition with the rootfs and the kernel. When I modified mender\_uboot\_root variable, Linux Kernel starts and everything works well. I found that mender\_uboot\_root variable is construct like this in the code; ```auto setenv mender_uboot_root " MENDER_UBOOT_STORAGE_INTERFACE " " __stringify(MENDER_UBOOT_STORAGE_DEVICE) ":${mender_boot_part}; ``` So I modified MENDER\_UBOOT\_STORAGE\_DEVICE and MENDER\_UBOOT\_STORAGE\_DEVICE\_imx8mmevk values to 0 but mender\_uboot\_root variable define by mender-setup command doesn’t reflect UBOOT\_STORAGE\_DEVICE value. It is still “mmc 1:2” instead of “mmc 0:2”. Any idea why mender\_uboot\_root is not well set? Thanks. ---
**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:** [June 3, 2019, 12:08pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/12 "2019-06-03T12:08:48Z")
hi @jean, there is now an integration for this board, > [@NXP® i.MX 8M Mini Evaluation Kit](https://hub.mender.io/t/nxp-i-mx-8m-mini-evaluation-kit/659): > > The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is simply a board-specific complement to the official documentation. Board description The i.MX 8M Mini EVK provides a platform for comprehensive evaluation of the i.MX 8M Mini and i.MX 8M Mini Lite applications processors. It delivers high performance with power efficiency, multimedia interfaces, and Wi-Fi/BT for connectivity out-of-the box. The two-board solution consists of a compact 2”x2”compute module and a larger base boar… Though it has not yet been run-time tested ---
**Author:** ![jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jean](https://hub.mender.io/u/jean)\ **Post date:** [June 12, 2019, 2:27pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/13 "2019-06-12T14:27:31Z")
Hi Mirzak, Thanks for the pointer. I will test it and send you some feedback. Regards. ---
**Author:** ![walidraach](https://avatars.discourse-cdn.com/v4/letter/w/ac91a4/32.png) [@walidraach](https://hub.mender.io/u/walidraach)\ **Post date:** [November 8, 2019, 11:29am UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/14 "2019-11-08T11:29:41Z")
hello @mirzak The image generated above assumes it is running from the eMMC ?? it’s work on SD card but not on eMMC i have core-image-base-imx8mmevk.sdimg and core-image-base-imx8mmevk.mender i flash the image with the commande uuu -b emmc\_all imx-boot-imx8mmevk-sd.bin-flash\_evk core-image-base-imx8mmevk.sdimg successfully but it start only u-boot What i have to do please ---
**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:** [November 8, 2019, 11:33am UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/15 "2019-11-08T11:33:20Z")
I believe the defaults will only work on SD. You need to adjust the following variables for it to work for eMMC, > ---
**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:** [November 8, 2019, 11:44am UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/16 "2019-11-08T11:44:57Z")
Additional reading: [https://docs.mender.io/2.2/devices/yocto-project/partition-configuration](https://docs.mender.io/2.2/devices/yocto-project/partition-configuration) ---
**Author:** ![walidraach](https://avatars.discourse-cdn.com/v4/letter/w/ac91a4/32.png) [@walidraach](https://hub.mender.io/u/walidraach)\ **Post date:** [November 15, 2019, 1:34pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/17 "2019-11-15T13:34:13Z")
Hello i set this config: MENDER\_STORAGE\_DEVICE\_imx8mmevk = “/dev/mmcblk0” and i have this problem when i boot from emmc mmc1(part 0) is current device \*\* Unable to read file boot.scr \*\* Card did not respond to voltage select! \*\* Bad device mmc 0 \*\* i thnik it’s the same problem as @jean ,what i have to do please?i have to modify mender\_uboot\_root variable??where can i find it? ---
**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:** [November 15, 2019, 5:17pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/18 "2019-11-15T17:17:10Z")
This appears to be using the standard bootcmd and not the one modified for use with Mender as it is trying to load a boot script. Do you have the Mender integration patches applied? Also, the “Bad device mmc 0” message indicates that you don’t have anything enumerated as device 1 on the MMC bus. What does “mmc list” show when manually run from the U-Boot prompt? Drew ---
**Author:** ![walidraach](https://avatars.discourse-cdn.com/v4/letter/w/ac91a4/32.png) [@walidraach](https://hub.mender.io/u/walidraach)\ **Post date:** [November 18, 2019, 1:35pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/19 "2019-11-18T13:35:13Z")
i just follow this link without any changes(imx8mmevk):[NXP® i.MX 8MQuad Evaluation Kit](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567) Compilation done succefuly,Boot with SDcard done also,i flash the image on emmc but i have boot error:mmc1(part 0) is current device \*\* Unable to read file boot.scr \*\* ![mmc_list](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/8520462efbc606c97dd86dae9cf728001a63528c.png) ---
**Author:** ![walidraach](https://avatars.discourse-cdn.com/v4/letter/w/ac91a4/32.png) [@walidraach](https://hub.mender.io/u/walidraach)\ **Post date:** [November 20, 2019, 1:17pm UTC](https://hub.mender.io/t/nxp-imx8mm-evk-dont-boot/585/20 "2019-11-20T13:17:00Z")
Can someone help me u-boot=\> fatload mmc 1:1 \*\* No boot file defined \*\* u-boot=\> fatls mmc 1:1 677053 u-boot-imx8mmevk.bin 1 file(s), 0 dir(s) what i have to do please