topic Re: Stuck up at 'starting kernel' in i.MX Processors

Stuck up at 'starting kernel'

tejummb — Fri, 12 Feb 2016 03:28:13 GMT

Hi Everyone,

We are testing a custom board designed using imx6 dual processor.

We have modified the u-boot and device tree file as per our design. We have the kernel and rootfs on SD card.

We are loading the u-boot using mfgtool.

The code hangs after 'starting kernel'. The log is as follows:

/****************************************************************************************************/

U-Boot 2015.07 (Feb 10 2016 - 12:14:42 +0530)

CPU: Freescale i.MX6D rev1.5 996 MHz (running at 792 MHz)

Reset cause: POR

Board: SABRE Lite

I2C: ready

DRAM: 1 GiB

MMC: FSL_SDHC: 0, FSL_SDHC: 1

SF: Unsupported flash IDs: manuf 00, jedec 0000, ext_jedec 0000

*** Warning - spi_flash_probe() failed, using default environment

auto-detected panel hannstar7

Display: lvds:hannstar7 (1280x800)

In: serial

Out: serial

Err: serial

Net: Phy 4 not found

using phy at 4

PHY reset timed out

FEC [PRIME]

Error: FEC address not set.

, usb_ether

Error: usb_ether address not set.

Hit any key to stop autoboot: 3 2 1 0

AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode

flags: ncq stag pm led clo only pmp pio slum part

No port device detected!

** Bad device size - sata 0 **

SATA device 1: unknown device

** Bad device sata 1 **

switch to partitions #0, OK

mmc0 is current device

reading /6x_bootscript

2933 bytes read in 22 ms (129.9 KiB/s)

## Executing script at 10008000

reading uEnv.txt

** Unable to read file uEnv.txt **

reading /imx6q-sabrelite.dtb

42516 bytes read in 28 ms (1.4 MiB/s)

Setting bus to 1

Error writing the chip: -19

only CEA modes allowed on HDMI port

reading /zImage

4954080 bytes read in 331 ms (14.3 MiB/s)

Kernel image @ 0x10800000 [ 0x000000 - 0x4b97e0 ]

## Flattened Device Tree blob at 13000000

Booting using the fdt blob at 0x13000000

reserving fdt memory region: addr=13000000 size=b000

Using Device Tree in place at 13000000, end 1300dfff

Starting kernel ...

/****************************************************************************************************/

The sd card port is USDHC2.

We have tried following few posts with the same issues, but with no success.

Please let us know the other dependencies for booting kernel image.

Re: Stuck up at 'starting kernel'

Yuri — Fri, 12 Feb 2016 03:51:36 GMT

Hello,

If a board boots u-boot but stops at “Starting kernel ...”, it may be possible to read the

kernel log_buffer. To view memory dump (say in ASCII) at the needed address, assuming

memory still contains log information from the previous boot.

To find the __log_buf address, please use readelf utility :

$ readelf -s vmlinux | grep __log_buf

Then, don’t power off the board, just reset it, and read the

(__log_buf) address on JTAG or u-boot.

Please try it.

Have a great day,
Yuri

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

Re: Stuck up at 'starting kernel'

tejummb — Fri, 12 Feb 2016 04:16:15 GMT

Hi Yuri,

Where do I run this command?

I'm using mfgtool to load the u-boot.

Re: Stuck up at 'starting kernel'

Yuri — Fri, 12 Feb 2016 05:17:50 GMT

Readelf should be run on host Linux, where the kernel was built.

Regards,

Yuri.

Re: Stuck up at 'starting kernel'

tejummb — Wed, 23 Mar 2016 04:39:49 GMT

Hi Yuri,

I apologize for the delay in my response.

Currently, we have updated u-boot and dts files for some minor changes in hardware, and with this setup, we are not even reaching kernel.

The log is as follows:

/********************************************************************************************************************/

U-Boot 2015.07 (Mar 11 2016 - 17:53:03 +0530)

CPU: Freescale i.MX6D rev1.5 996 MHz (running at 792 MHz)

Reset cause: POR

Board: SABRE Lite

I2C: ready

DRAM: 1 GiB

MMC: FSL_SDHC: 0

SF: Unsupported flash IDs: manuf 00, jedec 0000, ext_jedec 0000

*** Warning - spi_flash_probe() failed, using default environment

auto-detected panel hannstar7

Display: lvds:hannstar7 (1280x800)

In: serial

Out: serial

Err: serial

Net: Phy 4 not found

using phy at 4

PHY reset timed out

FEC [PRIME]

Error: FEC address not set.

, usb_ether

Error: usb_ether address not set.

Hit any key to stop autoboot: 3 2 1 0

AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode

flags: ncq stag pm led clo only pmp pio slum part

No port device detected!

** Bad device size - sata 0 **

SATA device 1: unknown device

** Bad device sata 1 **

switch to partitions #0, OK

mmc0 is current device

reading /6x_bootscript

3124 bytes read in 19 ms (160.2 KiB/s)

## Executing script at 10008000

reading uEnv.txt

** Unable to read file uEnv.txt **

reading /imx6q-sabrelite.dtb

37414 bytes read in 22 ms (1.6 MiB/s)

Setting bus to 1

Error writing the chip: -19

only CEA modes allowed on HDMI port

reading /zImage

** Unable to read file /zImage **

Error loading kernel image

MMC Device 1 not found

no mmc device at slot slot slot ::::: 1

MMC Device 1 not found

** Bad device mmc 1 **

starting USB...

USB0: Port not available.

USB1: USB EHCI 1.00

scanning bus 1 for devices... 1 USB Device(s) found

scanning usb for storage devices... 0 Storage Device(s) found

scanning usb for ethernet devices... 0 Ethernet Device(s) found

USB device 0: unknown device

** Bad device usb 0 **

USB device 1: unknown device

** Bad device usb 1 **

6x_bootscript not found

serial console at 115200, 8N1

details at http://boundarydevices.com/6q_bootscript

AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode

flags: ncq stag pm led clo only pmp pio slum part

No port device detected!

AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode

flags: ncq stag pm led clo only pmp pio slum part

No port device detected!

switch to partitions #0, OK

mmc0 is current device

expose mmc 0 over USB

UMS: disk start sector: 0x0, count: 0x1dacc00

|/-\|/-\/-\|/-\/-\|/-\/-\|/-\/-\|/-\/-\|/-\/-\|/-\/-\|/-\/-\|/

/*******************************************************************************************************************/

In the log shown above, the 6x_bootscript and dtb is read, but reading zImage fails.

Sometimes, even reading bootscript/dtb itself gives error.

Kindly, let us know what could be the issue.

Regards,

Teju M M B

Re: Stuck up at 'starting kernel'

Yuri — Wed, 18 May 2016 08:40:17 GMT

Hello,

What is Your procedure to prepare boot device ?

Regards,

Yuri.