[#4050] xip test case failed in BF548-EZKIT

Question

Accepted Answer

[#4050] xip test case failed in BF548-EZKIT

Submitted By: Vivi Li

Open Date

2008-04-23 00:06:36 Close Date

2008-04-24 04:39:09

Priority:

Medium Assignee:

Bernd Schmidt

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

Category:

N/A Board:

N/A

Processor:

N/A Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Duplicate

Uboot version or rev.:

Toolchain version or rev.:

08r1-rc8

App binary format:

N/A

Summary: xip test case failed in BF548-EZKIT

Details:

xip test case failed in BF548-EZKIT ver1.3 for both fdpic and shared-flat formats.

For BF548-EZKIT ver1.1, xip shared-flat test pass in 08r1 branch. While it still fails for BF548-EZKIT ver1.3 board in 08r1 branch.

And it also fails for BF548-EZKIT ver1.1 board in trunk.

Bellow is the log:

--

U-Boot 1.1.6-svn1095 (ADI-2008R1) (Jan 13 2008 - 04:49:34)^M

^M

CPU: ADSP bf548-0.0 (Detected Rev: 0.1)^M

Board: ADI BF548 EZ-Kit board^M

Support: blackfin.uclinux.org/^M

Clock: VCO: 525 MHz, Core: 525 MHz, System: 131 MHz^M

RAM: 64 MB^M

Flash: 16 MB^M

In: serial^M

Out: serial^M

Err: serial^M

NAND: 256 MiB^M

Net: LAN9x18 (0x118a0000) detected at 0x24000000^M

MAC: 00:E0:22:FE:B8:54^M

I2C: ready^M

Hit any key to stop autoboot: 8 ^H^H^H 0 ^M

bfin> successful reset attemp

set bootargs root=mtd1 rootfstype=romfs ro^M

bfin> save^M

Saving Environment to EEPROM...^M

..done^M

bfin> tftpboot 0x1000000 linux.romfs^M

start Auto negotiation... (take ~2sec)^M

Auto negotiation complete, 100BaseTX, full duplex^M

TFTP from server 10.100.4.174; our IP address is 10.100.4.50^M

Filename 'linux.romfs'.^M

Load address: 0x1000000^M

Loading: *^H#################################################################^M

#################################################################^M

########################^M

done^M

Bytes transferred = 8770649 (85d459 hex)^M

bfin> boote^M

Loading .text @ 0x00001000 (1592560 bytes)^M

Loading .exit.text.refok @ 0x00185cf0 (296 bytes)^M

Loading .rodata @ 0x00185e20 (440420 bytes)^M

Loading __ksymtab @ 0x001f1684 (17592 bytes)^M

Loading __ksymtab_gpl @ 0x001f5b3c (5560 bytes)^M

Loading __ksymtab_strings @ 0x001f70f4 (57184 bytes)^M

Loading __param @ 0x00205054 (1080 bytes)^M

Clearing .bss @ 0x002054a0 (68932 bytes)^M

Loading .data @ 0x002161e4 (106012 bytes)^M

Loading .init.text @ 0x00230000 (132292 bytes)^M

Loading .init.data @ 0x002504c4 (23004 bytes)^M

Loading .init.setup @ 0x00255ea0 (612 bytes)^M

Loading .initcall.init @ 0x00256104 (576 bytes)^M

Loading .con_initcall.init @ 0x00256344 (4 bytes)^M

Loading .init.ramfs @ 0x00256348 (133 bytes)^M

Loading .text_l1 @ 0xffa00000 (5636 bytes)^M

sh_addr: FFA00000, p_paddr: 002563CD^M

Loading from: 01247000 to 002563CD, size: 5636^M

Loading .data_l1 @ 0xff800000 (192 bytes)^M

sh_addr: FF800000, p_paddr: 002579D1^M

Loading from: 01249000 to 002579D1, size: 192^M

Loading .romfs @ 0x00258000 (5658624 bytes)^M

## Starting application at 0x00230000 ...^M

Linux version 2.6.24.4-ADI-2008R2-pre-svn4644 (test@uclinux84-bf548-kernel) (gcc version 4.1.2 (ADI svn)) #15 Wed Apr 23 04:33:35 GMT 2008^M

Board Memory: 64MB^M

Kernel Managed Memory: 64MB^M

Memory map:^M

fixedcode = 0x00000400-0x00000490^M

text = 0x00001000-0x00185cf0^M

rodata = 0x00185e20-0x0020548c^M

bss = 0x002054a0-0x002161e4^M

data = 0x002161e4-0x00230000^M

stack = 0x0022e000-0x00230000^M

init = 0x00230000-0x00258000^M

available = 0x00258000-0x0389a000^M

rootfs = 0x0389a000-0x03e00000^M

DMA Zone = 0x03e00000-0x04000000^M

Hardware Trace Active and Enabled^M

Reset caused by Software reset^M

Compiled for ADSP-BF548 Rev 0.0^M

Warning: Compiled for Rev 0, but running on Rev 1^M

Blackfin Linux support by blackfin.uclinux.org/^M

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

NOMPU: setting up cplb tables for global access^M

Instruction Cache Enabled^M

Data Cache Enabled (write-through)^M

Built 1 zonelists in Zone order, mobility grouping off. Total pages: 14377^M

Kernel command line: root=mtd1 rootfstype=romfs ro^M

Configuring Blackfin Priority Driven Interrupts^M

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

console [ttyBF0] enabled^M

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

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

Memory available: 54980k/65536k RAM, (160k init code, 1555k kernel code, 681k data, 2048k dma, 584k reserved)^M

Blackfin Scratchpad data SRAM: 4 KB^M

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

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

Blackfin Instruction SRAM: 48 KB (42 KB free)^M

Security Framework initialized^M

Mount-cache hash table entries: 512^M

net_namespace: 64 bytes^M

NET: Registered protocol family 16^M

Blackfin GPIO Controller^M

Blackfin DMA Controller^M

ezkit_init(): registering device resources^M

SCSI subsystem initialized^M

NET: Registered protocol family 2^M

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

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

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

TCP: Hash tables configured (established 2048 bind 2048)^M

TCP reno registered^M

io scheduler noop registered^M

io scheduler anticipatory registered (default)^M

io scheduler cfq registered^M

bf54x-lq043: FrameBuffer initializing...^M

dma_alloc_init: dma_page @ 0x00313000 - 512 pages at 0x03e00000^M

bfin-otp: initialized^M

Serial: Blackfin serial driver^M

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

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

smsc911x: Driver version 2007-07-13.^M

eth0: SMSC911x MAC Address: 00:e0:22:fe:b8:54^M

Driver 'sd' needs updating - please use bus_type methods^M

Driver 'sr' needs updating - please use bus_type methods^M

register bfin atapi driver^M

scsi0 : pata-bf54x^M

ata1: PATA max UDMA/66 irq 68^M

ata1.00: ATA-6: TOSHIBA MK4032GAX, AD101A, max UDMA/100^M

ata1.00: 78140160 sectors, multi 16: LBA48 ^M

ata1.00: configured for UDMA/66^M

blk_queue_max_hw_segments: set to minimum 1^M

scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK4032GA AD10 PQ: 0 ANSI: 5^M

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

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

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

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

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

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

sda: sda1 sda2^M

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

physmap platform flash device: 01000000 at 20000000^M

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

Intel/Sharp Extended Query Table at 0x010A^M

Unknown Intel/Sharp Extended Query version 1.5.^M

gen_probe: No supported Vendor Command Set found^M

physmap-flash physmap-flash.0: map_probe failed^M

uclinux[mtd]: RAM probe address=0x389a000 size=0x5655a0^M

Creating 1 MTD partitions on "RAM":^M

0x00000000-0x005655a0 : "ROMfs"^M

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

NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)^M

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

0x00000000-0x00400000 : "Linux Kernel"^M

0x00400000-0x10000000 : "File System"^M

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@4^M

bfin-spi bfin-spi.1: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc02300, dma channel@5^M

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

bf54x-keys: Blackfin BF54x Keypad registered IRQ 76^M

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

i2c /dev entries driver^M

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc00700^M

i2c-bfin-twi i2c-bfin-twi.1: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc02200^M

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

Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).^M

