• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 592 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/CC2640R2F: BLE Connection drops on characteristic writes ONLY when debugger is connected (no WriteRsp)

KBurchMS
Intellectual 500 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2540

Tool/software: Code Composer Studio

Device: CC2640R2F LaunchPad

CCS Version: 7.1.0.00016 

BLE SDK 1.35.00.33 for CC26040R2 LaunchPad

BLE Device Monitor 2.5.0 with attached CC2540 USB dongle with HostTestApp programmed (Central device)

I have an example application similar to the SimplePeripheral app project loaded on my CC2640R2F Launchpad board, connected via BLE device monitor using a CC2540 USB dongle as the central. I can make a connection and do discovery with my debugger connected and without my debugger connected. However, when trying to write to characteristic values, if I have my debugger (the onboard launchpad USB debugger) connected and running the application and I write to a characteristic, I see that I dont get a Write Response back in the BLE device monitor (I get a "WriteRsp failed" popup), and my BLE connection drops. When my debugger is not connected, I receive the write response just fine and everything seems to work correctly.

Has anyone experienced this? Does anyone know why the write responses dont work correctly only when the debugger is connected? Thanks

  • 0
    TI__Guru* 82341 points
    Hi,

    I don't know why this would happen. Which characteristic are you writing to?

    Can you describe your set-up when the debugger is not connected? E.g. which jumpers you have removed?
  • 0 in reply to Marie H
    Intellectual 500 points

    Hi Marie,

    It happens when I write to any characteristic. It actually seems as though its tied to System_* module calls such as System_prints and System_flush. I added the inclusion of the SysMin module for debug prints to the console. It should be noted that it only takes one print and flush to seem to trigger it - its not like im doing heavy logging of any sort... just a "Char write CB triggered" type of print.

    When I dont have the debugger connected, I simply mean all of the HW is the same (same jumpers + powered VIA USB), but CCS is not in an active debug session (after I hit "stop", but the application is still running without the debug session). 

    Thanks

    Kris

  • 0 in reply to KBurchMS
    TI__Guru* 82341 points
    Hi,

    Can you try to reproduce by writing from your phone? (using e.g. Light Blue or BLE Scanner app?)