天嵌 ARM开发社区

 找回密码
 注册
查看: 3262|回复: 7

请教构建文件系统问题

 关闭 [复制链接]
wsmahan 发表于 2010-1-28 10:28:17 | 显示全部楼层 |阅读模式
按照教程构建了一个文件系统(适合linux-2.6.30.4内核),
但编译后,烧入开发板出错,
重复了教程好几遍,但现在还是同样的问题,
不知道站里的学长们有没有也碰到同样的问题的?

问题出现提示:
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 180K
Warning: unable to open an initial console.
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Backtrace:
[<c0039fd4>] (dump_backtrace+0x0/0x10c) from [<c02b17f8>] (dump_stack+0x18/0x1c)

r7:00000000 r6:c03bdf40 r5:c03bd900 r4:c0396248
[<c02b17e0>] (dump_stack+0x0/0x1c) from [<c02b1848>] (panic+0x4c/0x124)
[<c02b17fc>] (panic+0x0/0x124) from [<c00354f0>] (init_post+0xec/0x178)
r3:00000000 r2:c384ee00 r1:c03f1000 r0:c033f2dc
[<c0035404>] (init_post+0x0/0x178) from [<c000847c>] (kernel_init+0xcc/0xf4)
r5:c001d670 r4:c001d9d4
[<c00083b0>] (kernel_init+0x0/0xf4) from [<c004af30>] (do_exit+0x0/0x620)
r7:00000000 r6:00000000 r5:00000000 r4:00000000
亚瑟王 发表于 2010-1-28 21:16:45 | 显示全部楼层
1、制作文件系统的编译器和编译内核的编译器相同吗?
2、使用你的内核烧写天嵌科技的文件系统能起来吗?
3、是不是你的TQ2440开发板的Nand 是256MB的,你烧写的是64MB的文件系统?
 楼主| wsmahan 发表于 2010-1-29 09:38:04 | 显示全部楼层
本帖最后由 wsmahan 于 2010-1-29 09:54 编辑

1、我使用的开发板是nand 256MB,教程为v4.0-20091028的
2、编译环境是RedHat9,交叉编译器是EABI 4.3.3(其中pc的/etc/profile已更改)
3、busybox为busybox-1.13.0(通过解压,安装)
4、文件系统编译器:直接linux-2.6.30.4_20091030.tar.bz2通过解压后的yaffs
5、内核编译器:这个不是很清楚,电脑上就解压了linux-2.6.30.4,开发板用的是:
     出厂烧录镜像-东华-zImage_2.6.30.4_W35_256MB_20091030.bin
6、使用过公司提供的文件系统(QT源码包-root_qtopia_2.2.0_2.6.30.4_20091030.tar),
   通过编译,烧入开发板也出错,估计是我没配置好编译环境,但不知道是遗漏了重要的哪一步?
 楼主| wsmahan 发表于 2010-2-3 16:00:56 | 显示全部楼层
2# 亚瑟王
请问“制作文件系统的编译器和编译内核的编译器相同吗?”是什么意思?
是不是指编译前一步,使用#make menuconfig 进去的配置单?
如果不是,能否具体介绍下?谢谢(不好意思,linux刚刚接触的)
亚瑟王 发表于 2010-2-3 17:51:50 | 显示全部楼层
1、编译内核时使用的编译器要和编译busybox、文件系统中的lib目录下使用的编译器相同。
2、要在dev下面建立console和null两个设备节点,不然不能启动的。Linux移植手册里面讲了这两点的。
 楼主| wsmahan 发表于 2010-2-4 14:11:47 | 显示全部楼层
你好,你说的两个我都已经修改了,下面是错误的部分代码提示:                             

