2009-04-13 13:10:55     Problem when booting Kernel image with JFFS2 root file system

Document created by Aaronwu Employee on Aug 14, 2013
Version 1Show Document
  • View in full screen mode

2009-04-13 13:10:55     Problem when booting Kernel image with JFFS2 root file system

Aymen Abdelwahed (TUNISIA)

Message: 72600   

 

Hi guys, I have a problem when I try to load uClinux Kernel with JFFS2 root file system.

 

I have a BF548 EZKIT Lite board.

First of all, I enabled support for the jFFS2 and mtd-utils package and compiled my uClinux Kernel. I obtained as a result these 2 files : vmImage(1.3MB) AND rootfs.jffs2(4.3MB).

 

After than, I loaded the rootfs.jffs2 using TFTPBOOT and wrote it to my Flash (size:16MB). Finally I loaded vmImage using TFTP and I modifiyed bootargs.

 

When I boot my uClinux (using bootm) I obtain the following error :

 

________________________________

 

## Booting image at 01000000 ...

   Image Name:   Linux-2.6.22.19-ADI-2008R1.5-svn

   Created:      2009-04-12  19:28:02 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    1406859 Bytes =  1.3 MB

   Load Address: 00001000

   Entry Point:  00254000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 254000

Linux version 2.6.22.19-ADI-2008R1.5-svn (aymen@aymen-pc) (gcc version 4.1.2 (AD

I svn)) #17 Sun Apr 12 21:27:56 CEST 2009

early printk enabled on early_BFuart0

Hardware Trace Active and Enabled

Blackfin support (C) 2004-2007 Analog Devices, Inc.

Compiled for ADSP-BF548 Rev 0.0

Warning: Compiled for Rev 0, but running on Rev 2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 525 MHz core clock and 131 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  text      = 0x00001000-0x001b1f10

  rodata    = 0x001b2000-0x002377a4

  data      = 0x00238000-0x00254000

    stack   = 0x00238000-0x0023a000

  init      = 0x00254000-0x0027a000

  bss       = 0x0027a000-0x0028f8f0

  available = 0x0028f8f0-0x03dff000

  DMA Zone  = 0x03e00000-0x04000000

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists.  Total pages: 15748

Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2 earlyprintk=serial,

uart1,57600 console=tty0 console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

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

Console: colour dummy device 80x25

console handover: boot [early_BFuart0] -> real [tty0]

Linux version 2.6.22.19-ADI-2008R1.5-svn (aymen@aymen-pc) (gcc version 4.1.2 (AD

I svn)) #17 Sun Apr 12 21:27:56 CEST 2009

early printk enabled on early_BFuart0

Hardware Trace Active and Enabled

Blackfin support (C) 2004-2007 Analog Devices, Inc.

Compiled for ADSP-BF548 Rev 0.0

Warning: Compiled for Rev 0, but running on Rev 2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 525 MHz core clock and 131 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  text      = 0x00001000-0x001b1f10

  rodata    = 0x001b2000-0x002377a4

  data      = 0x00238000-0x00254000

    stack   = 0x00238000-0x0023a000

  init      = 0x00254000-0x0027a000

  bss       = 0x0027a000-0x0028f8f0

  available = 0x0028f8f0-0x03dff000

  DMA Zone  = 0x03e00000-0x04000000

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists.  Total pages: 15748

Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2 earlyprintk=serial,

uart1,57600 console=tty0 console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

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

Console: colour dummy device 80x25

console handover: boot [early_BFuart0] -> real [tty0]

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

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

Memory available: 60280k/65536k RAM, (152k init code, 1731k kernel code, 735k da

ta, 2048k dma, 588k reserved)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin Data A SRAM: 16 KB (15 KB free)

Blackfin Data B SRAM: 16 KB (16 KB free)

Blackfin Instruction SRAM: 48 KB (42 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

ezkit_init(): registering device resources

SCSI subsystem initialized

NET: Registered protocol family 2

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

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

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

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bf54x-lq043: FrameBuffer initializing...

dma_alloc_init: dma_page @ 0x0036d000 - 512 pages at 0x03e00000

Console: switching to colour frame buffer device 80x24

bfin-otp: initialized

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 48) is a BFIN-UART

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

