Phonesuite烧写有问题

mengwei2275

烧到88%的时候就停了，ct - lubuntu、

mengwei2275

[Fet]:find a bad block 12
[Fet]:find a bad block 4094
[Fet]:find a bad block 4095

mengwei2275

FES:INFO : ......1........
FES:INFO : ......2........
FES:INFO : ......3........
FES:INFO : ......5........
FES:INFO : ......6........
FES:INFO : ......7........
FES:INFO : ......8........
FES:INFO : ......9........
FES:CONFIG_USB_GADGET_DUALSPEED
FES:fes connect to host
FES:USB_MOV_DATA_BY_DMA!
FES:INFO : ......10.......
FES:jump to fes_main
FES:INFO: fes_protocol_process start
FES:[info]: set address 11
FES:write special pipe
FES:INFO: fed reg_addr = 0x4011f714
FES:fed para[0] = 0x40a00000
FES:fed para[1] = 0x40a01000
FES:fed para[2] = 0x00000000
FES:fed para[3] = 0x00000000
[Fed]:-------------------------------------------------
[Fed]:                Hello, Nand Register
[Fed]:-------------------------------------------------
[Fed]:"private" part NOT configured.
NHW : start nand scan
[NAND] nand driver(b) version: 0x2, 0x12, data: 20130325
NFC Randomizer start.
[SCAN_DBG] Nand flash chip id is:0xad 0xde 0x94 0xda 0x74 0xc4
NFC Read Retry Init.
chip 0, block 8, page 0, oob: 0xff, 0xff, 0xff, 0xff
chip 0, block 9, page 0, oob: 0xff, 0xff, 0xff, 0xff
chip 0, block 10, page 0, oob: 0xff, 0xff, 0xff, 0xff
chip 0, block 11, page 0, oob: 0xff, 0xff, 0xff, 0xff
[PHY_DBG] can't get right otp value from nand otp blocks, then use otp command
_vender_get_param_otp_hynix time 0!
otp copy 0 is ok!
NFC_LSBExit
[PHY_DBG] repair otp value end
chip 0, block 8, page 0, oob: 0x0, 0x4f, 0x4f, 0x42
find good otp value in chip 0, block 8
Read Retry value Table from nand otp block:
0x2f 0x3e 0x54 0x9d 0x34 0x3e 0x4a 0x93
0x39 0x43 0x58 0x94 0x3e 0x43 0x4e 0x8b
0x37 0x48 0x52 0x93 0x3c 0x47 0x52 0x89
0x35 0x3d 0x4e 0x91 0x3a 0x3e 0x46 0x87
0x31 0x3b 0x4c 0x8d 0x36 0x3c 0x44 0x84
0x2a 0x39 0x4a 0x8b 0x2f 0x3b 0x42 0x83
0x20 0x37 0x48 0x88 0x25 0x3a 0x40 0x7e
0x16 0x21 0x36 0x7c 0x1b 0x21 0x2c 0x72


[SCAN_DBG] ==============Nand Architecture Parameter==============
[SCAN_DBG]    Nand Chip ID:         0xda94dead 0xffffff74
[SCAN_DBG]    Nand Chip Count:      0x1
[SCAN_DBG]    Nand Chip Connect:    0x1
[SCAN_DBG]    Nand Rb Connect Mode:      0x1
[SCAN_DBG]    Sector Count Of Page: 0x10
[SCAN_DBG]    Page Count Of Block:  0x100
[SCAN_DBG]    Block Count Of Die:   0x1000
[SCAN_DBG]    Plane Count Of Die:   0x2
[SCAN_DBG]    Die Count Of Chip:    0x1
[SCAN_DBG]    Bank Count Of Chip:   0x1
[SCAN_DBG]    Optional Operation:   0x1188
[SCAN_DBG]    Access Frequence:     0x28
[SCAN_DBG]    ECC Mode:             0x4
[SCAN_DBG]    Read Retry Type:      0x20708
[SCAN_DBG]    DDR Type:             0x0
[SCAN_DBG] =======================================================

[SCAN_DBG] ==============Optional Operaion Parameter==============
[SCAN_DBG]    MultiPlaneReadCmd:      0x60, 0x60
[SCAN_DBG]    MultiPlaneWriteCmd:     0x11, 0x81
[SCAN_DBG]    MultiPlaneCopyReadCmd:  0x60, 0x60, 0x35
[SCAN_DBG]    MultiPlaneCopyWriteCmd: 0x85, 0x11, 0x81
[SCAN_DBG]    MultiPlaneStatusCmd:    0x70
[SCAN_DBG]    InterBnk0StatusCmd:     0xf1
[SCAN_DBG]    InterBnk1StatusCmd:     0xf2
[SCAN_DBG]    BadBlockFlagPosition:   0x2
[SCAN_DBG]    MultiPlaneBlockOffset:  0x1
[SCAN_DBG] =======================================================
NHW : nand hw scan ok
check nand version start.
Current nand driver version is 0x000000ff 0x00000000 0x00000002 0x00000012
Succeed in getting flash info.
block 0 is cleared block.
block 1 is cleared block.
block 0 is cleared block.
block 1 is cleared block.
can't find valid version info in boot blocks.
VersionCheck end.
[Fed]:To erase boot0 blocks.
Ready to erase boot blocks.
has cleared the boot blocks.
[Fed]:&&This flash NOT need to erase
Ready to scan bad blocks.
nfb phy init ok.
Succeed in getting flash info.
scan CE 0
find defined bad block in chip 0, block 12.
find defined bad block in chip 0, block 4094.
find defined bad block in chip 0, block 4095.
3 bad blocks in CE 0
cal bad block num is 6
cal good block num is 972
good block ratio is 912
[Fed]:get the good blk ratio after hwscan : 912
_RepairLogBlkTbl start
Log Block Index 0, LogicBlockNum: 150, LogBlockType: 0
log0: 156, Log1: ffff, WriteIndex: 0
datablock: 159, lastusedpage: ff
Log Block Index 1, LogicBlockNum: 151, LogBlockType: 0
log0: 157, Log1: ffff, WriteIndex: 0
datablock: 15a, lastusedpage: 7f
Log Block Index 2, LogicBlockNum: 14, LogBlockType: 0
log0: 7f7, Log1: ffff, WriteIndex: 0
datablock: 1d, lastusedpage: ff
Log Block Index 3, LogicBlockNum: 6, LogBlockType: 0
log0: 7f9, Log1: ffff, WriteIndex: 0
datablock: f, lastusedpage: 95
_RepairLogBlkTbl end
get mbr error
[Fed]:erase=0, hasPrivatePart=0.
[Fed]:nand logic size [0x00000000, 0x00e40000]Sec.
[Fed]:-------------------------------------------------
[Fed]:               Byebye, Nand Register.
[Fed]:-------------------------------------------------
FES:INFO : run addr = 0x00000000 , type = 1437204482
FES:---------------------------------------------------
FES:fes_crc   = 0x00000000
FES:media_crc = 0x59c9585d
FES:---------------------------------------------------

mengwei2275

新人求解释啥意思的说。

mengwei2275

为啥每次都是88%

wilsonwan

镜像文件有问题吧?查一下md5是否一致

sencars

排除软件方面没问题的话，说到硬件，在我维修的经验来说，大多是DDR或主控虚焊了。最好用官方的软件烧写固件比较好....

功夫猫

我的也是，不过重试了几次居然写进去了- -

mengwei2275

功夫猫 发表于 2014-5-13 02:34
我的也是，不过重试了几次居然写进去了- -

我的好像是解压的时候损坏了。。。校验了md5，的确不一样。。。