I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

[rexxdad]

the provider has provided source for their firmware which provides serial port communications to control operation only in old sdk 1.7.0 format

I need to use some other approach..

I would like to use pairing to connect my app to the local device

and then the local device would be ble central

and remotes would be ble peripheral 

today the 'same' firmware is loaded on both identical devices

but my testing will have a different local device using the 52840 and the remote is 52833

so my firmware update should be able to distinguish how to operate, I 'think' this is different boards and different binary builds. 

my app would pair with the local device (should only ever connect to ONE local device, during initial setup, the device is nearby)

there 'is' a possibility that there COULD be multiple instances of the same local device within bt range, so want to preclude ever seeing talking to others

in the future these devices would be BT6 with channel sounding support. but still architected this way to minimize dependencies.

data traffic from app to local device is low, done with BT notification (using ble).. 

I suppose I could store persistent data on both app device and local device with some key/identifier to be able to use only ble (one of the future devices says single mode bt, aka ble only)

but I still don't understand how to configure the 1.7.0 sdk to add the function that I can use.   the java config app assumes you know what the words/terminology means

and understand the concurrence (this function and not that) restrictions..

the provider has another instance using the 1.7.0 sdk  with BT ble peripheral only (but does not have serial port comms at all) 

extending their firmware is an exercise for the user (me!).. so trying to get my head around the config 

I can build each w the segger IDE, so that part is ready.

I have flashed the build with the IDE as well and command line tools.. so have that

have ble code that does most of what I want in both ios and android.. so have ble experience.  now to get runtime in the right config.. 

[JONATHAN LL]

Hi,

I would recommend that you look in to using NRF Connect SDK that is based on Zephyr as the building blocks for a project that you want to future proof as you are looking at Channel sounding and Bluetooth 6, and use NCS 2.7.0.  


If I understood correctly, 

You are working with a product that needs to get some new features, the current product and its SW is provided and that is what you want to modify ?

You should be able to get the programs to work with both the 840 and the 833.



But I am a bit unsure what SDK you are talking about if it is the nRF5 SDK or the NCS


BLE samples can be found here: https://docs.nordicsemi.com/bundle/ncs-2.7.99-cs2/page/nrf/samples/bl.html 


Regards,
Jonathan

[rexxdad]

i am extending the qorvo uwb build which uses the 1.7.0 sdk. its supports the 833 and 840 already.

i will do similar with the nrf sdk for cs, but hardware not available yet 

[rexxdad]

[JONATHAN LL]

rexxdad said:

i am extending the qorvo uwb build which uses the 1.7.0 sdk.

Image showes using nRF5 SDK v17.1.0 it seems.

Ref https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/index.html 

So If I understand correctly you want to port the nRF5 SDK project to NCS SDK?

Regards,
Jonathan

[rexxdad]

no... I want to add the BLE services to this build.. on the 840 peripheral(really server in pairing style to talk to my phone app) and central (to be UCI controller), and on the 833, peripheral only(to control UCI controllee)

I do NOT want to rewrite the UWB support.. 
I asked an earlier question here about migrating this to the new sdk under VS, and was told, No, we don't have that.

in the future (after I get this working with my app) I would do a pure BT implementation using 
ble between phone and localdevice , and bt(master) with CS to BT(slaves) wi CS

[rexxdad]

architectural drawing

[JONATHAN LL]

Thanks for all the extra details.


So the best example I have to offer here is the FreeRTOS example with Hart Rate Monitor:  https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/ble_sdk_app_hrs_freertos.html 

It is probably the closes example that shows how BLE is implemented compared to what you want. 

Regards,
Jonathan

[rexxdad]

thanks. but i want more info on what the settings in the config file mean, and what tasks a developer has to complete to make a particular configuration work. 

i see critical sections and encryption functions.ii see linker errors which i think are sdk code, not implementor code. and i cant tell if i have incomplete settings or if the provider stripped the sdk files down to save space.

i don't  understand Softdevice. it looks like i need competing versions to make my scenarios work

[JONATHAN LL]

rexxdad said:

i don't  understand Softdevice.

The SoftDevice is a protocol stack, made by nordic. https://docs.nordicsemi.com/bundle/ug_gsg_ses/page/UG/gsg/softdevices.html 
In the Zephyr based SDK you have the option to use nordic's solution or the Zephyr provided option. 

In short you need it to get BLE. 


Here is what we have as extra material, https://docs.nordicsemi.com/bundle/ug_gsg_keil/page/UG/gsg/related_docs.html 

You will need to dig in to the documentation for specifics on the errors or warnings that you are getting. https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/index_1.html 


And we also do have some guides : https://devzone.nordicsemi.com/guides/short-range-guides/ most might not be relevant. 

Regards,
Jonathan