Yocto fsl-image-gui-sdk build can't make i.MX28 bootup

Showing results for 
Search instead for 
Did you mean: 

Yocto fsl-image-gui-sdk build can't make i.MX28 bootup

Contributor IV


Run dd command

$ sudo dd if=fsl-image-gui-imx28evk-20130417013203.rootfs.sdcard of=/dev/sdf bs=4M

171+0 records in

171+0 records out

717225984 bytes (717 MB) copied, 221.253 s, 3.2 MB/s

And boot from SD0, the system can't boot up, list debug message in blue below. Any idea to find what cause from?

U-Boot 2012.10-00994-g7e6c682 (Apr 17 2013 - 11:04:38)                                

CPU:   Freescale i.MX28 rev1.2 at 454 MHz


I2C:   ready

DRAM:  128 MiB


MMC0: Command 8 timeout (status 0xe0384020)

*** Warning - bad CRC, using default environment


Out:   serial

Err:   serial

Net:   FEC0 [PRIME]

Warning: FEC0 using MAC address from net device

, FEC1

Warning: FEC1 using MAC address from net device

Hit any key to stop autoboot:  0

MMC0: Command 8 timeout (status 0xe02c4020)

reading boot.scr

** Unable to read "boot.scr" from mmc 0:2 **

reading uImage

2590572 bytes read

Booting from mmc ...

reading imx28-evk.dtb

** Unable to read "imx28-evk.dtb" from mmc 0:2 **

## Booting kernel from Legacy Image at 42000000 ...

   Image Name:   Linux-

   Created:  2013-04-17   2:03:22 UTC

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:2590508 Bytes = 2.5 MiB

   Load Address: 40008000

   Entry Point:  40008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK


Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Linux version (thomas@thomas-Linux) (gcc version 4.7.2 (GCC) ) #1 PREEMPT Wed Apr 17 10:03:12 CST 2013

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

CPU: VIVT data cache, VIVT instruction cache

Machine: Freescale MX28EVK board

Memory policy: ECC disabled, Data cache writeback

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512

Kernel command line: console=ttyAMA0,115200 root=/dev/mmcblk0p3 rw rootfstype=ext3 rootwait

PID hash table entries: 512 (order: -1, 2048 bytes)

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 128MB = 128MB total

Memory: 124260k/124260k available, 6812k reserved, 0K highmem

Virtual kernel memory layout:

vector  : 0xffff0000 - 0xffff1000   (   4 kB)
fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
DMA : 0xfde00000 - 0xffe00000   (  32 MB)
vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)
lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
modules : 0xbf000000 - 0xc0000000   (  16 MB)
.init : 0xc0008000 - 0xc0030000   ( 160 kB)
.text : 0xc0030000 - 0xc0503000   (4940 kB)
.data : 0xc0504000 - 0xc0542160   ( 249 kB)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.


Console: colour dummy device 80x30

console [ttyAMA0] enabled

Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)

pid_max: default: 32768 minimum: 301

Security Framework initialized

SELinux:  Initializing.

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

regulator: core version 0.5

NET: Registered protocol family 16

regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal

regulator: vdddbo: 800 <--> 1575 mV fast normal

regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal

vddio = 3380000, val=10

regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal

regulator: overall_current: fast normal

regulator: vbus5v:

regulator: mxs-duart-1: fast normal

regulator: mxs-bl-1: fast normal

regulator: mxs-i2c-1: fast normal

regulator: mmc_ssp-1: fast normal

regulator: mmc_ssp-2: fast normal

regulator: charger-1: fast normal

regulator: power-test-1: fast normal

regulator: cpufreq-1: fast normal

i.MX IRAM pool: 124 KB@0xc8820000

usb DR wakeup device is registered

IMX usb wakeup probe

audit: cannot initialize inotify handle

bio: create slab <bio-0> at 0

SCSI subsystem initialized

Freescale USB OTG Driver loaded, $Revision: 1.55 $

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Advanced Linux Sound Architecture Driver Version 1.0.23.

Switching to clocksource mxs clock source

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 4096 (order: 3, 32768 bytes)

TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

Bus freq driver module loaded

IMX usb wakeup probe

usb h1 wakeup device is registered

audit: initializing netlink socket (disabled)

type=2000 audit(0.490:1): initialized

VFS: Disk quotas dquot_6.5.2

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.

msgmni has been set to 242

alg: No test for stdrng (krng)

cryptodev: driver loaded.

Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Console: switching to colour frame buffer device 100x30

mxs-duart.0: ttyAMA0 at MMIO 0x80074000 (irq = 47) is a DebugUART

mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0

Found APPUART 3.1.0

mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1

Found APPUART 3.1.0

mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2

Found APPUART 3.1.0

mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3

Found APPUART 3.1.0

mxs-auart.4: ttySP4 at MMIO 0x80072000 (irq = 116) is a mxs-auart.4

Found APPUART 3.1.0

brd: module loaded

loop: module loaded


NFC: Version 1, 8-chip GPMI and BCH

gpmi-nfc: probe of gpmi-nfc.0 failed with error 1

mxs-spi mxs-spi.0: Max possible speed 120000 = 120000000/2 kHz

mxs-spi mxs-spi.0: at 0x80014000 mapped to 0xF0014000, irq=84, bus 1, DMA ver_major 4

FEC Ethernet Driver

fec_enet_mii_bus: probed

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci: irq 93, io base 0x80080000

fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.0: irq 92, io base 0x80090000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

ARC USBOTG Device Controller driver (1 August 2005)

mice: PS/2 mouse device common for all mice

input: mxs-kbd as /devices/platform/mxs-kbd.0/input/input0

input: MXS touchscreen as /devices/virtual/input/input1

MXS RTC driver v1.0 hardware v2.3.0

mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

Linux video capture interface: v2.00

mxs-pxp mxs-pxp.0: initialized

mxs watchdog: initialized, heartbeat 19 sec

mxs-mmc: MXS SSP Controller MMC Interface driver

mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96

dcp dcp.0: DCP crypto enabled.!

usbcore: registered new interface driver hiddev

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

mmc0: new high speed SD card at address 0002

mmcblk0: mmc0:0002 N/A   3.67 GiB (ro)

mmcblk0: p1 p2 p3

sgtl5000_hw_read: read reg error : Reg 0x00

Device with ID register 0 is not a SGTL5000

mxs-spdif mxs-spdif.0: MXS SPDIF Audio Transmitter

No device for codec mxs spdif

No device for DAI mxs spdif

No device for DAI mxs-saif

No device for DAI mxs-spdif

asoc: mxs spdif <-> mxs-spdif mapping ok

ALSA device list:

  #0: mxs-evk (mxs spdif)

TCP cubic registered

NET: Registered protocol family 17

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:08 UTC (8)

VFS: Cannot open root device "mmcblk0p3" or unknown-block(179,3)

Please append a correct "root=" boot option; here are the available partitions:

b300     3850240 mmcblk0 driver: mmcblk
  b301        1024 mmcblk0p1
  b302       10240 mmcblk0p2
  b303      684032 mmcblk0p3

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,3)


[<c0034110>] (dump_backtrace+0x0/0x10c) from [<c03ce4ac>] (dump_stack+0x18/0x1c)

r6:c0029a14 r5:c7459000 r4:c0543018 r3:00000002

[<c03ce494>] (dump_stack+0x0/0x1c) from [<c03ce694>] (panic+0x74/0xf0)

[<c03ce620>] (panic+0x0/0xf0) from [<c0008f14>] (mount_block_root+0x1d4/0x218)

r3:00000002 r2:00000001 r1:c7c27f48 r0:c0487dc4

[<c0008d40>] (mount_block_root+0x0/0x218) from [<c0009130>] (mount_root+0xe0/0x124)

[<c0009050>] (mount_root+0x0/0x124) from [<c00092e0>] (prepare_namespace+0x16c/0x1cc)

r5:c0029a29 r4:c0542418

[<c0009174>] (prepare_namespace+0x0/0x1cc) from [<c0008b14>] (kernel_init+0x12c/0x16c)

r5:c0028214 r4:c0028214

[<c00089e8>] (kernel_init+0x0/0x16c) from [<c004e490>] (do_exit+0x0/0x6c0)

r5:c00089e8 r4:00000000

Labels (3)
0 Kudos
4 Replies

NXP TechSupport
NXP TechSupport


      According to above log messages, linux kernel can't find file system. the issue should be from from u-boot environment settings. Are you using u-boot to boot system ?



0 Kudos

Contributor IV

Hi Weidong,

I think so.

After do some reset, it work. So far, also do bitbake fsl-image-gui-sdk. Looks this image effect gui one.

So, fsl-image-gui-sdk have problem, but not fsl-image-gui.

0 Kudos

Specialist I

Hi Thomas/Weidong.

I have also see this issue but not only with gui-sdk images also with gui. After some (hard) resets, kernel finishes booting correctly. OtavioSalvador, I tag you so you are aware of this issue. From my side, I have done any debugging.

Senior Contributor II

It might be several issues. Can you give it a try using upcoming 1.4 release?