boot stop at "starting kernel..."

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

boot stop at "starting kernel..."

1,013 Views
guochgz
Contributor III

hello.

      on my iMX6ULL board, system boot stops at "starting kernel...". However, if enter uboot cmd, and run the "boot" command, we can successfully boot into kernel, what's the reason of this phenomenon? 

system boot log:

U-Boot 2016.03-imx_v2016.03_4.1.15_2.0.0_ga+ga57b13b (Aug 23 2019 - 16:12:38 +0800)

CPU: Freescale i.MX6ULL rev1.1 69 MHz (running at 396 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 39C
Reset cause: POR
Board: MX6ULL 14x14 EVK
I2C: ready
DRAM: 256 MiB
force_idle_bus: sda=0 scl=0 sda.gp=0x1d scl.gp=0x1c
force_idle_bus: failed to clear bus, sda=0 scl=0
NAND: 128 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
Net: FEC1
Error: FEC1 address not set.

Normal Boot
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x1000000, size 0x800000
8388608 bytes read: OK

NAND read: device 0 offset 0x2000000, size 0x100000
1048576 bytes read: OK
Kernel image @ 0x80800000 [ 0x000000 - 0x65cbe8 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300b918

Starting kernel ...

enter uboot cmdline, and running boot command log:

DRAM: 256 MiB
force_idle_bus: sda=0 scl=0 sda.gp=0x1d scl.gp=0x1c
force_idle_bus: failed to clear bus, sda=0 scl=0
NAND: 128 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
Net: FEC1
Error: FEC1 address not set.

Normal Boot
Hit any key to stop autoboot: 0
=> boot

NAND read: device 0 offset 0x1000000, size 0x800000
8388608 bytes read: OK

NAND read: device 0 offset 0x2000000, size 0x100000
1048576 bytes read: OK
Kernel image @ 0x80800000 [ 0x000000 - 0x65cbe8 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300b918

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.1.15+g30278ab (gczhang@ubuntu-VBox) (gcc version 7.3.0 (GCC) ) #93 SMP PREEMPT Fri Aug 23 15:49:26 CST 2019
CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Freescale i.MX6 ULL 14x14 EVK Board
Reserved memory: failed to allocate memory for node 'linux,cma'
Memory policy: Data cache writealloc
PERCPU: Embedded 12 pages/cpu @8fdd4000 s16908 r8192 d24052 u49152

...

Labels (3)
0 Kudos
2 Replies

834 Views
igorpadykov
NXP Employee
NXP Employee

Hi 国承 张

such behaviour may be caused by incorrect ddr configuration, one can try

to run ddr test https://community.nxp.com/docs/DOC-105652 

and update image with new calibration coefficients found from ddr test.

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

0 Kudos

834 Views
guochgz
Contributor III

I have fixed this issue by just disable DCACHE function.

DDR calibration config have be update to imx6image.cfg

0 Kudos