Problem with boot from eMMC on custom board

Showing results for 
Search instead for 
Did you mean: 

Problem with boot from eMMC on custom board

Contributor III


I burned official example file  u-boot-imx6ull14x14evk_emmc.imx and fsl-image-validation-imx-imx6ul7d.sdcard in my custom board by UUU tool.The command I used: 

./uuu.exe emmc_all u-boot-imx6ull14x14evk_emmc.imx fsl-image-validation-imx-imx6ul7d.sdcard

I powered on board,and the boot process stuck in Starting kernel ,here is uboot message:

U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df (Apr 11 2019 - 13:47:37 +0000)

CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz)
CPU: Commercial temperature grade (0C to 95C) at 32C
Reset cause: POR
Model: Freescale i.MX6 UltraLite 14x14 EVK Board
Board: MX6UL 14x14 EVK
DRAM: 512 MiB
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Failed (-5)
Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc1(part 0) is current device
flash target is MMC:1
Error: ethernet@020b4000 address not set.
No ethernet found.
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
switch to partitions #0, OK
mmc1(part 0) is current device
** Unable to read file boot.scr **
7491560 bytes read in 181 ms (39.5 MiB/s)
Booting from mmc ...
37340 bytes read in 14 ms (2.5 MiB/s)
Kernel image @ 0x80800000 [ 0x000000 - 0x724fe8 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300c1db
ft_system_setup for mx6

Starting kernel ...   **stuck here**

After that,I found it might caused by printk disabled(LINUX KERNEL driver hangs/freeze after handling mapped register - Stack Overflow ).So I modified imx6ul.dtsi and replace pwm1 status from "disabled"  to "okay".

I build core-image-minimal-imx6ulevk.rootfs.sdcard with bitbake,and burned my board again by UUU tool.

But the boot process still hang in Starting kernel.

If I missed something,comment below,please.  

Labels (1)
Tags (3)
0 Kudos
2 Replies

NXP TechSupport
NXP TechSupport

Hi west

"official example file" will not work on custom board as they are built for

nxp reference boards. For custom board images should be rebuilt.

In general for new board recommended first to run ddr test

i.MX6/7 DDR Stress Test Tool V3.00 

then update ddr calibration coefficients in uboot/board/freescale/mx6ul_14x14_evk/imximage.cfg

imximage.cfg\mx6ul_14x14_evk\freescale\board - uboot-imx - i.MX U-Boot 

Best regards

0 Kudos

Contributor III

Hi igor,

Thanks for your reply.

I solved the problem after ddr calibration.

Though I encounter 「Bad Linux ARM zImage magic!」 problem in uboot,but I can deal with it temporarily by boot kernel manual.

Now I can enter Linux kernel.


0 Kudos