Dual Core Bluetooth Stack Options (RPC)

This topic is only relevant if you are using the nRF5340

The nRF5340 has two cores. The main core is called the Application Core, and is where most of your application is running. When you add Bluetooth Low Energy to your application for an nRF5340, the nRF Connect SDK will add the SoftDevice Controller to the mix, and program it into the Network Core. This way, whenever your application wants to do tasks related to Bluetooth Low Energy, it will communicate with the network core using something called OpenAmp.

This is one of the advantages using the nRF5340. All the timing critical operations are handled by the Network Core, instead of your application core. This leaves you with more control of the CPU on the Application Core, in case you want to do high accuracy timing tasks. Let’s say you want to have very accurate control of a GPIO interrupt. In the nRF52 series, this is not possible while doing Bluetooth Low Energy tasks, because the Bluetooth Low Energy stack requires first priority access to the CPU on every connection interval. In the nRF53 this can be offloaded to the network core, leaving you in more control of the CPU of the Application Core.

Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.