block 25 is badck at  0x021800
blo
Bad eraseblock 245 at 0x000001ea0000is badd block at  0x0
block 28 is ba
Bad eraseblock 246 at 0x000001ec0000d block at
block 30 is bad  
RPC: Re
Bad eraseblock 247 at 0x000001ee0000block 32 is bad0              
block
Bad eraseblock 248 at 0x000001f00000 bad200000         
block 35 is badc
Bad eraseblock 249 at 0x000001f200000000   
block 37 is bad            
Bad eraseblock 250 at 0x000001f40000ock 39 is bad is bad24 is ba
block 4
Bad eraseblock 251 at 0x000001f60000ad bad 225 is bad
block 42 is bad at
Bad eraseblock 252 at 0x000001f80000 is ba
block 44 is bad      
OK  


Bad eraseblock 270 at 0x0000021c00006 is badet to 1        
block 87 is
Bad eraseblock 271 at 0x0000021e0000ters        
block 89 is badr] Reboo
Bad eraseblock 272 at 0x000002200000n
block 91 is bad)ck 53 is badf8
blo
Bad eraseblock 273 at 0x000002220000is bad 54 i
Enter you
block 94 is ba
Bad eraseblock 274 at 0x000002240000OS for SKY
block 96 is bad#2 is bads
Bad eraseblock 275 at 0x000002260000block 98 is badto Download Mod
block
Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit": fr
block 101 is badux kernel from 0
block 102 is bad0
0x000000000000-0x000000040000 : "EmbedSky_Board_uboot"104 is bad               
block 105 is badbad: tq2440
0x000000200000-0x000000400000 : "EmbedSky_Board_kernel"000000 r2:c3   
block 108 is bad   
           
block
usbcore: registered new interface driver usb-storage1 is bad               
block 152 is bad bader
Buil
USB Mass Storage support registered.
block 154 is badal pages: 16256

b
usbcore: registered new interface driver usbserial   
......  
block 157 is badmmand line: noin
blo
usbserial: USB Serial Driver corek 159 is badSAC0.... done, b
bloc
USB Serial support registered for pl2303 badad v1:1.10tes)k
block 162 is bad   
usbcore: registered new interface driver pl2303lock 164 is bad        

block
block 165 is ba
pl2303: Prolific PL2303 USB to serial adaptor driverock 168 is badEmbe
PID hash ta
block 169 is bad(orde
s3c2410_udc: debugfs dir creation failed -19block 171 is bad     

Console:
block 172 i
block 238
usbcore: registered new interface driver usbhid-i2c: i
block 240 is badpteroad Linux   
block
usbhid: v2.6:USB HID core driver242 is bading CRDA to upda
block
Advanced Linux Sound Architecture Driver Version 1.0.18a.  
yaffs_read_super: isCheckpointed 0otocol family 2     
No device for DAI UDA134Xd root (yaffs filesystem)
No device for DAI s3c24xx-i2s096 bytes)  
block 176 is bad
S3C24XX_UDA134X SoC Audio driver0K        
TCP established
Warn
UDA134X SoC Audio Codecnitial console.tes)   
asoc: UDA134X <-> s3c24xx-i2s mapping okd to execute /linuxrc.  Attempting defau
ALSA device list:er: 1, 8192 bytes
  #0: S3C24XX_UDA134X (UDA134X)nic - not syncing: No init foun
