当前位置: 技术问答>linux和unix
s3c2410内核移植和cramfs.cramfs烧写问题,是怎么了!!!
来源: 互联网 发布时间:2017-01-06
本文导语: 这是我用s3c2410作为开发板写,用DNW软件用串口启动的提示信息: /////////////////////////////////////////////////////// Power on reset Read chip id = ec76 Nand flash status = c0 Env.Os_Auto_Flag=1 ************************************ * ...
这是我用s3c2410作为开发板写,用DNW软件用串口启动的提示信息:
///////////////////////////////////////////////////////
Power on reset
Read chip id = ec76
Nand flash status = c0
Env.Os_Auto_Flag=1
************************************
* *
* 北京蓝海微芯科技发展有限公司 *
* http://www.bluemcu.com *
* Support:010-82684385/86/87 *
************************************
NAND Flash Boot
Please select function :
0 : USB download file
1 : Uart download file
2 : Write Nand flash with download file
3 : Load Pragram from Nand flash and run
4 : Erase Nand flash regions
5 : Write NOR flash with download file
6 : Set boot params
7 : Set AutoBoot parameter,1:linux 2:wince
1
Now download file from uart0...
Download File Size = 1510526
Are you sure to run? [y/n]
Uncompressing Linux................................................................................................... done, booting the kernel.
Linux version 2.6.22.1 (root@localhost.localdomain) (gcc version 3.4.5) #1 Wed Sep 16 08:06:33 CST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: SMDK2410
Warning: bad configuration page, trying to continue
Memory policy: ECC disabled, Data cache writeback
CPU S3C2410A (id 0x32410002)
S3C2410: core 200.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
S3C24XX Clocks, (c) 2004 Simtec Electronics
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 16256
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0,115200 mem=64M
irq: clearing pending status 00002000
irq: clearing subpending status 00000093
irq: clearing subpending status 00000092
PID hash table entries: 256 (order: 8, 1024 bytes)
timer tcon=00090d00, tcnt a2c1, tcfg 00000200,00001030, usec 00001eb8
Console: colour dummy device 80x30
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: 61696KB available (2788K code, 313K data, 132K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2410 Power Management, (c) 2004 Simtec Electronics
S3C2410: Initialising architecture
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4800000, irq 33
DMA channel 1 at c4800040, irq 34
DMA channel 2 at c4800080, irq 35
DMA channel 3 at c48000c0, irq 36
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
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
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
s3c2410-lcd s3c2410-lcd: no platform data for lcd, cannot attach
s3c2410-lcd: probe of s3c2410-lcd failed with error -22
lp: driver loaded but no devices found
ppdev: user-space parallel port driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
s3c2410-uart.0: s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2410
s3c2410-uart.1: s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2410
s3c2410-uart.2: s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2410
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
dm9000 Ethernet Driver
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
BAST NOR-Flash Driver, (c) 2004 Simtec Electronics
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2410-nand s3c2410-nand: Tacls=3, 30ns Twrph0=7 70ns, Twrph1=3 30ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00100000 : "Boot"
0x00100000-0x00500000 : "Kernel"
0x00500000-0x02500000 : "Rootfs"
0x02500000-0x04000000 : "User"
usbmon: debugfs is not available
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-i2c s3c2410-i2c: slave address 0x10
s3c2410-i2c s3c2410-i2c: bus frequency set to 390 KHz
s3c2410-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
TCP cubic registered
NET: Registered protocol family 1
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
List of all partitions:
1f00 1024 mtdblock0 (driver?)
1f01 4096 mtdblock1 (driver?)
1f02 32768 mtdblock2 (driver?)
1f03 27648 mtdblock3 (driver?)
No filesystem could mount root, tried: ext3 ext2 cramfs msdos vfat romfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
////////////////////////////////////////
问题:
之前我已经在
0x00000000-0x00100000 : "Boot"
0x00100000-0x00500000 : "Kernel"
0x00500000-0x02500000 : "Rootfs"
0x02500000-0x04000000 : "User"
在0x005000出写入了rootfs.cramfs, 后来在0x30008000位置写如了内核,然后让内核启动,结果还是出了为题,总是提示出现上面最后红的哪个问题,
上面关于nandflash的分区是按照知道书上写的,但是为什么书上还是提示写内核从0x30008000位置开始写,
如果这样一来的话我把rootfs.cramfs写入0x00500000不对!!!!
|
烧写flash 肯定是能保存到 flash 里去的。问题是你怎么烧写的。
内核从0x30008000位置开始写
============================
内核从这里启动,这是内存地址,而不是flash 地址。
内核从0x30008000位置开始写
============================
内核从这里启动,这是内存地址,而不是flash 地址。
|
你自己编译的内核的机器号和U-BOOT里的机器号不匹配
|
这个过程, 是先通过 tftp 下载文件, 由于uboot 的功能比较单一,并不是直接写到flash 上去,而是放在内存里先, 然后再让你选择放到什么地方去。