Cannot flash custom images to eMMC using UUU Tool (i.MX8M Mini EVK)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cannot flash custom images to eMMC using UUU Tool (i.MX8M Mini EVK)

1,812 Views
mahesh_rd
Contributor I

Hi,

We are currently working on developing a custom board using the i.MX8M Mini Processor. We have procured a i.MX8M Mini EVK for prototyping. Using the Yocto Project, I have made a custom layer and have made changes to device trees and kernel in that layer and have successfully managed to generate a SDCARD image. This SDCARD image works perfectly So far, so good. But when I generate an eMMC image using Yocto, and I try to flash the same image onto the board using UUU tool, I get the following error.

U-Boot SPL 2018.03-4.14.98-2.2.0+g73af2fc (Mar 10 2020 - 12:37:16 +0000)
power_bd71837_init
DDRINFO: start DRAM init
DRAM PHY training for 3000MTS
check ddr_pmu_train_imem code
check ddr_pmu_train_imem code pass
check ddr_pmu_train_dmem code
check ddr_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 400MTS
check ddr_pmu_train_imem code
check ddr_pmu_train_imem code pass
check ddr_pmu_train_dmem code
check ddr_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 100MTS
check ddr_pmu_train_imem code
check ddr_pmu_train_imem code pass
check ddr_pmu_train_dmem code
check ddr_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 3000MTS
check ddr_pmu_train_imem code
check ddr_pmu_train_imem code pass
check ddr_pmu_train_dmem code
check ddr_pmu_train_dmem code pass
Training PASS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...
Downloading file of size 1231560 to 0x40400000... done
Jumping to header at 0x40400000
Header Tag is not an IMX image
Found header at 0x4042b400


U-Boot 2018.03-4.14.98-2.2.0+g73af2fc (Mar 10 2020 - 12:37:16 +0000)

CPU:   Freescale i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 44C
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... Card did not respond to voltage select!
*** Warning - No block device, 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 1355c5d
  - U-Boot 2018.03-4.14.98-2.2.0+g73af2fc

Card did not respond to voltage select!
Detect USB boot. Will enter fastboot mode!
Net:   
Warning: ethernet@30be0000 using MAC address from ROM
eth0: ethernet@30be0000
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for                  mfgtools
Run 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}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
Hit any key to stop autoboot:  0

## Checking Image at 43800000 ...
Unknown image format!
Run fastboot ...
g_dnl_register: failed!, error: -19
u-boot=>

I get "g_dnl_register: failed!, error:-19" and "card did not respond to voltage select!"  errors.

When I tried flashing the demo images provided by NXP, there was no such problem. It only happens with my custom image. I have attached the files which I have used. Can anyone please help me with this?

I have used

sudo ./uuu -b emmc imx-boot-imx8dfmc-emmc.bin-flash_evk

to flash only the bootlader to emmc.

Regards,

Mahesh R Devadia

0 Kudos
3 Replies

1,583 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

 

Regarding uboot you may use the same image for both SD and eMMC, since SD boot can be flashed in eMMC for boot from eMMC instead of an SD card.

Just make sure to have added uSDHC3 to your device tree so it doesn't fail to initialize it.

 

Hope this helps,

Best regards,

Aldo.

0 Kudos

1,583 Views
mahesh_rd
Contributor I

Hey Aldo, Can you kindly please respond to my reply?

0 Kudos

1,583 Views
mahesh_rd
Contributor I

Hi Aldo,

I have checked the device tree files in both u-boot and the linux-kerenel. Both have uSDHC3 enabled. I still get this error. I am now going to check with SDCard image and post an update in this thread.

 fsl-imx8mm-evk.dts(Linux Kernel device tree)

&usdhc3 {
    pinctrl-names = "default", "state_100mhz", "state_200mhz";
    pinctrl-0 = <&pinctrl_usdhc3>;
    pinctrl-1 = <&pinctrl_usdhc3_100mhz>;
    pinctrl-2 = <&pinctrl_usdhc3_200mhz>;
    bus-width = <8>;
    non-removable;
    status = "okay";
};

fsl-imx8mm-evk.dts (u-Boot device tree)

&usdhc3 {
    pinctrl-names = "default", "state_100mhz", "state_200mhz";
    pinctrl-0 = <&pinctrl_usdhc3>;
    pinctrl-1 = <&pinctrl_usdhc3_100mhz>;
    pinctrl-2 = <&pinctrl_usdhc3_200mhz>;
    bus-width = <8>;
    non-removable;
    status = "okay";
};

 

0 Kudos