ASoC version 0.13.1^M

AD1980 SoC Audio Codec^M

asoc: AC97 <-> bf5xx-ac97 mapping ok^M

ALSA device list:^M

#0: bf5xx-board (AD1980)^M

TCP cubic registered^M

NET: Registered protocol family 1^M

NET: Registered protocol family 17^M

rtc-bfin rtc-bfin: setting system clock to 2004-05-31 11:48:08 UTC (1086004088)^M

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x0003e383^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x00000383^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x000003ff^M

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

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x000003ff^M

bf5xx-nand bf5xx-nand.0: calced[0x001ab0a9], stored[0x0019532a]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00f4de9b^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x0000069b^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x00000000^M

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

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x00000000^M

bf5xx-nand bf5xx-nand.0: calced[0x000b2164], stored[0x00ffffff]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00061ddc^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x000005dc^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x000003ff^M

bf5xx-nand bf5xx-nand.0: syndrome[3] 0x000006e0^M

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x0000051f^M

bf5xx-nand bf5xx-nand.0: calced[0x000ee223], stored[0x0008ffff]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00fdbfe8^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x000007e8^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x00000000^M

bf5xx-nand bf5xx-nand.0: syndrome[3] 0x0000005f^M

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x0000005f^M

bf5xx-nand bf5xx-nand.0: calced[0x0002a855], stored[0x00ff17bd]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00f4cd66^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x00000566^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x000003ff^M

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

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x000003ff^M

