- 积分
- 4
贡献15
飞刀0 FD
注册时间2015-12-21
在线时间1 小时
扫一扫,手机访问本帖
|
各位高手 本人新手 学习 OK6410-A开发板的 sd卡方式一键烧写linux时,提示nand flash有坏块,虽烧成功,但是从nand flash 启动失败。
板子的参数和 烧写的过程 的串行打印数据如下: (希望各位高手指点,我该怎么办。难道要维修或者还是有解决的方法) 注:我重新烧回WINCE 则又可以;
U-Boot 1.1.6 (Sep 25 2012 - 10:10:38) for SMDK6410
****************************************
** u-boot 1.1.6 **
** Updated for OK6410 TE6410 Board **
** Version (2012-09-23) **
** OEM: Forlinx Embedded **
** Web: http://www.witech.com.cn **
****************************************
CPU: S3C6410 @532MHz
Fclk = 532MHz, Hclk = 133MHz, Pclk = 66MHz, Serial = CLKUART (SYNC Mode)
Board: SMDK6410
DRAM: 128 MB
Flash: 0 kB
NandFlash Information:
Nandflash:ChipType= MLC ChipName=samsung-K9LBG08U0D
No No Calc pagesize, blocksize, erasesize, use ids table .............
NandFlash:name=NAND 4GiB 1,8V 8-bit,id=d7, pagesize=4096 ,chipsize=2048 MB,erasesize=524288 oobsize=128
NandFlash Size is 2048 MB
SD/MMC: SD 2.0 SDHC / Manufacturer: 0x27,OEM: "PH/SD8GB",REV: 3.0,S/N: 28129153,DATE: 2015/10
SDHC size: 7386 MiB
Freq = 50MHz
In: serial
Out: lcd
Err: lcd
Hit any key to stop autoboot: 0
###################### User Menu for OK6410#####################
[1] Format the nand flash
[2] Burn image from SD card
[3] Burn image from USB
[4] Reboot the u-boot
[5] Exit to command line
-----------------------------Select---------------------------------
Enter your Selection:1
NAND scrub: device 0 whole chip
Warning: scrub option will erase all factory set bad blocks!
There is no reliable way to recover them.
Use this command only for testing purposes if you
are sure of what you are doing!
Really scrub this NAND flash? <y/N>
Erasing at 0x2880000 -- 2% complete.
NAND 4GiB 1,8V 8-bit: MTD Erase failure: -5
NAND 4GiB 1,8V 8-bit: MTD Erase failure: -5
NAND 4GiB 1,8V 8-bit: MTD Erase failure: -5
NAND 4GiB 1,8V 8-bit: MTD Erase failure: -5
NAND 4GiB 1,8V 8-bit: MTD Erase failure: -5
Erasing at 0x7ff80000 -- 100% complete.
Scanning device for bad blocks
OK
###################### User Menu for OK6410#####################
[1] Format the nand flash
[2] Burn image from SD card
[3] Burn image from USB
[4] Reboot the u-boot
[5] Exit to command line
-----------------------------Select---------------------------------
Enter your Selection:5
SMDK6410 # K
U-Boot 1.1.6 (Sep 25 2012 - 10:10:38) for SMDK6410
****************************************
** u-boot 1.1.6 **
** Updated for OK6410 TE6410 Board **
** Version (2012-09-23) **
** OEM: Forlinx Embedded **
** Web: http://www.witech.com.cn **
****************************************
CPU: S3C6410 @532MHz
Fclk = 532MHz, Hclk = 133MHz, Pclk = 66MHz, Serial = CLKUART (SYNC Mode)
Board: SMDK6410
DRAM: 128 MB
Flash: 0 kB
NandFlash Information:
Nandflash:ChipType= MLC ChipName=samsung-K9LBG08U0D
No No Calc pagesize, blocksize, erasesize, use ids table .............
NandFlash:name=NAND 4GiB 1,8V 8-bit,id=d7, pagesize=4096 ,chipsize=2048 MB,erasesize=524288 oobsize=128
NandFlash Size is 2048 MB
SD/MMC: SD 2.0 SDHC / Manufacturer: 0x27,OEM: "PH/SD8GB",REV: 3.0,S/N: 28129153,DATE: 2015/10
SDHC size: 7386 MiB
Freq = 50MHz
In: serial
Out: lcd
Err: lcd
Hit any key to stop autoboot: 0
NAND erase: device 0 whole chip
Skipping bad block at 0x02f00000
Skipping bad block at 0x02f80000
Skipping bad block at 0x03380000
Skipping bad block at 0x03480000
Skipping bad block at 0x03680000
Erasing at 0x7ff80000 -- 100% complete.
OK
reading u-boot.bin
212992 bytes read
NAND write: device 0 offset 0x0, size 0x200000
1032192 bytes written: OK
reading zImage
3638592 bytes read
NAND write: device 0 offset 0x200000, size 0x500000
Writing data at 0x6ff000 -- 100% complete.
5242880 bytes written: OK
reading rootfs.yaffs2
128679936 bytes read
NAND write: device 0 offset 0x700000, size 0x7ab8000
Bad block at 0x2f00000 in erase block from 0x2f00000 will be skipped
Bad block at 0x2f80000 in erase block from 0x2f80000 will be skipped
Bad block at 0x3380000 in erase block from 0x3380000 will be skipped
Bad block at 0x3480000 in erase block from 0x3480000 will be skipped
Bad block at 0x3680000 in erase block from 0x3680000 will be skipped
Writing data at 0x807f000 -- 100% complete.
128679936 bytes written: OK
|
|