This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/CC2640R2F: SimpleLink SDK Explorer" on Android mobile never seen any OAD transfer's

Part Number: CC2640R2F


Tool/software: TI-RTOS

Hi Team ,

Subject : To perform firmware updates over BLE(OAD) via a mobile device to send the firmware to the CC2640R2F eval board Flash.

Software Version : 2_30_00_28 

If  I am using LAUNCHXL-CC2604R2F eval board as the OAD Downloader, my on-chip OAD is successful all the time .

If I am using "SimpleLink SDK Explorer" on Android mobile I never seen any OAD transfer's . Can you let me know why this mobile app is not working . 

Any help in this regard would be appreciated . 

  • Hi,

    Could be the connection parameters or other limiting factors in the smartphone bluetooth chipset. Do you know the parameters used by the Android?

  • Hi Joakim ,

    I doesn't know the parameters used by the android , But the "SimpleLink SDK Explorer" was developed by TI and available in Android mobile phone "play store" app.

    Note:If I use the hex file "cc2640r2lp_host_test.hex"  on LAUNCHXL-CC2604R2F eval board , able to transfer the bin file Over The Air .

  • Hi,

    Yes I know we developed the app, but the Bluetooth chipset in the phone varies over models and some doesn't expose full functionality to the app. Have you tried multiple vendors?

  • Hi ,

    The below git source help me to transfer bin file from mobile phone to the CC2640R2F device .

    http://git.ti.com/simplelink-ble-oad-android 

    But the problem is its working with few smart-phone(like nokia , LG ) and not at all working with other smart-phone (like lenovo and moto).

    Could you let me know the condition for not working with other smart phones . Is it something with BLE version ? 

  • Hi,

    The various BT chipset in phones supports different amount packets per connection events for example, furthermore it's often a combo-chip and has to share resources with WiFi. There is nothing we can do than complying to the spec in order to ensure interoperability, but sometimes that is not enough and applications is in need of tuning to support all use cases..

    Many Bluetooth low energy products state what phones and OS versions they are compatible with. This does not have anything to do with our SDK or the HW, it has to do with the use case and expected behaviour.