bf5xx-nand bf5xx-nand.0: calced[0x000b3299], stored[0x00ffffff]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x002bd5d5^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x000005d5^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x00000000^M

bf5xx-nand bf5xx-nand.0: syndrome[3] 0x000000af^M

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x000000af^M

bf5xx-nand bf5xx-nand.0: calced[0x0019532a], stored[0x003286ff]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00e8461c^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x0000061c^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x000003ff^M

bf5xx-nand bf5xx-nand.0: syndrome[3] 0x000000eb^M

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x00000314^M

bf5xx-nand bf5xx-nand.0: calced[0x0017b908], stored[0x00ffff14]^M

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

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

bf5xx-nand bf5xx-nand.0: syndrome[0] 0x00ebcd79^M

bf5xx-nand bf5xx-nand.0: syndrome[1] 0x00000579^M

bf5xx-nand bf5xx-nand.0: syndrome[2] 0x00000000^M

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

bf5xx-nand bf5xx-nand.0: syndrome[4] 0x00000000^M

bf5xx-nand bf5xx-nand.0: calced[0x00143286], stored[0x00ffffff]^M

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

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

VFS: Cannot open root device "mtd1" or unknown-block(0,0)^M

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

0800 39070080 sda driver: sd^M

0801 8193118 sda1^M

0802 20482875 sda2^M

1f00 5525 mtdblock0 (driver?)^M

1f01 4096 mtdblock1 (driver?)^M

1f02 258048 mtdblock2 (driver?)^M

Kernel panic - not sy

--

Follow-ups

--- Bernd Schmidt 2008-04-23 03:29:38

My guess would be that this is another case where you passed the wrong device

name to the kernel. Try with mtd2 instead of mtd1.

--- Vivi Li 2008-04-23 07:33:31

Yeah, I tried it but it didn't work...

--

bfin> set bootargs root=mtd1 rootfstype=romfs ro

bfin> tftp 0x1000000 linux.romfs

start Auto negotiation... (take ~2sec)

Auto negotiation complete, 100BaseTX, full duplex

TFTP from server 10.100.4.174; our IP address is 10.100.4.50

Filename 'linux.romfs'.

Load address: 0x1000000

Loading: #################################################################

#################################################################

########################

done

Bytes transferred = 8770649 (85d459 hex)

bfin> boote

Loading .text @ 0x00001000 (1592560 bytes)

Loading .exit.text.refok @ 0x00185cf0 (296 bytes)

Loading .rodata @ 0x00185e20 (440420 bytes)

Loading __ksymtab @ 0x001f1684 (17592 bytes)

Loading __ksymtab_gpl @ 0x001f5b3c (5560 bytes)

Loading __ksymtab_strings @ 0x001f70f4 (57184 bytes)

Loading __param @ 0x00205054 (1080 bytes)

Clearing .bss @ 0x002054a0 (68932 bytes)

Loading .data @ 0x002161e4 (106012 bytes)

Loading .init.text @ 0x00230000 (132292 bytes)

Loading .init.data @ 0x002504c4 (23004 bytes)

Loading .init.setup @ 0x00255ea0 (612 bytes)

Loading .initcall.init @ 0x00256104 (576 bytes)

Loading .con_initcall.init @ 0x00256344 (4 bytes)

Loading .init.ramfs @ 0x00256348 (133 bytes)

Loading .text_l1 @ 0xffa00000 (5636 bytes)

sh_addr: FFA00000, p_paddr: 002563CD

Loading from: 01247000 to 002563CD, size: 5636

Loading .data_l1 @ 0xff800000 (192 bytes)

sh_addr: FF800000, p_paddr: 002579D1

Loading from: 01249000 to 002579D1, size: 192

Loading .romfs @ 0x00258000 (5658624 bytes)

## Starting application at 0x00230000 ...

Linux version 2.6.24.4-ADI-2008R2-pre-svn4644 (test@uclinux84-bf548-kernel)

