i.MX Processors中的主题 Re: Loading Yocto Environment from MMC issue

Loading Yocto Environment from MMC issue

shai_b — Thu, 26 Aug 2021 14:39:50 GMT

Dear team,

My customer has built a custom image for imx8mm and when he tried to load his custom image into eMMC he getting the following error (find uboot log below):

CPU: Commercial temperature grade (0C to 95C) at 70C
Reset cause: POR
Model: FSL i.MX8MM EVK board
DRAM: 2 GiB
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 1cb68fa
- U-Boot 2018.03-imx_v2018.03_4.14.98_2.0.0_ga+g87a19df
Card did not respond to voltage select!
Detect USB boot. Will enter fastboot mode!
Net:
Error: ethernet@30be0000 address not set.
No ethernet found.
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

BTW, when the customer tied to load his image using an SD card and the image has loaded successfully.

the attached is the customer device tree

Could you please advise what could be the issue and how to resolve it, Thanks in advance

Kind regards,

Shai

Re: Loading Yocto Environment from MMC issue

nxf63675 — Tue, 31 Aug 2021 18:42:18 GMT

Hi @shai_b,

The problem is that the eMMC is not responding to the selected voltage, usually is because the memory uses a different work voltage than the one you are using, one could try to move the BOOT_CFG[1] that change the operating eMMC voltage.

Other stuff that probably is causing this and we could try:

1. reason may be poor soldering, one can resolder eMMC or change from a known good board.

2. one can debug it using an oscilloscope or digital analyzer and sect.7.4.2 Operating voltage range validation eMMC specification:

http://yourcmc.ru/wiki/images/5/55/EMMC_JESD84-A441.pdf

https://community.nxp.com/thread/341480

If there is something more I can do for you, please let me know.

Regards,

Israel.

Re: Loading Yocto Environment from MMC issue

shai_b — Wed, 01 Sep 2021 07:35:49 GMT

Hi @nxf63675 (Israel),

I want to let you know the customer is using NXP imx8mm EVK, when the customer tried to use NXP's image file, everything works well.

But once the customer tries to use his own custom image he got the emmc error.

so I do not believe it could be a soldering issue, what could be the issue?

maybe misconfiguration of the image file addresses could lead to the same issue?

Your fast responses will be highly appreciated

Kind regards,

Shai

Re: Loading Yocto Environment from MMC issue

BiyongSUN — Wed, 01 Sep 2021 11:38:27 GMT

g_dnl_register: failed!, error: -19

The log should check the usb device issue if it matches the customer board hardware.

The bsp for i.MX8MM is enable typeC(CONFIG_USB_TCPC ) in u-boot.

CONFIG_FASTBOOT_USB_DEV is for the usb device index. and don't which BSP version you are using. the old version could not auto detect and need to configure it.

for emmc voltage, if you read the spec, the emmc io 1.8v could work for high speed and legacy speed both. So far, it is not emmc issue.

emmc is not sdcard, sdcard has voltage select when init. and emmc and sdcard belong to different spec.

This is from emmc jedec spec, emmc io could be 1.8v for all speed.

you can double check the hardware mmc io is 1.8v or 3.3v or add no-1-8-v to the device tree(linux\Documentation\devicetree\bindings\mmc\mmc.txt) to try.

and you can boot from sdcard, when you get into linux.

you can check in the /sys fs.

you need to check the usb first if has typeC or not.