• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 305 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

OAD using BLE Device Monitor give a flood of errors and terminates

Eyal Lasko
Expert 2300 points
Other Parts Discussed in Thread: CC2541

Hi, 

I'm trying to OAD using BLE Device Monitor.

I succeed occasionally but most of the time BLE Dev Mon gives tons of errors like the one below and terminate after few seconds....

I'm not sure if its related but when opening the com port after the app is launched,  it also give an error message (but keep working)

I'm using BLE stack V1.4.0, USB dongle (HostTestRelease) and a proprietary sensor based on CC2541.

What could be the reason for this ?

thanks

  • 0
    TI__Expert 4095 points

    1. What version of the BLE Device Monitor are you using?

    2. What is the connection interval? For CC2541 devices it should be at least 20 ms during OAD.

    3. Have you tried the same operation on a CC2541 SensorTag ?

  • 0
    Expert 2300 points

    UPDATE -

    Upgrading to  Device Monitor 2.1.0 seems to solve the problems....

    However, I've noticed that OAD on this latest version shows a bar on the right that (I presume) relates to the memory page(s) being flashed.

    However this bar lists 32 blocks 00000- 1F000 which is 128KB...

    How this is used if one would like to program image larger than 128KB (CC2541) ?

    Thanks

  • 0 in reply to Eyal Lasko
    TI__Expert 4095 points
    This is because the BLE Device Monitor assumes that your device is a CC26xx SensorTag! You can "fool it" by naming your device "SensorTag" while you're developing. Then you will get back the old OAD dialog.