u-boot issue it will stuck at starting kernel

cancel
Showing results for 
Search instead for 
Did you mean: 

u-boot issue it will stuck at starting kernel

Jump to solution
2,317 Views
Contributor IV

Hi Community,

I'm working on iMX6 Quad sabre-SD platform and build my image with android_M6.0.1_2.1.0_source.

Here is what I can not understand.

When my machine start on u-boot then it stuck at Starting kernel place, below is my u-boot log.

U-Boot 2015.04 (Aug 12 2018 - 18:14:23)

CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 36 C
Reset cause: POR
Board: MX6-SabreSD
I2C: ready
DRAM: 2 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In: serial
Out: serial
Err: serial
check_and_clean: reg 0, flag_set 0
Fastboot: Normal
flash target is MMC:2
Net: FEC [PRIME]
Error: FEC address not set.

Normal Boot
Hit any key to stop autoboot: 0
boota mmc2
kernel @ 14008000 (8723664)
ramdisk @ 15000000 (1028152)
fdt @ 14f00000 (43493)
## Booting Android Image at 0x12000000 ...
Kernel load addr 0x14008000 size 8520 KiB
Kernel command line: console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb2:off video=mxcfb3:off vmalloc=256M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=FX100 cma=384M androidboot.selinux=disabled androidboot.dm_verity=disabled
## Flattened Device Tree blob at 14f00000
Booting using the fdt blob at 0x14f00000
Loading Kernel Image ... OK
Using Device Tree in place at 14f00000, end 14f0d9e4

Starting kernel ...

As you can see it stuck at Staring kernel... and will not keep going down to run kernel image.

I get my u-boot environment via printenv like below log.

Normal Boot
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
bootargs= console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb2:off video=mxcfb3:off vmalloc=256M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=FX100 cma=384M androidboot.selinux=disabled androidboot.dm_verity=disabled
bootcmd=boota mmc2
bootdelay=1
ethact=FEC
ethprime=FEC
fastboot_dev=mmc2
fdt_high=0xffffffff
initrd_high=0xffffffff
loadaddr=0x12000000
splashpos=m,m

Environment size: 492/8188 bytes
=>

I used SD4 to connect my emmc. 

Is there anything I need to mentioned?

How can I fix this problem?

Thanks in Advanced!

Labels (4)
0 Kudos
1 Solution
450 Views
NXP TechSupport
NXP TechSupport

if you hardware design has no PMIC, most probably kernel hangs when trying to

access pmic through i2c, so you can try to debug it.

Best regards
igor

View solution in original post

0 Kudos
5 Replies
450 Views
NXP TechSupport
NXP TechSupport

Hi tsung

was ddr test passed on board

i.MX6/7 DDR Stress Test Tool V2.90 

and new calibration coefficients were updated in file

uboot/../mx6sabresd/mx6q_4x_mt41j128.cfg

For programming images recommended to use

i.MX 6 Series Manufacturing Toolkit for Android M6.0.1_2.1.0 Release

https://www.nxp.com/webapp/Download?colCode=IMX6_M6.0.1_2.1.0_MFG_TOOL&appType=license&location=null... 

For testing purposes one can try linux minimal image using documentation on

i.MX Software|NXP 

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

0 Kudos
450 Views
Contributor IV

Hi igorpadykov

ddr test is running perfect and I had using the parameter in mfgtool firmware also the image.

Also I test mfgtool firmware by using mfgtool to burn it in to my machine and it works fine too.

Mfgtool will show green bar and burning success.

Besides if my ddr test parameter is not right, I think u-boot log will not showing up either.

I could not use  linux minimal image to test because my hardware design has no PMIC on it.

Is there any other possibility that cause this issue?

Or how can I test to now my emmc is still alive or have any dtb and zimage inside?

0 Kudos
451 Views
NXP TechSupport
NXP TechSupport

if you hardware design has no PMIC, most probably kernel hangs when trying to

access pmic through i2c, so you can try to debug it.

Best regards
igor

View solution in original post

0 Kudos
450 Views
Contributor IV

I had found the solution.

My dtsi file has some settings are not correct.

While I correct it my machine can get into kernel.

0 Kudos
450 Views
Contributor I

Usually this problem is your kernel err,mostly your dts file is not matched

0 Kudos