自制firefly-rk3288板子第一次烧录固件多次失败求建议

buhui912 发表于 2015-5-21 16:40:36

我们项目组参考firefly-rk3288自己做的板子，只有pmic用的rk808，其他和firefly的硬件设计都一样。
现在插上usb-otg线，板子开机后，androidtools能正常识别为maskrom设备，但是烧写固件时，androidtools工具上老是在死在
下载IDB失败这一步，串口控制台上老是不断出现SDM_Read error=XXX ret=20信息。
然后我试着先擦除FLASH，但是androidtools工具上和串口控制台上的错误信息都和前面一样，最后老是卡在
不断出现SDM_Read error=XXX ret=20信息。

这是一次烧写失败的串口Log记录：（最后的SDM_Read error=XXX ret=20信息我知道非常有用，但是这一部分代码我也看不到，想请教下版主或者你们firefly-rk3288的原开发者，估计肯定也会碰到这个提示信息，这个提示信息是什么意思或者如果是USB信号的不好或者emmc的不好，有什么思路去解决啊？谢谢）

DDR Version 1.00 20141007
In
Channel a: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel b: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Memory OK
Memory OK
OUT
serial_init 0
ChipType = 8
SDC_BusRequest:CMD=8 DATA BUSY1615
SDC_BusRequest:CMD=8 DATA BUSY1615
SDC_BusRequest:CMD=8 DATA BUSY1615
SdmmcInit=0 400
...FlashInit enter...
FtlMallocOffset = 8040 8000
FtlMallocOffset = 10040 8000
FtlMallocOffset = 11040 1000
FtlMallocOffset = 19040 8000
FtlMallocOffset = 1a040 1000
1:200 0 7f7f05 22
...NandcInit enter...
0:1200 0 7f7f05 22
gNandcVer = 6
SDC_BusRequest:CMD=8SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=8SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=8SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=5SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=5SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=5SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=55SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=55SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=55SDC_RESP_TIMEOUT 1784
mmc Ext_csd, ret=0 ,
Ext=10, bootSize=1000,
Ext=0, Ext=e9, Ext=0, Ext=0,cap =e90000
SDC_BusRequest:CMD=19SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=14SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=19SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=14SDC_RESP_TIMEOUT 1784
SdmmcInit=2 0
BootCapSize=1000
UserCapSize=e90000
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
FwPartOffset=2000 , 0
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=1f80 ret=20
UsbHook 20638386
powerOn 20639946
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=440 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=840 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=c40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=1040 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=40 ret=20
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Write error=40 ret=20
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Write error=440 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=440 ret=20
SDC_BusRequest:CMD=23SDC_RESP_TIMEOUT 1784
SDC_BusRequest:CMD=13SDC_RESP_TIMEOUT 1784
SDM_Read error=440 ret=20

buhui912 发表于 2015-5-21 16:48:32

再发一个LOG：（是android tool烧录工具的Log，下面的错误信息也估计有助于解决第一次烧录失败的问题）

