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.

CC2541 TIDA-00096 BLE connectivity problem

Other Parts Discussed in Thread: ADS1293, CC2541, TIDA-00096, CC2540

I have recreated the TIDA-00096 design and am currently in the testing phase of the PCB, more specifically debugging the firmware. I can successfully flash CC2541, the communication with ADS1293 works as well, but I just cannot get the BLE to a working phase. The target is completely hidden from the PC's bluetooth, but will show up at the Android phone. However, it simply won't pair. Depending on the debugging state, it will ask for PIN, but then Android return errors "unable to communicate with ADS1293" or either it won't connect to it (ask for PIN) at all. Actually just recently the Bluetooth connection stopped showing up at the phone at all although I have not changed anything and I really cannot find a reason for that.

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

  • Hi,

    Which phone are you using? I would recommend connecting first with another CC254x device such as with the CC2540 dongle running as the central device. Use BTOOL to connect to it:
    www.ti.com/.../swru270c.pdf

    Best wishes
  • Unfortunately I do not have the CC2540 dongle, only CC debugger.

    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 connections 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.