MINI6410开发板启动RAMDISK根文件系统失败

jason6765599 2014-05-19 04:33:56
本人按照神帖http://www.arm9home.net/read.php?tid-5610.html制作了RAMDISK并且编译了内核,然后将内核和RAMDISK tftp至内存中:
但是发现ramdisk挂在不上,串口输出消息如下:
MINI6410 # tftp 51000000 ramdisk.gz
dm9000 i/o: 0x18000300, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: 08:90:90:90:90:90
operating at 100M full duplex mode
TFTP from server 192.168.1.34; our IP address is 192.168.1.230
Filename 'ramdisk.gz'.
Load address: 0x51000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#######################################
done
Bytes transferred = 2195395 (217fc3 hex)
MINI6410 # tftp 52000000 zImage
dm9000 i/o: 0x18000300, id: 0x90000a46
DM9000: running in 16 bit mode
MAC: 08:90:90:90:90:90
operating at 100M full duplex mode
TFTP from server 192.168.1.34; our IP address is 192.168.1.230
Filename 'zImage'.
Load address: 0x52000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
######################
done
Bytes transferred = 3769112 (398318 hex)
MINI6410 # bootm 52000000
Boot with zImage
do not support this address : 52000000

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.38-FriendlyARM (root@hsz-virtual-machine) (gcc version 4.5.1 (ctng-1.8.1-FA) ) #2 PREEMPT Mon May 19 15:58:31 CST 2014
CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7), cr=00c5387f
.... .......
one_wire_status: 4
usbcore: registered new interface driver sonixb
usbcore: registered new interface driver sonixj
usbcore: registered new interface driver spca500
usbcore: registered new interface driver spca501
usbcore: registered new interface driver spca505
usbcore: registered new interface driver spca506
spca506: registered
usbcore: registered new interface driver spca508
usbcore: registered new interface driver spca561
usbcore: registered new interface driver spca1528
one_wire_status: 4
usbcore: registered new interface driver sq905
usbcore: registered new interface driver sq905c
usbcore: registered new interface driver sq930x
usbcore: registered new interface driver sunplus
usbcore: registered new interface driver stk014
usbcore: registered new interface driver stv0680
usbcore: registered new interface driver t613
usbcore: registered new interface driver tv8532
usbcore: registered new interface driver vc032x
one_wire_status: 4
usbcore: registered new interface driver xirlink-cit
usbcore: registered new interface driver zc3xx
usbcore: registered new interface driver ALi m5602
usbcore: registered new interface driver STV06xx
gspca_gl860: driver startup - version 0.9d10
usbcore: registered new interface driver gspca_gl860
usbcore: registered new interface driver hdpvr
usbcore: registered new interface driver s2255
one_wire_status: 4
s3c-fimc: controller 0 registered successfully
s3c-fimc: controller 1 registered successfully
FIMC Driver, 2010 ported by FriendlyARM http://www.arm9.net
ov965x: probe
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: i2c transfer error
s3c-fimc: ov965x: Product ID fb:fb Manufacturer ID fb:fb
parent clock for camera: 266.000 MHz, divisor: 11
[CAM]RESET CAM.
one_wire_status: 4
S3C6400 MFC Driver, (c) 2007 Samsung Electronics, 2010 ported by FriendlyARM http://www.arm9.net
S3C6400 MFC Driver init OK.
S3C PostProcessor Driver v3.12, (c) 2009 Samsung Electronics
S3C6410 TV encoder Driver, (c) 2008 Samsung Electronics
S3C6410 TV encoder Driver init OK.
S3C6410 TV scaler Driver, (c) 2008 Samsung Electronics
S3C6410 TV scaler Driver init OK.
S3C Rotator Driver, (c) 2008 Samsung Electronics
s3c_rotator_probe called
s3c_rotator_probe success
S3C JPEG Driver, (c) 2007 Samsung Electronics
one_wire_status: 4
s3c_g2d_probe called
s3c_g2d_probe Success
S3C G2D Init : Done
S3C G3D Driver, (c) 2007-2009 Samsung Electronics
s3c_g3d version : 0x1050000
S3C G3D Init : Done
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
sdhci: Secure Digital Host Controller Interface driver
one_wire_status: 4
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (24000000 Hz)
one_wire_status: 4
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133000000 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: mmc_bus (24000000 Hz)
mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SU08G 7.40 GiB
mmcblk0: p1
mmc1: new SDIO card at address 0001
asoc: wm9713-hifi <-> samsung-ac97 mapping ok
ALSA device list:
#0: MINI6410
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
s3c-rtc s3c64xx-rtc: setting system clock to 2000-03-22 23:29:40 UTC (953767780)
Freeing init memory: 1412K
mount: mounting /dev/ram on /r failed: No such file or directory
1Wire touchscreen OK
/init: line 103: can't open /r/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
[<c0178c44>] (unwind_backtrace+0x0/0xe4) from [<c0515d4c>] (panic+0x58/0x174)
[<c0515d4c>] (panic+0x58/0x174) from [<c018aeb0>] (do_exit+0x68/0x5e4)
[<c018aeb0>] (do_exit+0x68/0x5e4) from [<c018b6f0>] (do_group_exit+0x90/0xc4)
[<c018b6f0>] (do_group_exit+0x90/0xc4) from [<c018b734>] (sys_exit_group+0x10/0x18)
[<c018b734>] (sys_exit_group+0x10/0x18) from [<c01735e0>] (ret_fast_syscall+0x0/0x30)
one_wire_status: 2
然后bootargs为;
bootargs=initrd=0x51000000,0x800000 root=/dev/ram rw init=/linuxrc console=ttySAC0,115200 mem=64M
我以前在OK6410上按照帖子配置之后妥妥的,为何在mini6410上就不行呢?
...全文
152 1 打赏 收藏 转发到动态 举报
写回复
用AI写文章
1 条回复
切换为时间正序
请发表友善的回复…
发表回复
jason6765599 2014-06-11
  • 打赏
  • 举报
回复
原因已经找到,重新做一遍RAMDISK就行了。

21,600

社区成员

发帖
与我相关
我的任务
社区描述
硬件/嵌入开发 驱动开发/核心开发
社区管理员
  • 驱动开发/核心开发社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