• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 424 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.

LAUNCHXL-CC1352P: Adding scanning (observing) ability to dmm_wsnnode_remote_display example

GOHM ELECTRONICS
Expert 2085 points
Part Number: LAUNCHXL-CC1352P

Hi all,

We studied dmm_wsnnode_remote_display example and noticed that it provides only advertising (broadcasting) functionality. Is it possible to add scanning ability over BLE to this particular example? Is there such a DMM example?

Regards

  • 0
    TI__Intellectual 1975 points
    Hello,

    There is no such DMM example for this at the moment. However, there is nothing that I'm aware of that would stop you from adding it into the example. I would take an example from the SDK with scanning to base your work off of in order to add it in.

    Although this should not be a concern with adding scanning, keep in mind that any added traffic to the device will increase the likelihood of stack collisions. I believe in this example BLE has a higher priority over the WSN stack. So if you add too much traffic then the WSN stack will be starved of radio time by the higher priority BLE traffic. Again, this amount of traffic should not cause large issues. If it does you can decrease the BLE connection interval to enable more radio scheduling options per supervision timeout.

    If you have not already, there is a SLA on DMM Fundamentals that may be beneficial to check out! dev.ti.com/.../dmm_fundamentals.html

    Best,
    Kris
  • 0 in reply to Kristopher Burney
    Expert 2085 points

    Hi Kristopher,

    Thank you for your answer.

    These days we're trying to implement scanning ability to dmm_wsnnode_remote_display example by simply adding scan functions and variables to it from simple_central example, but it seems that the project is not able to "see" functions starting with GapScan_(function_name) although icall_ble_api.h is included to the remote_display.c file.  Here's an example of the error we've got:

    unresolved symbol GapScan_enable, first referenced in <whole-program>

    We've already checked linked resources, includes, libraries etc. and everything seems fine. Do you have any ideas?

    Regards

  • 0 in reply to GOHM ELECTRONICS
    Expert 2085 points
    Should we add any libraries to linker settings?

    Regards
  • 0 in reply to GOHM ELECTRONICS
    TI__Intellectual 1975 points

    My apologies for the delay.

    You will need to change the BLE Host Build Configuration of the stack_library project.

    in dmm_wsnnode_remote_display_stack_library project under the TOOLS folder there is a file build_config.opts. In this file there is a section for changing the Host Build Configuration. Modifying this HOST_CONFIG define will link the GapScan_enable function as well as other Central device functions.

    Here you can see I've commented out the Peripheral_cfg choice and instead uncommented the peripheral_cfg + central_cfg option.

    /* BLE Host Build Configurations */
/* -DHOST_CONFIG=PERIPHERAL_CFG */
/* -DHOST_CONFIG=CENTRAL_CFG */
/* -DHOST_CONFIG=BROADCASTER_CFG */
/* -DHOST_CONFIG=OBSERVER_CFG */
/* -DHOST_CONFIG=PERIPHERAL_CFG+OBSERVER_CFG */
/* -DHOST_CONFIG=CENTRAL_CFG+BROADCASTER_CFG */
-DHOST_CONFIG=PERIPHERAL_CFG+CENTRAL_CFG

    After this make sure to do a rebuild of the stack_library project and app project to make sure the change gets applied. Your app project should be able to resolve the function now!

    Best,

    Kris

  • 0 in reply to Kristopher Burney
    Expert 2085 points

    Hi Kristopher,

    Thank you for the answer. We're able to build the project and we can move on now.

    Best regards