• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 486 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.

CC2650DK Discovery Information Service data bad using BLE-STACK-2.1

Tosa
Expert 1340 points
Other Parts Discussed in Thread: CC2650

I have a CC2650DK. I'm using BLE-STACK-2.1. If I upload the SimpleBLEPeripheral output to one of the CC2650 evaluation modules, the Device Information Service data is okay (per the Android app). However, the other module gives corrupt data. If I use BLE-STACK-2.0 on this bad module, the data is okay. How do I resolve this?

  • 0
    TI__Guru** 105180 points
    Hello,

    What does "corrupt data" mean in this context? Did you check the results with BTool or a BLE air sniffer? Are you using a pre-built hex file or building and downloading the code yourself with custom data? How are you programming the module / download code?

    Best wishes
  • 0 in reply to JXS
    Expert 1340 points

    I used the example SimpleBLEPeripheral projects without modification (just build and run). "corrupt data" meant that the value displayed by the Android app for various characteristics (Manufacturer Name String, etc) wasn't showing properly as "Manufacturer Name" but rather "p(*" or some jibberish. Power cycling or cycling BT off/on on the Android tablet seems to resolve this.

    I think this is because the stack changed (v2.0 to v2.1 or vice versa) and the Android tablet retained some information of the peripheral with the previously flashed stack. This was proven by flashing both modules with v2.0 and then v2.1 without cycling the tablet. Between stack changes, the data would show up incorrectly on the tablet.

    Anyhow, thanks for your response JXS!