(gcc version 4.1.2 (ADI8

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

fixedcode = 0x00000400-0x00000490

text = 0x00001000-0x00185cf0

rodata = 0x00185e20-0x0020548c

bss = 0x002054a0-0x002161e4

data = 0x002161e4-0x00230000

stack = 0x0022e000-0x00230000

init = 0x00230000-0x00258000

available = 0x00258000-0x0389a000

rootfs = 0x0389a000-0x03e00000

DMA Zone = 0x03e00000-0x04000000

Hardware Trace Active and Enabled

Compiled for ADSP-BF548 Rev 0.0

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

Blackfin Linux support by blackfin.uclinux.org/

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

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists in Zone order, mobility grouping off. Total pages: 14377

Kernel command line: root=mtd2 rootfstype=romfs ro

Configuring Blackfin Priority Driven Interrupts

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

console [ttyBF0] enabled

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

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

Memory available: 54980k/65536k RAM, (160k init code, 1555k kernel code, 681k

data, 2048k dma, 584k)

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 initialized

Mount-cache hash table entries: 512

net_namespace: 64 bytes

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

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bf54x-lq043: FrameBuffer initializing...

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

bfin-otp: initialized

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

smsc911x: Driver version 2007-07-13.

eth0: SMSC911x MAC Address: 00:e0:22:fe:b8:54

Driver 'sd' needs updating - please use bus_type methods

Driver 'sr' needs updating - please use bus_type methods

register bfin atapi driver

scsi0 : pata-bf54x

ata1: PATA max UDMA/66 irq 68

ata1.00: ATA-6: TOSHIBA MK4032GAX, AD101A, max UDMA/100

ata1.00: 78140160 sectors, multi 16: LBA48

ata1.00: configured for UDMA/66

blk_queue_max_hw_segments: set to minimum 1

scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK4032GA AD10 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 sda2

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

physmap platform flash device: 01000000 at 20000000

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

Intel/Sharp Extended Query Table at 0x010A

Unknown Intel/Sharp Extended Query version 1.5.

gen_probe: No supported Vendor Command Set found

physmap-flash physmap-flash.0: map_probe failed

uclinux[mtd]: RAM probe address=0x389a000 size=0x5655a0

Creating 1 MTD partitions on "RAM":

0x00000000-0x005655a0 : "ROMfs"

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-bit)

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

0x00000000-0x00400000 : "Linux Kernel"

0x00400000-0x10000000 : "File System"

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

regs_base@ffc00500,4

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

regs_base@ffc02300,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.0: Blackfin BF5xx on-chip I2C TWI Contoller,

regs_base@ffc00700

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

regs_base@ffc02200

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

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

2006 UTC).

ASoC version 0.13.1

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 system clock to 2004-05-31 06:32:42 UTC

(1085985162)

VFS: Can't find a romfs filesystem on dev romfs.

List of all partitions:

0800 39070080 sda driver: sd

0801 8193118 sda1

0802 20482875 sda2

1f00 5525 mtdblock0 (driver?)

1f01 4096 mtdblock1 (driver?)

1f02 258048 mtdblock2 (driver?)

No filesystem could mount root, tried: romfs

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

--

--- Bernd Schmidt 2008-04-23 08:53:40

What you quoted still gave the kernel "mtd1" as the root device. Try

with mdt0 and mtd2.

--- Bernd Schmidt 2008-04-23 08:54:01

What you quoted still gave the kernel "mtd1" as the root device. Try

with mtd0 and mtd2.

--- Vivi Li 2008-04-24 01:56:36

Sorry I pasted a wrong log last time.

It can boot up after I use bootargs as "root=mtd0 rootfstype=romfs

ro". Thanks!

Now XIP is been tested with a romfs root filesystem in system ram. Is it

supported on NOR/NAND flash?

--- Bernd Schmidt 2008-04-24 04:39:08

It probably does not work on flash yet.

A very similar bug to this one, with an identical solution, was posted a few

months ago. Before opening new bugs please spend some time trying to research

the cause of the problem.

--- Robin Getz 2008-04-24 09:05:47

Bernd:

>It probably does not work on flash yet.

Hmm - why not? (At least NOR - NAND will not work for sure, but NAND has jffs2

or yaffs).

-Robin

--- Bernd Schmidt 2008-04-24 09:27:37

access_ok would prohibit using flash for user data, and the MPU CPLB code would

need adjusting as well.

--- Vivi Li 2008-05-07 03:37:22

I have tried xip with parallel nor flash, root was mounted but it failed after

dma_alloc_init. I open a new bug 4090 to describe this.

Files

Changes

Commits

Dependencies

Duplicates

Associations

Partner Forums

Partner Libraries

[#4050] xip test case failed in BF548-EZKIT