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

TIDA-00096 BLE connectivity problem

vix3c
Intellectual 430 points
Other Parts Discussed in Thread: ADS1293, CC2541, TIDA-00096

I have recreated the TIDA-00096 design and am currently in the testing phase of the PCB and the firmware. I can successfully flash the firmware to CC2541, the communication with ADS1293 supposedly works as well, but I just cannot get the BLE to a working phase. 

After some debugging and testing, I have found out, that if I flash SimpleBLEPeripheral, my PC will find, pair and connect with the target (TIDA-00096). However if I flash the firmware that is provided for TIDA-00096, PC and Android 4.1.2 based phone won't find any Bluetooth devices at all.
Android 6.0 phone will however now see the target by name "ADS1293 ECG Wireless Demo" and also ask for PIN (which is 000000 as far as I know), when I try to connect to it. It will then usually return error "Unable to communicate with ADS1293, please make sure that the device is ready to pair" error in the 1st/2nd try, but in the 3rd try, it will finally add it to "Paired devices" list, however it won't state "connected" status.

I was wondering what may be the cause for this and how to find a solution?

  • 0
    TI__Guru* 92715 points
    vix3c,


    I've moved this post to the Bluetooth Low Energy Forum. I believe this forum will best help you get an answer to your question.


    Joseph Wu
  • 0
    Intellectual 430 points
    After additional testing with BlueTerm (Android terminal app for Android), I have found out that the Android cannot establish a connection with the target device. In order to diagnose the problem, I have then debugged firmware thoroughly. I have found out, that the firmware will jump into "connected" state for a tiny bit of a moment, but will disconnect right after and return to "advertising" mode. Connection thus cannot be established. I have been trying to find a solution for a while, but without any success. I have also read all the relevant threads on E2E forums and actually found some very related ones with the same/similar problems, such as e2e.ti.com/.../1827528 , e2e.ti.com/.../160620 or e2e.ti.com/.../441130 , but there does not seem to be any working solutions posted in there.