Using softdevice directly without SDK libraries

RE: Using softdevice directly without SDK libraries

Hung Bui — Fri, 25 Jan 2019 13:02:56 GMT

Hi,
The header file included with the softdevice is for to be used with softdevice. For other defines for the chip itself, you would need to write your own or you can reuse the .h files we have in the SDK. We also have a bare metal library here that you can refer.

RE: Using softdevice directly without SDK libraries

jfg — Thu, 24 Jan 2019 17:35:34 GMT

We're using the latest softdevice `s132_nrf52_4.0.5_API` and wanting to use it directly without the SDK. The problem we are running into is the included headers don't have an nrf.h file. Is this only available with the SDK?

RE: Using softdevice directly without SDK libraries

Hung Bui — Fri, 14 Aug 2015 13:02:40 GMT

Hi Nick,

You can also have a look at the ble_app_template example we have on SDK v8.0 (or v8.1, not v9.0). In that example, we don't use device_manager but handle all the BLE events and control directly from main.c.

We still use the app_timer, app_gpiote in the example, but you can refer to the template example to know how to handle BLE directly, in your application.

RE: Using softdevice directly without SDK libraries

Nick — Fri, 14 Aug 2015 09:06:46 GMT

Thanks for the response. I am also using my own app_timer module. The SDK app_timer module was hogging RTC1 and I needed to use it for multiple purposes. But I kept the .h (API) the same, so that the SDK modules can use my app_timer implementation. Not ideal, but that worked. The problem I am having now is that I created my own HAL for the GPIOTE.

RE: Using softdevice directly without SDK libraries

RK — Fri, 14 Aug 2015 08:01:52 GMT

You can absolutely do it - I do it. What you may lose is some of the higher level abstraction modules like the bond manager and the advertising manager. Some of them only use a couple of the HAL components, like pstorage and timers so you may still be able to use them. I have my own timer implementation which stops me using many of them at all.

You will need to know more about BLE if say you write your own device manager, that deals with bonding and persistence of bonded data etc.

If you're just talking about the real hardware drivers, TWI, SPI, UART etc, none of those are really used in the BLE modules, so you can use your own very easily.