PPP BSD Compression module registered

PPP MPPE Compression module registered

smsc911x: Driver version 2007-07-13.

register bfin atapi driver

scsi0 : pata-bf54x

ata1: PATA max UDMA/66 cmd 0x00000000 ctl 0xffc03800 bmdma 0x00000000 irq 68

ata1.00: ATA-7: FUJITSU MHW2040AT, 0000000B, max UDMA/100

ata1.00: 78140160 sectors, multi 16: LBA

ata1.00: configured for UDMA/66

blk_queue_max_hw_segments: set to minimum 1

scsi 0:0:0:0: Direct-Access     ATA      FUJITSU MHW2040A 0000 PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO

or FUA

sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO

or FUA

sda: sda1

sd 0:0:0:0: [sda] Attached SCSI disk

physmap platform flash device: 00400000 at 20000000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank

NOR chip too large to fit in mapping. Attempting to cope...

Intel/Sharp Extended Query Table at 0x010A

  Unknown Intel/Sharp Extended Query version 1.5.

gen_probe: No supported Vendor Command Set found

RedBoot partition parsing not available

BF5xx on-chip NAND FLash Controller Driver, Version 1.2 (c) 2007 Analog Devices,

Inc.

bf5xx-nand bf5xx-nand.0: page_size=256, data_width=8, wr_dly=3, rd_dly=3

NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-b

it)

Creating 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":

0x00000000-0x00400000 : "Linux Kernel"

0x00400000-0x10000000 : "File System"

No NAND device found!!!

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, r

egs_base@ffc00500, dma channel@4

bfin-spi bfin-spi.1: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, r

egs_base@ffc02300, dma channel@5

input: bf54x-keys as /class/input/input0

bf54x-keys: Blackfin BF54x Keypad registered IRQ 76

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

i2c /dev entries driver

i2c-bfin-twi i2c-bfin-twi.1: Blackfin BF5xx on-chip I2C TWI Contoller Driver, Ve

rsion 1.8, regs_base@ffc02200

Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50

2006 UTC).

ASoC version 0.13.1

dma rx:0 tx:1, err irq:10, regs:ffc00800

AD1980 SoC Audio Codec

asoc: AC97 <-> bf5xx-ac97 mapping ok

ALSA device list:

  #0: bf5xx-board (AD1980)

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-01-08 05:24:52 (624292)

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00f5295a

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x0000015a

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x000007ff

bf5xx-nand bf5xx-nand.0: syndrome[3] 0x00000000

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x000007ff

bf5xx-nand bf5xx-nand.0: calced[0x000ad6a5], stored[0x00ffffff]

bf5xx-nand bf5xx-nand.0: More than 1-bit error, non-correctable error.

bf5xx-nand bf5xx-nand.0: Please discard data, mark bad block

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00f988ce

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x000000ce

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x000007ff

bf5xx-nand bf5xx-nand.0: syndrome[3] 0x00000000

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x000007ff

bf5xx-nand bf5xx-nand.0: calced[0x00067731], stored[0x00ffffff]

bf5xx-nand bf5xx-nand.0: More than 1-bit error, non-correctable error.

bf5xx-nand bf5xx-nand.0: Please discard data, mark bad block

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x5163 in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0xb02e in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x6337 in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x2c12 in

stead

stead

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0x8766 in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018: 0x4daf in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c: 0xe72a in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020: 0x3c53 in

stead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0x27fe in

stead

Further such events for this erase block will not be printed

Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes

empty_blocks 31, bad_blocks 0, c->nr_blocks 32

VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)

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

0800   39070080 sda driver: sd

  0801   33553027 sda1

1f00       4096 mtdblock0 (driver?)

1f01       4096 mtdblock1 (driver?)

1f02       4096 mtdblock2 (driver?)

1f03     258048 mtdblock3 (driver?)

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

 

________________________

 

Please, help me to solve this problem

 

With my best regards.

 

-Ayman

TranslateQuoteReplyEditDelete

 

 

2009-04-13 17:47:29     Re: Problem when booting Kernel image with JFFS2 root file system

Mike Frysinger (UNITED STATES)

Message: 72609   

 

mtd devices start counting from 0, not 1, and unless i missed something, you only registered two partitions

Attachments

    Outcomes