search

yjftsjthsd-g / virtualmips

Automatically exported from code.google.com/p/virtualmips
0 stars 0 forks source link

Error occurs when scanning nandflash during booting linux kernel #5

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 

The information of starting linux kernel when scanning nandflash:

block2mtd: version $Revision: 1.30 $
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V
8-bit)
Scanning device for bad blocks
Bad eraseblock 64 at 0x0081f800
Bad eraseblock 65 at 0x0083f800
Bad eraseblock 66 at 0x0085f800
...
Bad eraseblock 498 at 0x03e5f800
Bad eraseblock 499 at 0x03e7f800
Bad eraseblock 500 at 0x03e9f800
Creating 6 MTD partitions on "NAND 1GiB 3,3V 8-bit":
0x00000000-0x00400000 : "NAND BOOT partition"
0x00400000-0x00800000 : "NAND KERNEL partition"
0x00800000-0x08000000 : "NAND ROOTFS partition"
0x08000000-0x10000000 : "NAND DATA1 partition"
0x10000000-0x20000000 : "NAND DATA2 partition"
0x20000000-0x40000000 : "NAND VFAT partition"
mice: PS/2 mouse device common for all mice
JzSOC Watchdog Timer: timer margin 60 sec
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
mtdblock_block_info_map_bad_block: bad_block=1
mtdblock_block_info_map_bad_block: bad_block=2
mtdblock_block_info_map_bad_block: bad_block=3
mtdblock_block_info_map_bad_block: bad_block=4
mtdblock_block_info_map_bad_block: bad_block=5
mtdblock_block_info_map_bad_block: bad_block=6
mtdblock_block_info_map_bad_block: bad_block=7
mtdblock_block_info_map_bad_block: bad_block=8
mtdblock_block_info_map_bad_block: bad_block=9
mtdblock_block_info_map_bad_block: bad_block=10
Warning: too many bad blocks: 11, nand flash is un-useable
Warning: too many bad blocks: 12, nand flash is un-useable
...
Warning: too many bad blocks: 436, nand flash is un-useable
Warning: too many bad blocks: 437, nand flash is un-useable
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
block 1 is bad
block 2 is bad
block 3 is bad
...
block 434 is bad
block 435 is bad
block 436 is bad
block 437 is bad
VFS: Mounted root (yaffs2 filesystem).
Freeing unused kernel memory: 172k freed
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

What version of the product are you using? On what operating system?
ubuntu-8.04
virtualmips-0.05
uImage-2.6 in test_suit-0.05
rootfs.tgz download from www.ingenic.cn, mkyaffs2image root26 root.yaffs2
the command mkyaffs2image is build from the code download from www.yaffs.net

Original issue reported on code.google.com by peterlih...@gmail.com on 3 Jun 2008 at 2:40

GoogleCodeExporter commented 8 years ago 
Please compile the mkyaffs2image from jz's linux 2.6.24 kernel with jz
patch(fs/yaffs2/utils). It may slove your problem.

I will download the code from www.yaffs.net and try it later. Some guy reports 
the
same problem. He uses the mkyaffs2image from yaffs.net too.

Thanks for your report.

Original comment by YaJinZ...@gmail.com on 4 Jun 2008 at 1:26

GoogleCodeExporter commented 8 years ago 
You can not use the mkyaffs2image from www.yaffs.net directly.
Please compile the mkyaffs2image follow
http://code.google.com/p/virtualmips/wiki/PavoEmulation.

I have tested it on ubuntu 8.04 and virtualmips 0.06. It works.

Original comment by YaJinZ...@gmail.com on 4 Jun 2008 at 2:37

GoogleCodeExporter commented 8 years ago

Original comment by YaJinZ...@gmail.com on 7 Jun 2008 at 3:49

GoogleCodeExporter commented 8 years ago 
Yes, Thank you！

Original comment by peterlih...@gmail.com on 12 Jun 2008 at 2:37

GoogleCodeExporter commented 8 years ago

Original comment by YaJinZ...@gmail.com on 13 Jun 2008 at 12:59