RE: Segger and the SDK

Øyvind — Fri, 21 May 2021 08:22:44 GMT

Hello,

Thank you for your valuable feedback.

Have you seen our NCS tutorial?

[quote user=""]Is it just me or is the nRF tool chain / sdk getting heavier and more complicated with the passage of time?[/quote]

The nRF Connect SDK is a more advanced SDK to handle our newer devices using Cortex M33, nRF9160 and nRF5340. The original nRF52 SDK is still available for development.

Kind regards,
Øyvind

RE: Segger and the SDK

wz2b — Thu, 20 May 2021 12:11:21 GMT

I figured some things out. There is a Zephyr bluetooth stack that doesn't use any soft device. The beacon example uses that by default. Then there is a soft device implementation that I could use if I needed those features. I don't know how I would do that, but I suspect that it would be that I add nrfxlib\softdevice_controller to my solution then somehow disable Zephyr. I don't need extended advertising so maybe there is no reason for me to do this. What I do need is very low power; the ability to control how often I advertise (again, to save power); and the ability to eventually move this project to whatever chip (maybe not the nRF52840, or maybe it is) is best suited to just being a battery powered beacon.