AnsweredAssumed Answered

Kernel  Stops booting in Starting kernel ...

Question asked by Keshava Kumar B on Jun 24, 2019
Latest reply on Jun 24, 2019 by igorpadykov

I am having Custom i.MX6ULL based board(NAND boot) which is currently having 4.1.15 Kernel . Now I am trying to port Latest NXP community BSP( ). This has following Items :

  1. Yocto Rocko 2.4
  2. Linux Kernel 4.9.88
  3. Uboot 2017.03


My plan is to retain older Uboot and just change Linux kernel and Rootfs. For this I ported My device tree(DTB) , defconfig and board file related to my board. But unfortunately Booting stops in  "Starting kernel ..."


U-Boot 2015.04 (Jun 17 2019 - 16:13:02)

CPU:   Freescale i.MX?? rev1.1 at 396 MHz
CPU:   Temperature 45 C
Reset cause: POR
Boot Device: NAND
I2C:   ready
DRAM:  256 MiB
PMIC: PFUZE300 DEV_ID=0x31 REV_ID=0x11
NAND:  1024 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial

Board Info:
        BSP Version     : iW-PRFYB-SC-01-R1.0-REL1.0-Linux4.1.15
        SOM Version     : iW-PRFYB-AP-01-R1.x
        CPU Unique ID   : 0x453b91d260435a43

Net:   FEC0
Normal Boot
Hit any key to stop autoboot:  0
iWave-G26P> setenv bootcmd 'nand read ${loadaddr} 0xA00000 0x1000000;nand read ${fdt_addr} 0x1A00000 0x1000000;bootz ${loadaddr} - ${fdt_addr}'
iWave-G26P> boot

NAND read: device 0 offset 0xa00000, size 0x1000000
 16777216 bytes read: OK

NAND read: device 0 offset 0x1a00000, size 0x1000000
 16777216 bytes read: OK
Kernel image @ 0x80800000 [ 0x000000 - 0x49ecf0 ]
## Flattened Device Tree blob at 83000000
   Booting using the fdt blob at 0x83000000
   Using Device Tree in place at 83000000, end 8300ab09

Starting kernel ...



I have Few doubts here.  I am using older version of Uboot

  1. Whether using Older version of Uboot is OK?
  2. How can I debug more on "Starting kernel ..." .


Thanks in Advance.

Keshava Kumar B