2008-08-15 23:52:34     why the vmImage contain the rootfs?

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

2008-08-15 23:52:34     why the vmImage contain the rootfs?

Zhi Qiang Zhang (CHINA)

Message: 60519   

 

Hi,

 

I am using this version

 

kernel: Linux release 2.6.26.2-ADI-2009R1-pre-svn5193-dirty17, build #3 PREEMPT Sat Aug 16 11:14:29 HKT 2008

toolchain: bfin-uclinux-gcc release gcc version 4.1.2 (ADI svn)

user-dist: release svn-7000, build #479 Sat Aug 16 11:12:24 HKT 2008

 

in u-boot, I download vmImage, and set the bootargs

 

setenv bootargs 'console=ttyBF0,115200n8'

 

tftp 0x1000000 vmImage;bootm

 

 

 

then it boots with the rootfs, it seems the vmImage contain the rootfs, right? How to build the vmImage without rootfs?

 

Starting Kernel at = 1f41f0

Linux version 2.6.26.2-ADI-2009R1-pre-svn5193-dirty17 (zzq01@linuxhost) (gcc version 4.1.2 (ADI svn)) #3 PREEMPT Sat Aug 16 11:14:28

Warning: limiting memory to 56MB due to hardware anomaly 05000263

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

fixedcode = 0x00000400-0x00000490

text = 0x00001000-0x00158590

rodata = 0x001585a0-0x001bef4c

bss = 0x001bef60-0x001d1b00

data = 0x001d1b00-0x001e6000

stack = 0x001e4000-0x001e6000

init = 0x001e6000-0x00390000

available = 0x00390000-0x037ff000

DMA Zone = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Reset caused by Software reset

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

Compiled for ADSP-BF537 Rev 0.2

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

Processor Speed: 625 MHz core clock and 104 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: 14223

Kernel command line: console=ttyBF0,115200n8

Preemptible RCU implementation.

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: 53112k/65536k RAM, (1704k init code, 1373k kernel code, 567k data, 1024k dma, 7756k reserved)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

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

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

Blackfin L1 Instruction SRAM: 48 KB (40 KB free)

net_namespace: 192 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

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

NET: Registered protocol family 1

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

msgmni has been set to 103

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

PPI: ADSP PPI Frame Capture Driver IRQ:11

Serial: Blackfin serial driver

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

brd: module loaded

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=104MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

physmap platform flash device: 00400000 at 20000000

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

Amd/Fujitsu Extended Query Table at 0x0040

number of CFI chips: 1

cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.

RedBoot partition parsing not available

Using physmap partition information

Creating 4 MTD partitions on "physmap-flash.0":

0x00000000-0x00040000 : "bootloader(nor)"

0x00040000-0x00280000 : "linux kernel(nor)"

0x00280000-0x003f0000 : "file system(nor)"

0x003f0000-0x00400000 : "MAC Address(nor)"

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

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

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

TCP cubic registered

NET: Registered protocol family 17

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

rtc-bfin rtc-bfin: setting system clock to 1970-01-01 02:02:49 UTC (7369)

Freeing unused kernel memory: 1704k freed

dma_alloc_init: dma_page @ 0x0038d000 - 256 pages at 0x03f00000

_____________________________________

a8888b. / Welcome to the uClinux distribution \

d888888b. / _ _ \

8P"YP"Y88 / | | |_| __ __ (TM) |

8|o||o|88 _____/ | | _ ____ _ _ \ \/ / |

8' .88 \ | | | | _ \| | | | \ / |

8`._.' Y8. \ | |__ | | | | | |_| | / \ |

d/ `8b. \ \____||_|_| |_|\____|/_/\_\ |

dP . Y8b. \ For embedded processors including |

d8:' " `::88b \ the Analog Devices Blackfin /

d8" 'Y88b \___________________________________/

:8P ' :888

8a. : _a88P For further information, check out:

._/"Yaa_: .| 88P| - http://blackfin.uclinux.org/

\ YP" `| 8P `. - http://docs.blackfin.uclinux.org/

/ \.___.d| .' - http://www.uclinux.org/

`--..__)8888P`._.' jgs/a:f - http://www.analog.com/blackfin

 

Have a lot of fun...

 

 

BusyBox v1.11.1 (2008-08-16 11:08:40 HKT) built-in shell (msh)

Enter 'help' for a list of built-in commands.

 

root:/>

 

Regards,

 

ZhangZQ

QuoteReplyEditDelete

 

 

2008-08-16 00:02:58     Re: why the vmImage contain the rootfs?

Mike Frysinger (UNITED STATES)

Message: 60520   

 

review the documentation:

http://docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:images

QuoteReplyEditDelete

 

 

2008-08-16 01:50:56     Re: why the vmImage contain the rootfs?

Zhi Qiang Zhang (CHINA)

Message: 60521   

 

Mike,

 

I read that document, here is some text from that document "vmImage The Linux kernel in the bootable U-Boot format -- no root filesystem"

 

but why my vmImage has the rootfs?

 

 

 

Regrards,

 

ZhangZQ

QuoteReplyEditDelete

 

 

2008-08-16 10:24:32     Re: why the vmImage contain the rootfs?

Mike Frysinger (UNITED STATES)

Message: 60545   

 

update your svn checkout

QuoteReplyEditDelete

 

 

2008-08-16 11:48:39     Re: why the vmImage contain the rootfs?

Zhi Qiang Zhang (CHINA)

Message: 60546   

 

Mike,

 

It is ok now, I can use the jffs2 as the rootfs now, but I got many message, here is some of those message,

 

physmap platform flash device: 00400000 at 20000000

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

Amd/Fujitsu Extended Query Table at 0x0040

number of CFI chips: 1

cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.

RedBoot partition parsing not available

Using physmap partition information

Creating 4 MTD partitions on "physmap-flash.0":

0x00000000-0x00040000 : "bootloader(nor)"

0x00040000-0x001c0000 : "linux kernel(nor)"

0x001c0000-0x003f0000 : "file system(nor)"

0x003f0000-0x00400000 : "MAC Address(nor)"

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

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

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

TCP cubic registered

NET: Registered protocol family 17

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:01:39 UTC (99)

Empty flash at 0x00140364 ends at 0x00140368

Empty flash at 0x001406cc ends at 0x001406d0

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406d0: 0x0029 instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406d4: 0x037f instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406dc: 0x0029 instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406e0: 0x037f instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406e8: 0x0029 instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406ec: 0x037f instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406f4: 0x0029 instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001406f8: 0x037f instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00140700: 0x0029 instead

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00140704: 0x037f instead

Further such events for this erase block will not be printed

Empty flash at 0x00140a34 ends at 0x00140a38

Empty flash at 0x00140d9c ends at 0x00140da0

Empty flash at 0x00141104 ends at 0x00141108

 

 

 

What are those message?

 

 

 

Regards,

 

ZhangZQ

QuoteReplyEditDelete

 

 

2008-08-17 10:09:46     Re: why the vmImage contain the rootfs?

Mike Frysinger (UNITED STATES)

Message: 60547   

 

start a new thread please

Attachments

    Outcomes