we can't boot with emmc 4.5

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

we can't boot with emmc 4.5

3,133 Views
seyoungkim
Contributor II

Hi everyone.

We can't boot with emmc 4.5 on my custom board.

before our Micron emmc(4G) was no problem and worked perfectly.

Since after old one has been discontinued. we need to change emmc to hynix

I have been digging about this for 1 month...  however I'v been still stuck this.

we use i.mx6ull and hynix emmc 4g (H26M31001HPR) 

EMMC 5.0 and EMMC 5.1 work on i.MX6 

i'v read already this.

but our kernel is 4.1.15_2.0.0 version. so the source code is quite different between here.

and we changed boot_cfg thousand of times. :-(

here is our boot log when i tried burn with MFGTOOL

//--------------------------------------------------------------------------------------------------------------------//

U-Boot 2016.03-imx_v2016.03_4.1.15_2.0.0_ga+g0ec2a01 (Mar 26 2018 - 12:40:47 +0900)

CPU: Freescale i.MX6ULL rev1.1 at 396MHz
CPU: Commercial temperature grade (0C to 95C) at 43C
Reset cause: POR
Board: MX6ULL 14x14 EVK
I2C: ready
DRAM: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

Display: TFT43AB (800x480)
Video: 800x480x24
In: serial
Out: serial
Err: serial
switch to partitions #0, OK

   :

   :

imx2-wdt 20bc000.wdog: use WDOG_B to reboot.
imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
/soc/aips-bus@02100000/usdhc@02190000: voltage-ranges unspecified
sdhci-esdhc-imx 2190000.usdhc: Got CD GPIO
sdhci-esdhc-imx 2190000.usdhc: No vqmmc regulator found
mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
/soc/aips-bus@02100000/usdhc@02194000: voltage-ranges unspecified
g_mass_storage gadget: high-speed config #1: Linux File-Backed Storage
sdhci-esdhc-imx 2194000.usdhc: No vmmc regulator found
sdhci-esdhc-imx 2194000.usdhc: No vqmmc regulator found
mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Key type dns_resolver registered
cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
Registering SWP/SWPB emulation handler
snvs_rtc 20cc000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01 00:00:00 UTC (0)
mmc1: MAN_BKOPS_EN bit is not set
VSD_3V3: disabling
can-3v3: disabling
clk: Not disabling unused clocks
ALSA device list:
No soundcards found.
Freeing unused kernel memory: 384K (80922000 - 80982000)
Starting UTP
uuc 0.5 [built Sep 16 2016 02:36:sdhci: Tuning procedure failed, falling back to fixed sampling clock
28]
UTP: Waiting for device to ammc1: tuning execution failed
ppear
UTP: file/device node /devmmc1: error -5 whilst initialising MMC card
/utp already exists
cpu_id is 0
UTP: received command 'send'
UTP: sending Success to kernel for command send.
UTP: received command '$ tar xf $FILE '
UTP: executing "tar xf $FILE "
UTP: sending Success to kernel for command $ tar xf $FILE .
mmc1: MAN_BKOPS_EN bit is not set
sdhci: Tuning procedure failed, falling back to fixed sampling clock
mmc1: tuning execution failed
mmc1: error -5 whilst initialising MMC card
utp_poll: pass returned.
UTP: received command '$ sh mksdcard.sh /dev/mmcblk1'
UTP: executing "sh mksdcard.sh /dev/mmcblk1"
mmc1: MAN_BKOPS_EN bit is not set
sdhci: Tuning procedure failed, falling back to fixed sampling clock
mmc1: tuning execution failed
mmc1: error -5 whilst initialising MMC card
mmc1: MAN_BKOPS_EN bit is not set
sdhci: Tuning procedure failed, falling back to fixed sampling clock
mmc1: tuning execution failed
mmc1: error -5 whilst initialising MMC card
“wait for /dev/mmcblk1 appear”
“wait for /dev/mmcblk1 appear”
“wait for /dev/mmcblk1 appear”
“wait for /dev/mmcblk1 appear”

//--------------------------------------------------------------------------------------------------------------------//

Thanks~

Labels (3)
0 Kudos
3 Replies

2,048 Views
igorpadykov
NXP Employee
NXP Employee

Hi seyoung

failures may be caused by drive strength issues, please check similar case on

eMMC 8GB to 4GB - crash on linux (yocto) boot 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

2,048 Views
seyoungkim
Contributor II

Thanks Igor

I checked out what you gave me a solution. 

eMMC 8GB to 4GB - crash on linux (yocto) boot 

But I don't know what i have to do.

The patch "0001-mmc-core-Set-non-default-Drive-Strength-via-platform.patch" seems old kernel version.

As I told you, we use 4.1.15 kernel. 

even I have tried this but source code are quite different between 3.x version.

 

Could you tell me more specific way? 

I'm telling you again, My custom imx6ull board can't boot with hynix emmc chip(ver 4.5 and 4GByte and Not SD Card) in MFGTool 

My another custom board with micron emmc chip is work perfectly and there are no problem to work with mfgtool

 

Best regards

Seyoung

0 Kudos

2,048 Views
igorpadykov
NXP Employee
NXP Employee

Hi Seyoung

one can try to debug it using jtag as described on below link

(check data on 0x907400 )

i.MX6Q NAND boot issues 

You should port changes himself, also NXP has service for helping with porting sw:

NXP Professional Services|NXP 

Best regards
igor

0 Kudos