• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 452 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.

CC2340R5: CC2340R5

Di Wu
Prodigy 30 points
Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG, ENERGYTRACE

Tool/software:

Dear Supporter,

It looks the CC2340R5 running the Basic Ble example is not visible from 5.3 center device.

I am running the Basic Ble example with the following tools:

- Simplelink Low Power F3 SDK 8.10.01.02

- CCS Theia140

When scan and connect from old center device (my 6-years old laptop and iPhone with smart-connnect), everything looks fine.  But I want to test the 5.x feature and the 2M PHY, hence I bought two BLE USB doggles from different brands and the one I am currently using now is a Realtek 5.3.  With any of these 5.3 center device, my CC2340R5 is invisible, I did not see them appear from the scan results.  I thought that the 5.3 centers were using Extended Scan, then I enabled the "Extended Advertising Feature" in the Sys Config, but my device still not visible and in the changed setup, even the old controllers does not see them from the scan results.

What's could be possible cause of the issue? How can I use the 5.3 feature as well as 2M PHY?

Thanks in adance.

woody

  • 0
    TI__Intellectual 2230 points

    Hi Di, 

    Thanks for reaching out. 

    Have you tried to run this using the CCS offline with the relevant SimpleLink software development kit locally? Please download our latest SDK v8.10 and CCStudio IDE. Let me know how you get on. 

    Regards

  • 0 in reply to Ivan
    Prodigy 30 points

    Hi Ivan,

    I am not sure I understand "offline" and "locally", but I describe my environment setup below:

    - As mentioned, SDK is the latest 8.10.

    - CCS is CCS Theia 140.

    Let me narrow down my quetion to this point:  How to make Extended Advertising feature work, which looks needed when talks with BLE 5.3 center devices.  For the Extended Advertising, what I did it that

    1. Based on the basic_ble

    2. I enabled Extended Advertising feature from the syscfg UI.

    3. I then change my advertisement type from Legacy to Extended.

    4. Since I got error prompt saying no Scan Response is possible in this advertisement type, so I unchecked all the items in my Scan Response Data from the UI.

    5. To make the compiling pass, I deleted two lines of initialization code for the 'scanRespDatalen' and 'scanRespData' members of the advSetInitParamsSet_1 in the app_peripheral.c

    6. Then I see, no any center including the SimpleLink Connect can see my device.

    7. But on my device side, the calls to BLEAppUtil_initAdvSet() and BLEAppUtil_advStart() were successful.

    8. From memory I dumpled my advData: 61420912 20636973 20454C42 6A6F7270 02746365 02030601 0A02FFF0 00

    Please sort me out and let me know how to make the Extended Advertising work. Thanks in advance!

    - woody

  • 0 in reply to Di Wu
    TI__Guru** 101460 points

    Hi Woody,

    Thank you for the details shared.

    For sanity,

    - could you please share a screen shot of the SysConfig configuration for the advertisement?

    - could you try changing the primary and secondary PHYs used? (try using 1M PHY only)

    Best regards,

  • 0 in reply to Clément
    Prodigy 30 points

    Hi Clement,

    Yes, I configured the primary and secondary PHYs for advertising as using 1M only. Please check my advertisement configuration from below screen shot:

    Kind Regards,

    woody

  • 0 in reply to Di Wu
    TI__Genius 15535 points

    Hello Woody,

    Can we double check that your device is actually advertising? For this we could do two things:

    1. Enable the RF observable and use a logic analyzer to see if the device is advertising. Please see the user guide here: Debugging RF Output.
    2. If you have a XDS110 ETHDR probe, please follow the user guide section here: EnergyTrace stand-alone Instructions. If the device is advertising, you should be able to see something similar to what is shown in Figure 181.

    If you can attach picture of this findings, it could be useful.

    BR,

    David.

  • 0 in reply to David
    Prodigy 30 points

    Hi David,

    The two methods you mentioned are alternative, right? And, what I had is XDS110 ET, not sure it's the same thing as the XDS110 ETHDR.

    Kr,

    woody

  • 0 in reply to Di Wu
    TI__Genius 15535 points

    Hello Woody,

    Yes, they are alternatives. Yes, the XDS110 ET should be able to enable Energy Trace.

    BR,

    David.

  • 0 in reply to David
    Prodigy 30 points

    Hi David,

    The instructions I found in web pages for how to use the EnergyTrace are for CCS. But my CCS Theia menu layout is very different. At the end, I found the EnergyTrace button in a location of my CCS Theia shown in below screenshot. Please firstly have a check.

    But, as you can see, the EnergyTrace button is grayed out.  Please help me in how to use this tool. Thanks!

    Kr,

    woody

  • 0 in reply to Di Wu
    TI__Intellectual 2230 points

    Hi Woody, 

    Sorry for the delay. Please see this guide on how to use the Energy Trace Tool on CCS Theia Energy Trace Tool CCS Theia which has a section on how to start the energy trace. Also, you need to be on debug session to run the energy trace. 

    Regards

    Ivan