TI中文支持网
TI专业的中文技术问题咨询交流网站

使用BTOOL工具升级时,总是失败,这是什么原因?麻烦帮我分析下!

cc2642r1  sdk: simplelink_cc13x2_26x2_sdk_3_40_00_02   

设备原有固件:simple_peripheral_oad_onchip

设备新的升级固件:project_zero

在连接成功后,按下send按钮,运行到一定的时候,出现OAD Download Not Successful

log如下:

——————————————————————–
[59] : <Rx> – 11:26:59.702
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x0B (11) bytes(s)
Event : 0x0607 (1543) (GAP_LinkParamUpdate)
Status : 0x00 (0) (SUCCESS)
ConnHandle : 0x0000 (0)
ConnInterval : 0x0006 (6)
ConnLatency : 0x0000 (0)
ConnTimeout : 0x0032 (50)
Dump(Rx):
0000:04 FF 0B 07 06 00 00 00 06 00 00 00 32 00 …………2.
——————————————————————–
[60] : <Info> – 11:27:01.207
Device Disconnected
Handle = 0x0000
Addr Type = 0x00 (ADDRTYPE_PUBLIC)
BDAddr = 58:93:D8:A4:B7:05
——————————————————————–
[61] : <Rx> – 11:27:01.202
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x06 (6) bytes(s)
Event : 0x0606 (1542) (GAP_TerminateLink)
Status : 0x00 (0) (SUCCESS)
ConnHandle : 0x0000 (0)
Reason : 0x08 (8) (SUPERVISION_TIMEOUT_TERM)
Dump(Rx):
0000:04 FF 06 06 06 00 00 00 08 ………
——————————————————————–
[62] : <Info> – 11:27:12.721
Establish Connection
——————————————————————–
[63] : <Tx> – 11:27:12.724
-Type : 0x01 (Command)
-OpCode : 0xFE62 (GapInit_connect)
-Data Length : 0x0A (10) byte(s)
PeerAddrType : 0x00 (0) (PEER_ADDRTYPE_PUBLIC_OR_PUBLIC_ID)
PeerAddr : 58:93:D8:A4:B7:05
InitiatingPhy : 0x01 (1) (
INIT_PHY_1M)
Timeout : 0x0000 (0)
Dump(Tx):
0000:01 62 FE 0A 00 05 B7 A4 D8 93 58 01 00 00 .b……..X…
——————————————————————–
[64] : <Rx> – 11:27:12.749
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x06 (6) bytes(s)
Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
Status : 0x00 (0) (SUCCESS)
OpCode : 0xFE62 (GapInit_connect)
DataLength : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 62 FE 00 ……b..
——————————————————————–
[65] : <Rx> – 11:27:12.819
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x14 (20) bytes(s)
Event : 0x0605 (1541) (GAP_EstablishLink)
Status : 0x00 (0) (SUCCESS)
DevAddrType : 0x00 (0) (ADDRTYPE_PUBLIC)
DevAddr : 58:93:D8:A4:B7:05
ConnHandle : 0x0000 (0)
ConnRole : 0x08 (8) (
Central)
ConnInterval : 0x0050 (80)
ConnLatency : 0x0000 (0)
ConnTimeout : 0x07D0 (2000)
ClockAccuracy : 0x00 (0)
Dump(Rx):
0000:04 FF 14 05 06 00 00 05 B7 A4 D8 93 58 00 00 08 …………X…
0010:50 00 00 00 D0 07 00 P……
——————————————————————–
[66] : <Tx> – 11:27:12.820
-Type : 0x01 (Command)
-OpCode : 0x2022 (HCI_LE_SetDataLength)
-Data Length : 0x06 (6) byte(s)
Handle : 0x0000 (0)
TxOctets : 0x00FB (251)
TxTime : 0x0848 (2120)
Dump(Tx):
0000:01 22 20 06 00 00 FB 00 48 08 ." …..H.
——————————————————————–
[67] : <Info> – 11:27:12.855
Device Connected
Handle = 0x0000
Addr Type = 0x00 (ADDRTYPE_PUBLIC)
BDAddr = 58:93:D8:A4:B7:05
——————————————————————–
[68] : <Rx> – 11:27:12.849
-Type : 0x04 (Event)
-EventCode : 0x000E (HCI_CommandCompleteEvent)
-Data Length : 0x06 (6) bytes(s)
Packets : 0x01 (1)
OpCode : 0x2022 (HCI_LE_SetDataLength)
Status : 0x00 (0) (SUCCESS)
Handle : 0x0000 (0)
Dump(Rx):
0000:04 0E 06 01 22 20 00 00 00 …." …
——————————————————————–
[69] : <Info> – 11:27:12.869
Restore Connection Parameters
——————————————————————–
[70] : <Info> – 11:27:12.884
Image Service Discovery
——————————————————————–
[71] : <Info> – 11:27:12.887
Image Service Discovery
——————————————————————–
[72] : <Tx> – 11:27:12.870
-Type : 0x01 (Command)
-OpCode : 0x2016 (HCI_LEReadRemoteUsedFeatures)
-Data Length : 0x02 (2) byte(s)
Handle : 0x0000 (0)
Dump(Tx):
0000:01 16 20 02 00 00 .. …
——————————————————————–
[73] : <Info> – 11:27:12.893
OAD Send UUID Discovery
——————————————————————–
[74] : <Tx> – 11:27:12.895
-Type : 0x01 (Command)
-OpCode : 0xFD86 (GATT_DiscPrimaryServiceByUUID)
-Data Length : 0x12 (18) byte(s)
ConnHandle : 0x0000 (0)
Value : 00:00:00:00:00:00:00:B0:00:40:51:04:C0:FF:00:F0
Dump(Tx):
0000:01 86 FD 12 00 00 00 00 00 00 00 00 00 B0 00 40 ……………@
0010:51 04 C0 FF 00 F0 Q…..
——————————————————————–
[75] : <Rx> – 11:27:12.929
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x06 (6) bytes(s)
Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
Status : 0x00 (0) (SUCCESS)
OpCode : 0xFD86 (GATT_DiscPrimaryServiceByUUID)
DataLength : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 86 FD 00 ………
——————————————————————–
[76] : <Rx> – 11:27:13.119
-Type : 0x04 (Event)
-EventCode : 0x003E (HCI_LE_GenericReportEvent)
-Data Length : 0x0C (12) bytes(s)
LE Event Code : 0x04 (4) (HCI_LE_ReadRemoteUsedFeaturesCompleteEvent)
LE Event Code : 0x04 (4) (HCI_LE_ReadRemoteUsedFeaturesCompleteEvent)
Status : 0x00 (0) (SUCCESS)
ConnectionId : 0x0000 (0)
Features : 0x00000000000059FF (23039) (
Encryption
Connection_Parameters_Request
Reject_Extended_Indication
Slave_Features_Exchange
Ping
Data_Packet_Length_Extension
Privacy
Extended_Scanner_Filter_Policies
PHY_2M
Coded_PHY
Extended_Advertising
Channel_Selection_Algorithm_2)
Dump(Rx):
0000:04 3E 0C 04 00 00 00 FF 59 00 00 00 00 00 00 .>……Y……
——————————————————————–
[77] : <Rx> – 11:27:13.219
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x0A (10) bytes(s)
Event : 0x0501 (1281) (ATT_ErrorRsp)
Status : 0x00 (0) (SUCCESS)
ConnHandle : 0x0000 (0)
PduLen : 0x04 (4)
ReqOpCode : 0x06 (ATT_FindByTypeValueReq)
Handle : 0x0001 (1)
ErrorCode : 0x0A (10) (ATTR_NOT_FOUND)
Dump(Rx):
0000:04 FF 0A 01 05 00 00 00 04 06 01 00 0A ………….
——————————————————————–
[78] : <Info> – 11:27:13.239
OAD – Restore Connection Settings
——————————————————————–
[79] : <Error> – 11:27:13.241
OAD Download Not Successful
——————————————————————–
[80] : <Tx> – 11:27:13.226
-Type : 0x01 (Command)
-OpCode : 0xFE11 (GAP_UpdateLinkParamReq)
-Data Length : 0x0A (10) byte(s)
ConnHandle : 0x0000 (0)
IntervalMin : 0x0006 (6)
IntervalMax : 0x0006 (6)
ConnLatency : 0x0000 (0)
ConnTimeout : 0x0032 (50)
Dump(Tx):
0000:01 11 FE 0A 00 00 06 00 06 00 00 00 32 00 …………2.
——————————————————————–
[81] : <Tx> – 11:27:13.243
-Type : 0x01 (Command)
-OpCode : 0x2016 (HCI_LEReadRemoteUsedFeatures)
-Data Length : 0x02 (2) byte(s)
Handle : 0x0000 (0)
Dump(Tx):
0000:01 16 20 02 00 00 .. …
——————————————————————–
[82] : <Rx> – 11:27:13.269
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x06 (6) bytes(s)
Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
Status : 0x00 (0) (SUCCESS)
OpCode : 0xFE11 (GAP_UpdateLinkParamReq)
DataLength : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 11 FE 00 ………
——————————————————————–
[83] : <Rx> – 11:27:13.280
-Type : 0x04 (Event)
-EventCode : 0x003E (HCI_LE_GenericReportEvent)
-Data Length : 0x0C (12) bytes(s)
LE Event Code : 0x04 (4) (HCI_LE_ReadRemoteUsedFeaturesCompleteEvent)
LE Event Code : 0x04 (4) (HCI_LE_ReadRemoteUsedFeaturesCompleteEvent)
Status : 0x00 (0) (SUCCESS)
ConnectionId : 0x0000 (0)
Features : 0x00000000000059FF (23039) (
Encryption
Connection_Parameters_Request
Reject_Extended_Indication
Slave_Features_Exchange
Ping
Data_Packet_Length_Extension
Privacy
Extended_Scanner_Filter_Policies
PHY_2M
Coded_PHY
Extended_Advertising
Channel_Selection_Algorithm_2)
Dump(Rx):
0000:04 3E 0C 04 00 00 00 FF 59 00 00 00 00 00 00 .>……Y……
——————————————————————–
[84] : <Tx> – 11:27:13.280
-Type : 0x01 (Command)
-OpCode : 0xFE11 (GAP_UpdateLinkParamReq)
-Data Length : 0x0A (10) byte(s)
ConnHandle : 0x0000 (0)
IntervalMin : 0x0050 (80)
IntervalMax : 0x0050 (80)
ConnLatency : 0x0000 (0)
ConnTimeout : 0x07D0 (2000)
Dump(Tx):
0000:01 11 FE 0A 00 00 50 00 50 00 00 00 D0 07 ……P.P…..
——————————————————————–
[85] : <Rx> – 11:27:13.319
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x06 (6) bytes(s)
Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
Status : 0x00 (0) (SUCCESS)
OpCode : 0xFE11 (GAP_UpdateLinkParamReq)
DataLength : 0x00 (0)
Dump(Rx):
0000:04 FF 06 7F 06 00 11 FE 00 ………
——————————————————————–
[86] : <Rx> – 11:27:14.819
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x0B (11) bytes(s)
Event : 0x0607 (1543) (GAP_LinkParamUpdate)
Status : 0x00 (0) (SUCCESS)
ConnHandle : 0x0000 (0)
ConnInterval : 0x0006 (6)
ConnLatency : 0x0000 (0)
ConnTimeout : 0x0032 (50)
Dump(Rx):
0000:04 FF 0B 07 06 00 00 00 06 00 00 00 32 00 …………2.
——————————————————————–
[87] : <Rx> – 11:27:18.836
-Type : 0x04 (Event)
-EventCode : 0x000E (HCI_CommandCompleteEvent)
-Data Length : 0x06 (6) bytes(s)
Packets : 0x01 (1)
OpCode : 0x2020 (HCI_LE_RemoteConnectionParameterRequestReply)
Status : 0x00 (0) (SUCCESS)
Handle : 0x0000 (0)
Dump(Rx):
0000:04 0E 06 01 20 20 00 00 00 …. …
——————————————————————–
[88] : <Rx> – 11:27:18.926
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x0B (11) bytes(s)
Event : 0x0607 (1543) (GAP_LinkParamUpdate)
Status : 0x00 (0) (SUCCESS)
ConnHandle : 0x0000 (0)
ConnInterval : 0x0320 (800)
ConnLatency : 0x0000 (0)
ConnTimeout : 0x0258 (600)
Dump(Rx):
0000:04 FF 0B 07 06 00 00 00 20 03 00 00 58 02 …….. …X.
——————————————————————–