TCP cubic registered option to kernel.8
RPC: Registered udp transport module.block 183 is bad 374K dot th
TCP reno
RPC: Registered tcp transport module.dump_backtrace+0x0/0x10c) from [<c02b
lib80211: common routines for IEEE802.1121:01:24 In           
               
block 3 is baddcized     
S3
block 4 is bad3
PWM-Test ini
block 5 is bad404>] (init_po
block 6 is badrom [<c000847c
block 7 is bad+0xcc/0xf4)eri
block 8 is bad0000000 (irq =
block 9 is bad40h           
block 10 is bad r5:c001d670 r4
block 11 is bad   
Bad erase

block 12 is bad(kernel_init+0x
block 13 is bad004af30>] (do_e
block 14 is bad   
block 208
block 15 is bad              

block 16 is bad   
b
s3
r7:0
block 17 is bad000 r5:00000000
block 18 is bad= 76) is a S3C2
block 19 is bad            


block 20 is badBIOS for SKY244
block 21 is badoop: module loa
block 22 is bad      
   
   
block 2
block 39 is bad...............
block 40 is bad...............
block 41 is badne, booting the
block 42 is bad   
s3c2440-nan
block 43 is badTacls=2, 20ns T
block 44 is badr
kernel.ns   
block 45 is bad2.6.30.4-EmbedS
block 46 is bady) (gcc version
block 47 is bad G++ufacturer I
block 48 is bad: 0xda (Samsung
block 49 is badV 8-bi         
block 50 is bad09q1-203) ) #13
block 51 is bad5:00 CST 2009  
block 52 is badcanning device
block 53 is bad co
CPU: ARM920
block 54 is badision 0 (ARk 33
block 55 is bad               
block 60 is badecated; please
block 61 is badloader.rnel.   
block 62 is bad           
Bad
block 63 is badt
Memory polic
block 64 is bad Data cache wri
block 65 is badlock 38 at 0x00
block 66 is badom [<c02
CPU S3
block 67 is bad40001)seblock 3
block 68 is bad000
S3C24XX Clo
block 69 is badmtec Electronic
block 70 is bad000000500000c03
block 71 is badC244X: core 400
block 72 is bad 100.000 MHz, p
block 73 is bad MHz2b17e0>] (d
block 74 is badraseblock 42 at
block 75 is bad4c/0x124)
CLOC
block 76 is bad500 MHz), fast,
block 77 is badn0560000      
block 78 is bad (panic+0x0/
Ba
block 79 is badzonelists in Zo
block 80 is badty grouping on.
block 81 is bad6256k 45 at 0x0
block 82 is bad      
r3:0000
block 83 is badBad eraseblock
block 84 is bad line: noinitrd
block 85 is badock2 init=/linu
block 86 is badAC000005e0000)
block 87 is bad               
block 88 is bad               
Bad e
Press
block 94 is badnload Mode !   
block 95 is bad0000000 r6:
Bad
block 96 is bad..0x00000066000
block 97 is badkernel from 0x0
block 98 is bad08000, size = 0
block 99 is badpy Kern0 #####
block 100 is badd eraseblock 53
block 101 is badSpace key to Dow
block 102 is badM done,NOW, Boot
block 103 is badc0000  Boot for
block 104 is badenu  #
Uncompres
block 105 is bad................
block 106 is bad................
block 107 is bad 0x000000700000N
block 108 is bad               
block 109 is bad57
.............
block 110 is bad................
block 111 is badone, booting the
block 112 is badwnload Linux Ker
block 113 is badraseblock 59 at
block 114 is badnel.  
[5]
Linu
block 115 is bad4-EmbedSky (root
block 116 is badersion 4.3.3 (So
block 117 is badYAFF
Bad erasebl
block 118 is bad07a0000         
block 119 is bad      
        
block 120 is         
block 132 is badyour bootloader.
block 133 is bad.bin) to Nand
Ba
block 134 is badt 0x000
Memory p
block 135 is baded, Data cache w
block 136 is bad 69 at 0x0000008
block 137 is bad      
CPU S3C2
block 138 is bad01)ck 70 at 0x00
block 139 is bad3C24XX Clocks, (
block 140 is badectronicsk 71 at
block 141 is bad:               
block 142 is bad 400.000 MHz, me
block 143 is bad peripheral 50.0
block 144 is bad     
Bad eraseb
block 145 is bad00920000EPLDR.nb
block 146 is badlow mode (1.500
block 147 is badon, UPLL on00   
block 148 is bad               

block 149 is badilt 1 zonelists
block 150 is badbility g        
block 151 is bad               
block 158 is bad0080000eblock 79
block 159 is bad0Program (uCOS-

block 160 is badding status 0200
block 161 is bada00000         
block 162 is badaring subpending
block 163 is bad00000a20000     
block 164 is badmat th
PID hash
block 165 is bad6 (order: 8, 102
block 166 is badeters           
block 168 is bad 83 at 0
Console
block 169 is badvice 80x30Q2440_
block 170 is badblock 84 at
cons
block 171 is badbled     
[b] Do
block 172 is badtry cache hash t
block 173 is bad2 (order: 3, 327
block 174 is bad
Bad eraseblock
block 175 is bad000            
block 176 is badhash table entri
block 178 is bad2, 16384 bytes))
block 179 is bad         
Bad e
block 180 is badx000000b0
Memory
block 181 is badalon:         

block 182 is bady: 60876KB avail
block 183 is bad 374K d         
block 184 is bad               
block 194 is badbc0000h  
CPU: T
block 195 is bader coherency: ok
block 196 is bad00000be0000nd Fl
block 197 is badace: 296 bytesBa
block 198 is badt 0x0
NET: Regis
block 199 is badmily 16 SDRAM an
block 200 is bad 97 at 0
S3C2440
block 201 is badchitecture      
block 202 is badblock 98 at
S3C2
block 203 is bad Format the Nand
block 204 is badriver, (c) 2003-
block 205 is badElectronics     
block 206 is bad
Bad eraseblock
block 207 is bad00
DMA channel 0
block 208 is bad 33   
Bad eras
block 209 is bad000
DMA channel
block 210 is badq 34re (.bin)
B
block 211 is bad at
DMA channel
block 212 is badrq 35   
[l] Se
block 213 is badock 1
DMA channe
block 214 is badirq 36         
block 215 is bad      
         
usbco
block 227 is badw device driver
block 228 is badk at            
block 229 is bad40-i2c s3c2440-i
block 230 is bad 0x10000ing bad
block 231 is badBad eraseblock

block 232 is bad40-i2c: bus freq
block 233 is badHzBad
block 239 is bad
block 240 is bad
block 241 is bad
block 242 is bad
block 243 is bad
block 244 is bad
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 180K
Warning: unable to open an initial console.
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Backtrace:
[<c0039fd4>] (dump_backtrace+0x0/0x10c) from [<c02b17f8>] (dump_stack+0x18/0x1c)

r7:00000000 r6:c03bdf40 r5:c03bd900 r4:c0396248
[<c02b17e0>] (dump_stack+0x0/0x1c) from [<c02b1848>] (panic+0x4c/0x124)
[<c02b17fc>] (panic+0x0/0x124) from [<c00354f0>] (init_post+0xec/0x178)
r3:00000000 r2:c384ae00 r1:c03f1000 r0:c033f2dc
[<c0035404>] (init_post+0x0/0x178) from [<c000847c>] (kernel_init+0xcc/0xf4)
r5:c001d670 r4:c001d9d4
[<c00083b0>] (kernel_init+0x0/0xf4) from [<c004af30>] (do_exit+0x0/0x620)
r7:00000000 r6:00000000 r5:00000000 r4:00000000
 楼主| wsmahan 发表于 2010-2-4 15:43:55 | 显示全部楼层
问题已经解决!!!
自己太粗心大意了,最后一步命令错打成---#mkyaffsimage
应该是---#mkyaffs2image
谢谢版主-亚瑟王
亚瑟王 发表于 2010-2-6 00:38:59 | 显示全部楼层
呵呵,根据你后来贴出来的,那么多坏块的产生,我猜到了,可能镜像文件压制有问题。因为512字节和2K字节页面的nand的坏块区分上的处理不一样。mkyaffsimage压制的yaffs文件系统是针对512字节的nand(64MB的),而mkyaffs2image压制的是针对2K页面的nand(大于或等于256MB的),
您需要登录后才可以回帖 登录 | 注册

本版积分规则

关闭

i.MX8系列ARM cortex A53 M4 工控板上一条 /1 下一条

Archiver|手机版|小黑屋|天嵌 嵌入式开发社区 ( 粤ICP备11094220号 )

GMT+8, 2024-5-5 10:16 , Processed in 1.062494 second(s), 18 queries .

Powered by Discuz! X3.4

Copyright © 2001-2020, Tencent Cloud.

快速回复 返回顶部 返回列表