#1 May 19, 2017 06:40:10

xxd@lsr
Registered: 2017-05-19
Posts: 1
Profile   Send e-mail  

Sable can not scan BLE devices

Chipset: Sable-x
BLE Stack version : BLE-SDK 2.02
Problem description:
Sable-x (TI CC2640) is programmed as BLE observer. It is designed to scan for BLE devices, collect BLE data and then send out data through UART. The system works well for first couple hours (from 4 to 15ish) and then Sable-x stops working. Can send command through UART to Sable when system doesnt work (data observed on MOSI line), but not responding from Sable. No data transmitting is observed on MISO line. The Sable doesnt seem to scan for any devices when this happens, based on testing log, so can not collect data either. Any idea why this is happening?
Any help is appropriated.

BTW, The BLE to UART is based on TI npi function, not LSR serial-to-ble function.

Edited xxd@lsr (May 19, 2017 06:51:04)

Offline

#2 May 19, 2017 16:51:36

SupportEngineer
Registered: 2016-03-11
Posts: 84
Profile   Send e-mail  

Sable can not scan BLE devices

Hello,

In your post you mention that you are observing the MOSI and MISO lines, but you are working with the UART. Can you please clarify this as MOSI and MISO are related to SPI not UART?

Based on the information you have provided it sounds like the module is storing up scan information until the memory fills up and then it stops working.

We recommend that you submit a support request through our support alias, cs-support@lairdtech.com so that we can better track the responses, as we will need to gather more information in order to better assist you with this issue.

Please provide the following information with your support request:
1) Confirm that you are using the TI SDK (Code Composer Studio) to program the module, if not please provide details of which SDK is being used.

2) Provide as much detail as possible about your intended application - what is it that you want to do with the module?

3) Has handshaking been implemented?

As per the TI Wiki: Since TL runs on top of the NPI layer, it uses the same handshaking pins (MRDY and SRDY) used in NPI. This is true for both SPI and UART (with power management). In order to properly manage the power domains of the CC26xx platform, NPI must include a way for an external host to wake the network processor from low power modes. This is done through the inclusion of “master ready”, MRDY, and “slave ready”, SRDY, signals. MRDY is an input pin set by the protocol master will wake the slave device, thus enabling it to receive data over the serial bus. SRDY is an output pin and, when set by the protocol master, signals the slave that it may begin data transfer. This sequence of setting MRDY and SRDY pins comprises a “handshake” process to guarantee both devices are awake and ready to send and/or receive data."

Edited SupportEngineer (May 19, 2017 16:52:29)

Offline

#3 May 19, 2017 17:09:52

SupportEngineer
Registered: 2016-03-11
Posts: 84
Profile   Send e-mail  

Offline

Board footer

Moderator control