Hi,
I am using BTool to OAD into a CC2640 custom board which implements OAD Target image A.
When I open a bin file with valid metadata generated by oad_image_tool.py and try to send it, BTool always send the wrong metadata and OAD image gets rejected.
Why is this happening?
I tried the steps given here.
-------------------------------------------------
Important:
In all the .bat files, which uses oad_image_tool.py script to generate unified hex file, app_name was assigned to "oad_target_cc2650lp" but I changed it to "oad_target_cc2650em" to match with my project.
I don't think that'd be the problem, right??
-------------------------------------------------
No issues with metadata anymore and OAD_Target_Image_A broadcasts perfectly.
But when connected through BTool and CC2650 USB Dongle, it automatically disconnects after a few seconds (before even initiating the OAD process).
It gets stuck at step "OAD Send UUID Info Discovery" for few seconds, then gets disconnected and shows "OAD Download Not Successful".
Disconnection is random and does not depend on any ongoing process. I searched online and it seems that my BTool version does not match with the firmware in my CC2650 USB Dongle.
I have "ble_sdk_2_02_01_18" and I have downloaded the host_text hex file from the same SDK version. As there's no OAD option in the btool installed at "ble_sdk_2_02_01_18\tools\btool.exe" I am using the btool installed at "C:\ti\simplelink_cc2640r2_sdk_1_35_00_33\tools\blestack\btool".
Is this the problem?
Hey,
Just realized problem is whenever BTool receives 11 Bytes (follow the screenshot) from OAD Target, it gets stuck immediately. Normally, it receives 10 bytes and then 6 bytes during the OAD process.
Not able to understand why is this happening??
Any idea?
Hello,
Do you have a CC2650 Launchpad that we can use to confirm that your tools (BTOOL with CC2540 dongle) are working correctly?
This is my oad_target_cc2650lp_unified.hex (to be loaded into the CC2650 LP using Flash Programmer 2)
This is my simple_peripheral_cc2650lp_img_b.bin (to be used with btool v1.41.17 for the OAD)
As soon as we confirm that your tools are working correctly, we can look into your code / python scripts.
Best regards,
David
Hi,
We solved the BLE being disconnected issue by changing the connection parameters to following:
/********************************************************************* * CONSTANTS */ // Advertising interval when device is discoverable (units of 625us, 160=100ms) #define DEFAULT_ADVERTISING_INTERVAL 80 // Limited discoverable mode advertises for 30.72s, and then stops // General discoverable mode advertises indefinitely #define DEFAULT_DISCOVERABLE_MODE GAP_ADTYPE_FLAGS_GENERAL // Minimum connection interval (units of 1.25ms, 80=100ms) if automatic // parameter update request is enabled #define DEFAULT_DESIRED_MIN_CONN_INTERVAL 1024 // Maximum connection interval (units of 1.25ms, 800=1000ms) if automatic // parameter update request is enabled #define DEFAULT_DESIRED_MAX_CONN_INTERVAL 2048 // Slave latency to use if automatic parameter update request is enabled #define DEFAULT_DESIRED_SLAVE_LATENCY 0 // Supervision timeout value (units of 10ms, 1000=10s) if automatic parameter // update request is enabled #define DEFAULT_DESIRED_CONN_TIMEOUT 100 // Whether to enable automatic parameter update request when a connection is // formed #define DEFAULT_ENABLE_UPDATE_REQUEST GAPROLE_LINK_PARAM_UPDATE_INITIATE_APP_PARAMS // Connection Pause Peripheral time value (in seconds) #define DEFAULT_CONN_PAUSE_PERIPHERAL 1 // How often to perform periodic event (in msec) #define OTA_PERIODIC_EVT_PERIOD 20 // The size of an OAD packet. #define OAD_PACKET_SIZE ((OAD_BLOCK_SIZE) + 2) // Task configuration #define OTA_TASK_PRIORITY 1 #ifndef OTA_TASK_STACK_SIZE #define OTA_TASK_STACK_SIZE 644 #endif // Internal Events for RTOS application #define OAD_STATE_CHANGE_EVT 0x0001 /*--------------------------------------------------------------------------------------------------------------*/
For Now, OAD from BTool is working smooth and perfect but with we're still facing the same issue with Android.
We're following this repo : https://git.ti.com/ble-oad-android-source-code/ble-oad-android-source-code
We've already cloned and built the repo but somehow we ended up getting the following error every time (Even after trying with hex file you sent).
Please look into the issue ASAP. We want to start the production immediately.
