nRF5340 development

RE: nRF5340 development

haakonsh — Fri, 14 Feb 2020 10:34:40 GMT

Hmm, The central uart sample could serve as a template for the lbs central.

I believe the uart central filters advertisers based on the Nordic Uart Service UUID. You'll have to change that to filter for the LBS Service UUID instead. You will also have to change how the application reacts to the Service Discovery data received as it will not contain the Nordic Uart Service and its Characteristics but the LBS instead.

I'm writing a tutorial that covers the creation of a custom Service as we speak, though I've only implemented the peripheral side and have just started on the central side myself.

For FreeRTOS support I'm guessing we'll have to look for support for the nRF5340 in a future nRF5 SDK. I'll ask around for what the plans are there.

RE: nRF5340 development

Brian — Thu, 13 Feb 2020 18:01:28 GMT

Thanks for the quick response haakonsh!

The link to scan.rst helped. After looking through the examples more, I'm wondering if the peripheral_uart is the right starting point. Looking at peripheral_lbs, this would get me the end functionality I need on one side - sending a button state and receiving an LED control command. I just need the matching central side to go with it, along with the ability to detect whether the device is connected as the central or the peripheral. I'd like to run the same code on both dev boards and have them connect when a button on one of the boards is pressed - the button press would initiate scanning on that board. How difficult would it be to implement the central side of the peripheral_lbs on the dev board?

Any inputs on future support for FreeRTOS?

Thanks...

Brian

RE: nRF5340 development

haakonsh — Thu, 13 Feb 2020 12:57:44 GMT

[quote user=""]Should sample code from both of these directories work on the dev board?[/quote]

Yes.

[quote user=""]Can you give me some guidance on which sample code to start with? Is it as simple as starting with the peripheral_uart example and adding a call to bt_scan_start when the button is pushed? Or is there more infrastructure to add to enable the central role?[/quote]

We've made a library/module called scan.c in NCS that we use to decode the advertising data that is returned in the scan callback. The uart and LBS Central samples use this library. I suggest you set the scan parameters with a call to bt_scan_params_set prior to calling bt_scan_start.

[quote user=""]Is there documentation that describes the steps I need to go through to implement this functionality?[/quote]

Documentation: https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/master/include/bluetooth/scan.rst use the Central samples in NCS as a reference.

[quote user=""]Is there documentation that describes setting up the various BLE parameters (connection interval, advertising interval, etc), as well as other behaviors such as scan filters?[/quote]

Zephyr API docs for the GAP layer: https://docs.zephyrproject.org/latest/reference/bluetooth/gap.html. The GAP layer handles advertisements, scanning, and connection management.

Setting the scan filter and parsing scan data with just the Zephyr API is a bit difficult so I recommend to use our Scan library.