### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 6, 2019, 1:26pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/1 "2019-11-06T13:26:37Z")
Hello all,
I have an imx8mmevk board, and I want to generate an image with Yocto containing Mender,
So I did follow the demo mender from this website: [Mender-demo](https://hub.mender.io/t/nxp-i-mx-8mquad-evaluation-kit/567)
The image core-image-base was built successfully, and now I have the choice to flash the image in an SDCARD or in the eMMC flash,
1. SDCARD was flashed correctly with dd , and the system boots correctly
2. For the eMMC I’m using uuu (Universal Update Utiliy) of NXP to flash it, I’m fimilar with this tool and I always flash the eMMC, but to flash the eMMC I need to give the bootloader alone and the image img too,
the question is when I’m giving it the u-boot-imx and the sdimg it fails,
And I think the problem is that the sdimg is already containing a BOOT partition
I have an idea with MENDER\_BOOT\_PART\_SIZE\_MB = “0”
Is my idea is correct or there is an other solution ?
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 6, 2019, 5:36pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/2 "2019-11-06T17:36:24Z")
I think you are on the right track, and the problem is probably that the `sdimg` contains the bootloader binary as well.
To disable this you would need to override this variable (set it to an empty string), which will disable the logic to embedded the U-Boot binary in to the `sdimg` file.
>
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 11, 2019, 9:34am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/3 "2019-11-11T09:34:08Z")
This is not working , I made it an empty string and I rebuilt core-image-base
And I flashed the emmc of the board with :
imx-boot-imx8mmevk-sd.bin-flash\_evk as bootloader
and core-image-base-imx8mmevk-20191111091630.sdimg as the image
but when booting the board it stuck at u-boot , I think because it’s not the right bootloader it dont know that the emmc is splitted as 4 partitions
I changed the MENDER\_STORAGE\_DEVICE\_imx8mmevk = “/dev/mmcblk1” to 0
and still not booting
I think the problem is with the bootloader
How can I generate a mender u-boot separatly ,
help plesae
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 13, 2019, 1:45pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/4 "2019-11-13T13:45:25Z")
Please any solutioon ??
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 14, 2019, 9:44am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/5 "2019-11-14T09:44:36Z")
It would be helpful if you can share the serial console output, which should provide more details about what is going wrong
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 15, 2019, 3:34pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/6 "2019-11-15T15:34:04Z")
U-Boot SPL 2018.03-imx\_v2018.03\_4.14.98\_2.0.0\_ga+g87a19df (Nov 15 2019 - 12:39:)
power\_bd71837\_init
DDRINFO: start lpddr4 ddr init
DRAM PHY training for 3000MTS
check ddr4\_pmu\_train\_imem code
check ddr4\_pmu\_train\_imem code pass
check ddr4\_pmu\_train\_dmem code
check ddr4\_pmu\_train\_dmem code pass
Training PASS
DRAM PHY training for 400MTS
check ddr4\_pmu\_train\_imem code
check ddr4\_pmu\_train\_imem code pass
check ddr4\_pmu\_train\_dmem code
check ddr4\_pmu\_train\_dmem code pass
Training PASS
DRAM PHY training for 100MTS
check ddr4\_pmu\_train\_imem code
check ddr4\_pmu\_train\_imem code pass
check ddr4\_pmu\_train\_dmem code
check ddr4\_pmu\_train\_dmem code pass
Training PASS
DRAM PHY training for 3000MTS
check ddr4\_pmu\_train\_imem code
check ddr4\_pmu\_train\_imem code pass
check ddr4\_pmu\_train\_dmem code
check ddr4\_pmu\_train\_dmem code pass
Training PASS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC2
U-Boot 2018.03-imx\_v2018.03\_4.14.98\_2.0.0\_ga+g87a19df (Nov 15 2019 - 12:39:59 +)
CPU: Freescale i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 43C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
MMC: FSL\_SDHC: 0, FSL\_SDHC: 1
Loading Environment from MMC… \*\*\* Warning - bad CRC, using default environment
Failed (-5)
No panel detected: default to MIPI2HDMI
adv7535\_init: Can’t find device id=0x3d, on bus 1
Display: MIPI2HDMI (1920x1080)
Video: 1920x1080x24
In: serial
Out: serial
Err: serial
BuildInfo:
- ATF 1cb68fa
- U-Boot 2018.03-imx\_v2018.03\_4.14.98\_2.0.0\_ga+g87a19df
switch to partitions #0, OK
mmc1(part 0) is current device
flash target is MMC:1
Net:
Warning: ethernet@30be0000 using MAC address from ROM
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
\*\* Unable to read file boot.scr \*\*
Saving Environment to MMC… Writing to redundant MMC(1)… OK
Card did not respond to voltage select!
\*\* Bad device mmc 0 \*\*
Booting from net …
ethernet@30be0000 Waiting for PHY auto negotiation to complete… TIMEOUT!
Could not initialize PHY ethernet@30be0000
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
.
.
.
---
### Author:  [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [November 15, 2019, 5:25pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/7 "2019-11-15T17:25:25Z")
The Uboot doesn’t seem to recognize the MMC device #1: “Bad device MMC1”
My guess is that is the SDCard and there is not one inserted. That is the default if you follow the instructions you linked above. You may be able to change the settings in your local.conf for MENDER\_STORAGE\_DEVICE\* to point at mmcblk0 instead but that’s just a guess. [https://github.com/mendersoftware/meta-mender-community/blob/sumo/meta-mender-imx/templates/local.conf.append](https://github.com/mendersoftware/meta-mender-community/blob/sumo/meta-mender-imx/templates/local.conf.append)
Drew
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 18, 2019, 9:12am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/8 "2019-11-18T09:12:06Z")
I made everything , pointing to mmcblk0
But here’s the output of some mmc info:
> u-boot=\> mmc list
> FSL\_SDHC: 0
> FSL\_SDHC: 1 (eMMC)
> u-boot=\> mmc part
>
> Partition Map for MMC device 1 – Partition Type: DOS
>
> Part Start Sector Num Sectors UUID Type
> 1 49152 32768 9695e9d0-01 0c Boot
> 2 81920 425984 9695e9d0-02 83
> 3 507904 425984 9695e9d0-03 83
> 4 933888 262144 9695e9d0-04 83
> u-boot=\> mmc dev
> switch to partitions #0, OK
> mmc1(part 0) is current device
What should I do now please help,
I need to flash the eMMC
[EDIT1]
I have a guess here: mmc1(part 0) is current device
I think it’s coorectly pointing to mmc1 which is the eMMC but part0, it needs to point to part1 which is the boot
[EDIT2]
I tried to switch to part 1 with:
> u-boot=\> mmc dev 1 1
> switch to partitions #1, OK
> mmc1(part 1) is current device
I need to make it permanent, cuz when I try to boot after the edit, it return to part 0
[EDIT3]
I followed the serial output when flashing the eMMC , and this is what is shown at the end:
> …
> downloading of 1418832 bytes finished
> writing to partition ‘bootloader’
> support sparse flash partition for bootloader
> Initializing ‘bootloader’
> switch to partitions #1, OK
> mmc1(part 1) is current device
> Writing ‘bootloader’
>
> MMC write: dev # 1, block # 66, count 2772 … 2772 blocks written: OK
> Writing ‘bootloader’ DONE!
You see it : **mmc1(part 1) is current device**
But when I boot it still looking : mmc1(part 0)
---
### Author:  [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [November 18, 2019, 2:08pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/9 "2019-11-18T14:08:49Z")
Yes, so MMC device 1 is indeed the eMMC. I’ve never worked on this specific board so I can’t add much more. What is the mechanism you are using to write the UBoot?
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 18, 2019, 2:19pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/10 "2019-11-18T14:19:31Z")
I’m using iMX8 Mini board
And to flash the eMMC I’m usiing UUU(Universal Update Utility) from NXP official
And in order to flash the eMMC I need to give it two arguments : uboot + .sdimg
And to flash the SD card I only need the sdimg because it’s having the uboot inside.
So for the SDK it’s okay,
The eMMC is flashed but can’t boot, I need to tell the U-boot to boot from dev1 part 1
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 19, 2019, 8:36am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/11 "2019-11-19T08:36:34Z")
> [@bhstalel](#):
>
> \*\* Unable to read file boot.scr \*\*
Please halt U-Boot and share the output of the following:
```auto
run mender_setup
print bootargs
print bootcmd
```
Also can you please share the content of your `local.conf` file.
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 19, 2019, 9:09am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/12 "2019-11-19T09:09:00Z")
Hello,
This is the output :
> u-boot=\> run mender\_setup
> u-boot=\> print bootargs
> bootargs=console=ttymxc1,115200 earlycon=ec\_imx6q,0x30890000,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp
> u-boot=\> print bootcmd
> bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else run mender\_setup; if run loadimage; then run mmcboot; run mender\_try\_to\_recover; else run mender\_try\_to\_recover; run netboot; fi; fii
> u-boot=\>
My local.conf : Same as the demo one: (removing the comments)
> 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"
> PREFERRED\_PROVIDER\_u-boot = “u-boot-imx”
> IMAGE\_CLASSES += “mender-setup-imx”
>
> MENDER\_STORAGE\_DEVICE\_imx8mmevk = “/dev/mmcblk0” (my machine is imx8mmevk)
> MENDER\_STORAGE\_DEVICE\_imx8mqevk = “/dev/mmcblk1”
[EDIT1]
I made the ```
MENDER\_IMAGE\_BOOTLOADER\_FILE to empty string as you told me
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 19, 2019, 11:37am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/13 "2019-11-19T11:37:22Z")
Also can you share the output of
```auto
run mender_setup
printenv
```
as well. That way I will get everything 🙂
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 19, 2019, 11:45am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/14 "2019-11-19T11:45:39Z")
> [@bhstalel](#):
>
> MENDER\_STORAGE\_DEVICE\_imx8mmevk = “/dev/mmcblk0”
Though I think your configuration needs to be,
```auto
MENDER_STORAGE_DEVICE_imx8mmevk = “/dev/mmcblk1”
```
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 19, 2019, 11:46am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/15 "2019-11-19T11:46:35Z")
I will create the image with mmcblk1 now , and I will give you the output,
Reminder: I’m still setting the MENDER\_IMAGE\_BOOTLOADER\_FILE to empty file
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 19, 2019, 11:58am UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/16 "2019-11-19T11:58:06Z")
Here’s the output :
> u-boot=\> run mender\_setup
> Saving Environment to MMC… Writing to redundant MMC(1)… OK
> u-boot=\> printenv
> altbootcmd=run mender\_altbootcmd; run bootcmd
> baudrate=115200
> boot\_fdt=try
> bootargs=
> bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else run mender\_setup; if run loadimage; then run mmcboot; run mender\_try\_to\_recover; else runi
> bootcmd\_mfg=run mfgtool\_args;if iminfo ${initrd\_addr}; then if test ${tee} = yes; then bootm ${tee\_addr} ${initrd\_addr} ${fdt\_addr}; else booti ${loadaddr} ${initrd\_addr} ${fdt\_addr}; f;
> bootcount=1
> bootdelay=2
> bootlimit=1
> bootscript=echo Running bootscript from mmc …; source
> console=ttymxc1,115200 earlycon=ec\_imx6q,0x30890000,115200
> emmc\_dev=1
> ethaddr=00:04:9f:05:fa:dc
> ethprime=FEC
> fastboot\_dev=mmc1
> fdt\_addr=0x43000000
> fdt\_file=boot/fsl-imx8mm-evk.dtb
> fdt\_high=0xffffffffffffffff
> fdtcontroladdr=bc906500
> image=boot/Image
> initrd\_addr=0x43800000
> initrd\_high=0xffffffffffffffff
> jh\_clk=
> jh\_mmcboot=mw 0x303d0518 0xff; setenv fdt\_file fsl-imx8mm-evk-root.dtb;setenv jh\_clk clk\_ignore\_unused; if run loadimage; then run mmcboot; else run jh\_netboot; fi;
> jh\_netboot=mw 0x303d0518 0xff; setenv fdt\_file fsl-imx8mm-evk-root.dtb; setenv jh\_clk clk\_ignore\_unused; run netboot;
> kboot=booti
> loadaddr=0x40480000
> loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
> loadfdt=ext4load ${mender\_uboot\_root} ${fdt\_addr} ${fdt\_file}
> loadimage=ext4load ${mender\_uboot\_root} ${loadaddr} ${image}
> mender\_altbootcmd=if test ${mender\_boot\_part} = 2; then setenv mender\_boot\_part 3; setenv mender\_boot\_part\_hex 3; else setenv mender\_boot\_part 2; setenv mender\_boot\_part\_hex 2; fi; setep
> mender\_boot\_kernel\_type=booti
> mender\_boot\_part=2
> mender\_boot\_part\_hex=2
> mender\_boot\_part\_name=/dev/mmcblk1p2
> mender\_check\_saveenv\_canary=1
> mender\_dtb\_name=fsl-imx8mm-evk-inmate.dtb
> mender\_kernel\_name=Image
> mender\_kernel\_root=/dev/mmcblk1p2
> mender\_kernel\_root\_name=/dev/mmcblk1p2
> mender\_saveenv\_canary=1
> mender\_setup=if test “${mender\_saveenv\_canary}” != “1”; then setenv mender\_saveenv\_canary 1; saveenv; fi; if test “${mender\_pre\_setup\_commands}” != “”; then run mender\_pre\_setup\_commandi
> mender\_try\_to\_recover=if test ${upgrade\_available} = 1; then reset; fi
> mender\_uboot\_boot=mmc 0:1
> mender\_uboot\_dev=0
> mender\_uboot\_if=mmc
> mender\_uboot\_root=mmc 0:2
> mender\_uboot\_root\_name=/dev/mmcblk1p2
> mfgtool\_args=setenv bootargs console=${console},${baudrate} rdinit=/linuxrc clk\_ignore\_unused
> mmcargs=setenv bootargs ${jh\_clk} console=${console} root=${mender\_kernel\_root}
> mmcautodetect=yes
> mmcboot=echo Booting from mmc …; run mmcargs; if test ${boot\_fdt} = yes || test ${boot\_fdt} = try; then if run loadfdt; then booti ${loadaddr} - ${fdt\_addr}; else echo WARN: Cannot lo;
> mmcdev=1
> mmcpart=1
> mmcroot=/dev/mmcblk2p2 rootwait rw
> netargs=setenv bootargs ${jh\_clk} console=${console} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
> netboot=echo Booting from net …; run netargs; if test ${ip\_dyn} = yes; then setenv get\_cmd dhcp; else setenv get\_cmd tftp; fi; ${get\_cmd} ${loadaddr} ${image}; if test ${boot\_fdt} = ;
> script=boot.scr
> sd\_dev=0
> soc\_type=imx8mm
> upgrade\_available=0
>
> Environment size: 4121/4091 bytes
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 19, 2019, 12:12pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/17 "2019-11-19T12:12:14Z")
> [@bhstalel](#):
>
> ext4load {mender\_uboot\_root} {loadaddr} {image}
Can you test running:
```auto
ext4load mmc 0:2 {loadaddr} {image}
ext4load mmc 1:2 {loadaddr} {image}
```
And let me know which of these work?
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 19, 2019, 12:15pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/18 "2019-11-19T12:15:37Z")
Also what does the following produce,
```auto
bitbake -e | grep ^MENDER_UBOOT_STORAGE_DEVICE
```
---
### Author:  [@bhstalel](https://hub.mender.io/u/bhstalel)
#### Post date: [November 19, 2019, 12:17pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/19 "2019-11-19T12:17:33Z")
> u-boot=\> ext4load mmc 0:2 {loadaddr} {image}
> Card did not respond to voltage select!
> \*\* Bad device mmc 0 \*\*
>
> u-boot=\> ext4load mmc 1:2 {loadaddr} {image}
> ext4load - load binary file from a Ext4 filesystem
>
> Usage:
> ext4load [\ [addr [filename [bytes [pos]]]]]
> - load binary file ‘filename’ from ‘dev’ on ‘interface’
> to address ‘addr’ from ext4 filesystem
bitbake core-image-minimal -e | grep ^MENDER\_UBOOT\_STORAGE\_DEVICE
MENDER\_UBOOT\_STORAGE\_DEVICE=“”
MENDER\_UBOOT\_STORAGE\_DEVICE\_DEFAULT=“”
MENDER\_UBOOT\_STORAGE\_DEVICE\_DEFAULT\_mender-ubi=“dummy”
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [November 19, 2019, 12:21pm UTC](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216/20 "2019-11-19T12:21:44Z")
Sorry it should have been,
```auto
ext4load mmc 0:2 ${loadaddr} ${image}
ext4load mmc 1:2 ${loadaddr} ${image}
```
[Next page](https://hub.mender.io/t/yocto-imx8mmevk-emmc-u-boot-problem/1216.md?page=2)