Susan Yang:

我会在测试后给您回复,请等待一下,谢谢

Viki Shi:

请按照academy操作一下,看Btool使用是否正常:
dev.ti.com/…/node

user5203601:

回复 Susan Yang:

 请问测试过了吗?btool 总是提示:OAD  Invalidate  Image on startreset;是固件哪里的设置不对吗?

详细 如图

Viki Shi:

回复 user5203601:

invalidata image,是不是CRC校验没过?请问academy测试是否正常?

user5203601:

回复 Viki Shi:

academy测试正常的

user5203601:

回复 user5203601:

从上面的图片可以看出,crc: valid这个是校验正确的

Viki Shi:

回复 user5203601:

确实是,刚才疏忽了。那问题应该在OAD reset service这块。
The OAD reset service is only used by on-chip OAD solutions. It implements a method for switching/invalidating the currently running image and resetting the device. This must occur because in on-chip solutions the currently running image cannot update itself. More information about the on-chip OAD process will be covered in the on-chip OAD chapter. Figure 92. shows an overview of the OAD reset service and its characteristics. Like the OAD service, the reset service uses the 128 bit TI base UUID with a 16 bit short UUID of 0xFFD0.

The OAD Start/Reset Characteristic is responsible for starting the OAD process or resetting the target device. The size of the characteristic payload is 1 byte. The OAD Process can be initiated by writing ‘1’ to this characteristic. The target device can be reset by writing ‘0’ to this characteristic.

user5203601:

回复 Viki Shi:

您好,BTOOL进行OAD时,提示invalidata image,是不是因为设备的固件不是persistant app image导致的?请问下persistant app image,需要怎么制作?

Viki Shi:

回复 user5203601:

建议看一下这边的文档:dev.ti.com/…/ble5-oad-index-cc13x2_26x2.html

user5203601:

回复 Viki Shi:

这个文档我看了,也按照这个设置了一些HEADER,但还是不行,您能zhi制作一个persistant app image测试固件给我测试一下吗(CC2642R1)?

赞(0)
未经允许不得转载:TI中文支持网 » 使用BTOOL工具升级时,总是失败,这是什么原因?麻烦帮我分析下!
分享到: 更多 (0)