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

LP-EM-CC2340R5: Device discovery by App and in the Bluetooth Settings on an Android and IOS devices not showing in the Settings Bluetooth device list

Itamar Cohen
Intellectual 490 points
Part Number: LP-EM-CC2340R5
Other Parts Discussed in Thread: CC2340R5, , SYSCONFIG

I am in the process of migrating a BLE based product from CC254X to the CC2340R5 platform using the LP-EM-CC2340R5 development board.

Using TI Simple Link Connect App (on both Android and IOS), i can scan for the device running the basic_ble example application, imported from  the simplelink_lowpower_f3_sdk_7_10_00_35 SDK.

The Basic BLE Project is listed in the scanner as it should an I can connect to it with no problem.

However, the  'Basic BLE Project' device  never shows up in the device list provided by the phone Bluetooth Settings, as It does in my CC254X implementation.

Any idea for making the CC2340R5 showing on the phone's Bluetooth device list   ?

 

  • +1
    TI__Expert 5150 points

    Hi,

    Thank you for reaching us,

    First, this behaviour is normal (not seeing the device in your phone scanner), hopefully you can see it on scanner application, so it works.

    Concerning the migration, I think i could be related to the content of the advertisement. Your phone filter all the device advertising on a specific way. It could be nice to compare both advertisements to know on which parameters our phone is filtering the device.

    Unfortunately I cannot say precisely which one is problematic for phone bluetooth scanner, maybe try to compare it also with the TI simpleLink Connect app.

    Regards,

  • 0 in reply to Guillaume
    Intellectual 490 points

    Hi  Guillaume3

    Not the answer I expected:-)

    Fortunately I investigated the issue farther and found out that if adding a Service Solicitation field to the advertising data, AND (on IOS) the service is actually available on the scanning device (ex. phone), the advertising  device will be listed in the Bluetooth Settings as available device.

    Looks like on Android just adding the Service Solicitation field is enough to get the advertising device listed on the scanner.

    here is the code produced by sysConfig after adding Service Solicitaion is SysConfig

    uint8_t advData1[] =
    {
    0x02,
    GAP_ADTYPE_FLAGS,
    GAP_ADTYPE_FLAGS_GENERAL,

    0x03,
    GAP_ADTYPE_16BIT_MORE,
    LO_UINT16(0xfff0),
    HI_UINT16(0xfff0),

    0x03,
    GAP_ADTYPE_SERVICES_LIST_16BIT,
    // Service Solicitation 16-bit - UUID 0
    LO_UINT16(0x1805),
    HI_UINT16(0x1805),

    };

    In my case the Service Solicitation is the  Current Time Service (CTS) with the standard ID : 0x1805

    All IOS devices (I checked so far ) have this service built-in. 

    In theory, the scanning device should automatically connect to the advertising device, in case it has the service available. However until now it didn't.

    Does this makes sense ?