5:18:36 559 Android开发工具 v2.3.3.0 start run
15:20:17 641 Layer<1-1-2>:下载Boot开始
15:20:20 095 Layer<1-1-2>:下载Boot成功
15:20:20 098 Layer<1-1-2>:等待Maskrom开始
15:20:21 047 Layer<1-1-2>:等待Maskrom成功
15:20:21 049 Layer<1-1-2>:测试设备开始
15:20:40 132 Layer<1-1-2>:测试设备成功
15:20:40 135 Layer<1-1-2>:获取FlashInfo开始
15:20:40 154 <LAYER 1-1-2> INFO:FlashInfo: 00 00 E9 00 00 04 04 00 28 00 01
15:20:40 157 Layer<1-1-2>:获取FlashInfo成功
15:20:40 159 Layer<1-1-2>:准备IDB开始
15:20:40 169 <LAYER 1-1-2> INFO:CS(1) (7456MB) (SAMSUNG)
15:23:57 487 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:23:59 443 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:24:01 397 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:24:03 435 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:24:05 471 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:24:05 476 Layer<1-1-2>:准备IDB成功
15:24:05 480 Layer<1-1-2>:擦除Flash开始
15:24:34 321 Layer<1-1-2>:擦除Flash成功
15:27:49 762 <LAYER 1-1-2> INFO:BufferWriteBack-->Crc is zero
15:27:49 768 Layer<1-1-2>:重启设备开始
15:27:50 772 Layer<1-1-2>:重启设备成功
15:32:10 308 Layer<1-1-2>:下载Boot开始
15:32:12 747 Layer<1-1-2>:下载Boot成功
15:32:12 748 Layer<1-1-2>:等待Maskrom开始
15:32:13 657 Layer<1-1-2>:等待Maskrom成功
15:32:13 658 Layer<1-1-2>:测试设备开始
15:32:33 735 Layer<1-1-2>:测试设备成功
15:32:33 738 Layer<1-1-2>:校验芯片开始
15:32:33 741 Layer<1-1-2>:校验芯片成功
15:32:33 744 Layer<1-1-2>:获取FlashInfo开始
15:32:33 745 <LAYER 1-1-2> INFO:FlashInfo: 00 00 E9 00 00 04 04 00 28 00 01
15:32:33 749 Layer<1-1-2>:获取FlashInfo成功
15:32:33 752 Layer<1-1-2>:准备IDB开始
15:32:33 753 <LAYER 1-1-2> INFO:CS(1) (7456MB) (SAMSUNG)
15:35:50 881 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:35:52 925 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:35:54 971 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:35:56 932 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:35:58 893 <LAYER 1-1-2> INFO:FindBackupBuffer-->No Found Tag
15:35:58 896 Layer<1-1-2>:准备IDB成功
15:35:58 898 Layer<1-1-2>:下载IDB开始
15:36:03 917 Error:RKU_Read-->ReadFile failed,bRet=1,err=0,size=13,read=0
15:36:05 919 INFO:RKU_ResetPipe-->DeviceIoControl OK
15:36:10 920 Error:RKU_Write-->WriteFile failed,bRet=1,err=0,size=31,write=0
15:36:10 920 <LAYER 1-1-2> ERROR:WriteIDBlock-->RKU_WriteSector failed,RetCode(-3)
15:36:16 569 INFO:RKU_ResetPipe-->DeviceIoControl OK
15:36:21 569 Error:RKU_Read-->ReadFile failed,bRet=1,err=0,size=13,read=0
15:36:21 570 <LAYER 1-1-2> ERROR:WriteIDBlock-->RKU_WriteSector-->RKU_EraseBlock failed,RetCode(-4)
15:36:21 574 Error:Layer<1-1-2>:下载IDB失败
15:36:25 655 Error:RKU_Read-->ReadFile failed,bRet=1,err=0,size=2112,read=1600
15:36:27 657 INFO:RKU_ResetPipe-->DeviceIoControl OK
15:36:27 659 Error:RKU_Read-->ReadFile failed,bRet=1,err=0,size=2112,read=13
15:36:27 659 <LAYER 1-1-2> ERROR:FindIDBlock-->RKU_ReadSector failed,RetCode(-4)
15:36:27 660 <LAYER 1-1-2> INFO:BufferWriteBack-->Crc is zero
15:54:59 474 Android开发工具 v2.3.3.0 start run
16:04:39 748 Android开发工具 v2.3.3.0 start run

zhansb 发表于 2015-5-22 09:27:15

firefly-rk3288调试没有遇到这种情况

mb16 发表于 2015-5-22 11:08:59

楼主..同病相怜啊...要是能找到解决方法分享下啊...也希望哪位开发者遇到过同样问题的能给个解决方法啊....:(

buhui912 发表于 2015-5-22 15:26:52

已经解决，好痛苦啊，原来是EMMC供电vcc选错了。

mb16 发表于 2015-5-22 15:34:11

buhui912 发表于 2015-5-22 15:26
已经解决，好痛苦啊，原来是EMMC供电vcc选错了。

怎么个选错？一路3.3V一路1.8啊难道你是对反接了？

叫我锋哥 发表于 2015-5-23 10:37:14

IDB一般都是主控或者FLASH的问题

cb_cb 发表于 2015-5-30 09:37:56

貌似RK自己都不搞808+3288的配合了吧？现在主流的是8846+3288，或818+3288

buhui912 发表于 2015-6-5 15:01:30

cb_cb 发表于 2015-5-30 09:37
貌似RK自己都不搞808+3288的配合了吧？现在主流的是8846+3288，或818+3288

为什么啊，808+3288配合会出什么样的错误啊，我们的项目用的还是这个配合。

屋里人 发表于 2016-4-14 18:36:55

请教下楼主，flash怎么擦除？一直死在准备IDB失败。

页: [1] 2

Firefly开源社区's Archiver

自制firefly-rk3288板子第一次烧录固件多次失败求建议