nRF Connect SDK and nRF5 SDK statement

RE: nRF Connect SDK and nRF5 SDK statement

user111296 — Mon, 04 Apr 2022 16:27:41 GMT

Comparing an implementation using Zephyr RTOS with an "old" bare-metal approach, how is power efficiency affected? Is Zephyr RTOS less optimized for energy efficiency due to multiple layers of abstraction?

RE: nRF Connect SDK and nRF5 SDK statement

user112580 — Wed, 30 Mar 2022 16:38:47 GMT

Runtime peripheral remapping is still not supported in Zephyr. It has been been open issue for more than a year now.

RE: nRF Connect SDK and nRF5 SDK statement

user79167 — Sun, 14 Nov 2021 11:24:03 GMT

Is there any reuse of libraries and drivers between nRF5 SDK and nRF Connect SDK? In other words if I used e.g. PWM or SAADC from nRF5 SDK, can I reuse the same implementation in nRF Connect SDK?

RE: nRF Connect SDK and nRF5 SDK statement

user79167 — Sun, 14 Nov 2021 11:19:37 GMT

We have a project developed under nRF5 SDK 14.3 using a bootloader and DFU. Is it possible to make an update of the app implemented / ported to nRF Connect? I.e is there any API compatibility between these two?

RE: nRF Connect SDK and nRF5 SDK statement

user80610 — Wed, 06 Oct 2021 07:57:26 GMT

I have my thread application running on nRF5 SDK for Thread and Zigbee. But it is not up to date with the latest open thread features. Can I port my current thread application on the "bare metal" approach on nRF Connect SDK?

RE: nRF Connect SDK and nRF5 SDK statement

user63932 — Thu, 23 Sep 2021 13:17:47 GMT

There was a note indicating that ANT is currently not supported in nRF Connect SDK. When do we expect ANT to be supported?

RE: nRF Connect SDK and nRF5 SDK statement

user11707 — Fri, 17 Sep 2021 15:42:31 GMT

Is it possible to use the nRF Connect SDK for nRF52) developers that prefer the "bare metal" approach? What would be the drawbacks of using nRF Connect SDK in "bare metal" mode?