AnsweredAssumed Answered

kernel 2.6.35 on imx233: boot problem

Question asked by Alberto Biancalana on Mar 29, 2013
Latest reply on Oct 23, 2013 by Alberto Biancalana

Hi, i'm trying to move from imx233 2.6.31 environment to 2.6.35 kernel by using ltib for mx28 configured for imx233.

Just trying to launch linux on my custom board, where the 2.6.31 kernel runs since some months.

Now on ltib I've set ub a basic 2.6.35 kernel for mx233 to load on the card and I've a bad problem as you can see at the end of the attached log.


I'm using the same boot command I used for 2.6.31:

     noinitrd console=ttyAM0,115200 ubi.mtd=1 root=ubi0:rootfs0 rootfstype=ubifs rw ip=none gpmi

which worked perfectly with 2.6.31 kernel and now I'm not able to understand what's happening.

The boot log for is almost identical, no problem to see the NAND flash, so the problem is ubi, pheraps.


Could anyone give me indications about this problem?






PowerPrep start initialize power...

Battery Voltage = 4.09V

boot from battery. 5v input not detected

LLCMar 28 201321:14:34

EMI_CTRL 0x1C084040

FRAC 0x92926192


power 0x00820710

Frac 0x92926192

start change cpu freq

hbus 0x00000003

cpu 0x00010001



done, booting the kernel.

Linux version (clc@ubuntu) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #5 PREEMPT Thu Mar 28 21:07:09 CET 2013

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

CPU: VIVT data cache, VIVT instruction cache

Machine: Freescale MX23EVK board

Memory policy: ECC disabled, Data cache writeback

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

Kernel command line: -e noinitrd console=ttyAM0,115200 ubi.mtd=1 root=ubi0:rootfs0 rootfstype=ubifs rw ip=none gpmi

PID hash table entries: 256 (order: -2, 1024 bytes)

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

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory: 64MB = 64MB total

Memory: 57372k/57372k available, 8164k reserved, 0K highmem



Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xfde00000 - 0xffe00000   (  32 MB)

    vmalloc : 0xc4800000 - 0xf0000000   ( 696 MB)

    lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)

    modules : 0xbf000000 - 0xc0000000   (  16 MB)

      .init : 0xc0008000 - 0xc0024000   ( 112 kB)

      .text : 0xc0024000 - 0xc0322000   (3064 kB)

      .data : 0xc0334000 - 0xc0359980   ( 151 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 [ttyAM0] enabled

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

pid_max: default: 32768 minimum: 301

Security Framework initialized

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

regulator: core version 0.5

NET: Registered protocol family 16

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

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

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

regulator: vddio: 2800 <--> 3575 mV at 3300 mV fast normal

regulator: overall_current: fast normal

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: 28 KB@0xc4808000

bio: create slab <bio-0> at 0

SCSI subsystem initialized

Switching to clocksource mxs clock source

NET: Registered protocol family 1

Trying to unpack rootfs image as initramfs...

rootfs image is not initramfs (junk in compressed archive); looks like an initrd

Freeing initrd memory: 4096K

Bus freq driver module loaded

mxs_cpu_init: cpufreq init finished

msgmni has been set to 120

alg: No test for stdrng (krng)

cryptodev: driver loaded.

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Console: switching to colour frame buffer device 30x40

mxs-duart.0: ttyAM0 at MMIO 0x80070000 (irq = 0) is a DebugUART

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

Found APPUART 3.0.0

brd: module loaded

loop: module loaded


NFC: Version 0, 4-chip GPMI and BCH

Boot ROM: Version 0, Single/dual-chip boot area, no block mark swapping

Scanning for NAND Flash chips...

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)


NAND Flash Device Information


Manufacturer      : Samsung (0xec)

Device Code       : 0xd3

Cell Technology   : MLC

Chip Size         : 1 GiB

Pages per Block   : 128

Page Geometry     : 2048+64

ECC Strength      : 4 bits

ECC Size          : 512 B

Data Setup Time   : 20 ns

Data Hold Time    : 15 ns

Address Setup Time: 20 ns

GPMI Sample Delay : 6 ns

tREA              : Unknown

tRLOH             : Unknown

tRHOH             : Unknown

Description       : K9G8G08U0M, K9HAG08U1M


Physical Geometry


Chip Count             : 1

Page Data Size in Bytes: 2048 (0x800)

Page OOB Size in Bytes : 64

Block Size in Bytes    : 262144 (0x40000)

Block Size in Pages    : 128 (0x80)

Chip Size in Bytes     : 1073741824 (0x40000000)

Chip Size in Pages     : 524288 (0x80000)

Chip Size in Blocks    : 4096 (0x1000)

Medium Size in Bytes   : 1073741824 (0x40000000)


NFC Geometry


ECC Algorithm          : BCH

ECC Strength           : 8

Page Size in Bytes     : 2112

Metadata Size in Bytes : 10

ECC Chunk Size in Bytes: 512

ECC Chunk Count        : 4

Payload Size in Bytes  : 2048

Auxiliary Size in Bytes: 16

Auxiliary Status Offset: 12

Block Mark Byte Offset : 0

Block Mark Bit Offset  : 0


Boot ROM Geometry


Boot Area Count            : 1

Boot Area Size in Bytes    : 41943040 (0x2800000)

Stride Size in Pages       : 64

Search Area Stride Exponent: 2

Scanning for an NCB fingerprint...

  Looking for a fingerprint in page 0x0

  Found a fingerprint

Scanning device for bad blocks

Boot area protection is enabled.

Creating 2 MTD partitions on "gpmi-nfc-main":

0x000000000000-0x000002800000 : "gpmi-nfc-0-boot"

0x000002800000-0x000040000000 : "gpmi-nfc-general-use"

UBI: attaching mtd1 to ubi0

UBI: physical eraseblock size:   262144 bytes (256 KiB)

UBI: logical eraseblock size:    258048 bytes

UBI: smallest flash I/O unit:    2048

UBI: VID header offset:          2048 (aligned 2048)

UBI: data offset:                4096

UBI: attached mtd1 to ubi0

UBI: MTD device name:            "gpmi-nfc-general-use"

UBI: MTD device size:            984 MiB

UBI: number of good PEBs:        3936

UBI: number of bad PEBs:         0

UBI: max. allowed volumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     2

UBI: available PEBs:             39

UBI: total number of reserved PEBs: 3897

UBI: number of PEBs reserved for bad PEB handling: 39

UBI: max/mean erase counter: 3/1

UBI: image sequence number: 0

UBI: background thread "ubi_bgt0d" started, PID 372

mice: PS/2 mouse device common for all mice

input: mxs-kbd as /class/input/input0

MXS RTC driver v1.0 hardware v2.0.0

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

i2c /dev entries driver

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: MMC HW configuration failed

mxs-mmc: probe of mxs-mmc.0 failed with error -16

dcp dcp.0: DCP crypto enabled.!

NET: Registered protocol family 17

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

VFS: Cannot open root device "ubi0:rootfs0" or unknown-block(0,0)

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

1f00           40960 mtdblock0 (driver?)

1f01         1007616 mtdblock1 (driver?)

1f02          262332 mtdblock2 (driver?)

1f03          708876 mtdblock3 (driver?)

fe00          262332 ubiblka (driver?)

fe08          708876 ubiblkb (driver?)

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