eMMC boot fail issue on imx6solo ?

[robinsingh]

Hi All/Kursad/Igor,

I am trying to boot from emmc but there are some issue.  i tried boot tester tool as per this post :

mfgtool gets stuck while loading Android 5.0 onto imx6 board based on SabreSD.

and here are the result, can some body from freescale  give  me some pointer based on this log  , where is it failing ?

===================================================================================

C:\Users\rsingh\Desktop\i.mx6SLSXSDLDQDPQP_rev106>Boot_Tester.exe -t imx -df 6te

st.inc

MX6DL opened.

HAB_TYPE: DEVELOP

Image loading...

download Image to IRAM OK

Re-open imx device.

Running BOOT DEBUG., press "ESC" key to exit.

*********************************************

    Boot Debug (106.1) for MX6DL

    Build: Nov 10 2015, 21:41:50

    Freescale Semiconductor, Inc.

*********************************************

WDOG Fuse Disabled

Boot_cfg_1    = 0x60

Boot_cfg_2    = 0x58

Boot_cfg_3    = 0x00

Boot_cfg_4    = 0x00

SBMR2         = 0x22000001

  BMOD        = 10  Boot from GPIO/Fuses

  BT_FUSE_SEL = 0

  DIR_BT_DIS  = 0

  SEC_CONFIG  = 01

Persistent Reg Value: 0x00000000

iROM Version  = 0x13

USB_ANALOG_DIGPROG = 0x00610003

    Device         = MX6 Solo/Duallite

    Si Revision    = 1.3

Log Entry #0    (0x00010002)  BOOTMODE - Internal/Override

Log Entry #1    (0x000200f0)  Security Mode - Open

Log Entry #2    (0x00030000)  DIR_BT_DIS = 0

Log Entry #3    (0x00040000)  BT_FUSE_SEL = 0

Log Entry #4    (0x00050001)  Secondary Image Selected

Log Entry #5    (0x00060001)  USDHC Boot

Log Entry #6    (0x00070000)  Device INIT Call

Log Entry #7    (0x000700f0)  Device INIT Pass

Log Entry #8    (0x00080000)  Device READ Data Call     Address: 0x00000000

Log Entry #10   (0x000800f0)  Device READ Data Pass

Log Entry #11   (0x00061fff)  Recovery Mode NONE

Log Entry #12   (0x00062001)  MFG Mode USDHC

Log Entry #13   (0x00070000)  Device INIT Call

Log Entry #14   (0x00070033)  Device INIT Fail

Log Entry #15   (0x000c0000)  Serial Downloader Entry

Log Entry #16   (0x00090000)  HAB Authentication Status Code:

                (0x00032233)  Invalid Address

Log Entry #18   (0x000d0000)  Serial Downloader Call

                (0x0091712c)  Address: 0x0091712c

Type 0 to Exit

Type 1 to Read Memory

Type 2 to Write Memory

Type 3 to Read Boot Page

Type 4 to Memory Dump

================================================================

thanks and regards

Robin Singh

[igorpadykov]

Hi robin

error may be caused by incorrect address, which range is defined

in Table 8-41. 16 Byte SDP Command Data Structure and Table 8-33.

Valid DCD Address Ranges i.MX6SDL Reference Manual (rev.2  5/2015)

http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6SDLRM.pdf

In general one can attach JTAG debugger and dump 0x907400 (ROM uses

0x907000 as starting address), you should see your IVT header here if the

eMMC access is ok.

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

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

-----------------------------------------------------------------------------------------------------------------------

[robinsingh]

Hi Igor,

I checked the address 0x907400 and i can see IVT header there from my mfg u-boot.imx. This same image boot via Manufacturing tool and i can bring up the kernel and eMMC , but this same uboot image fails to boot from eMMC.

regarding Valid DCD address All the address i verified via DDR stress test tool , is there any thing other i need to check of valid DCD address. What does the below log means in terms of iROM code.

=====================================================

Log Entry #12   (0x00062001)  MFG Mode USDHC

Log Entry #14   (0x00070033)  Device INIT Fail

Log Entry #16   (0x00090000)  HAB Authentication Status Code:

                (0x00032233)  Invalid Address

=====================================================

any other check point ?

Thanks

Robin

[igorpadykov]

Hi Robin

what eMMC revision are you using ?

Just for test please try rev.4.41 which officially supported.

~igor

[robinsingh · Accepted solution]

Hi igor,

We fixed it , it was a POR issue , PMIC was not generating POR with proper timing , a extended (more then 1 sec long ) POR is required for Imx6 to boot. it might be a issue from Free scale side , Igor have you seen this issue for other customer ? what was the final solution ?

thanks

Robin Singh

[alfred_liu]

Hi, robinsingh​

are you trying to boot with DDR mode?

if so,

could you dump out the register value for uSDHCx_DLL_CTRL (the boot port, SD3 or other?)?

[robinsingh]

Hi Alfred1z

I am not working in DDR mode . we are using SDHC4 port with below config:

Boot_cfg_1    = 0x60

Boot_cfg_2    = 0x58

Boot_cfg_3    = 0x00

Boot_cfg_4    = 0x00

DLLCTRL register value in uboot

uSDHCx_DLL_CTRL= 0x00 ( default , we are not changing it ).  do i need to change this ? any suggestion

Thanks

Robin

[alfred_liu]

Hi, robinsingh​

if you make sure you are NOT boot from eMMC with DDR mode. (then it's SDR mode).

and the uSDHC4_CTRL value reading from the register is 0x00.

you can ignore my input here.

please continue getting help from those guys here.