nRF5340 samples

This section lists the nRF Connect SDK samples specific to developing with the nRF5340 SoC.

General information about samples in the nRF Connect SDK

• If you are working with embedded devices, it is a good practice to first test your setup by programming an unchanged sample to your development kit.

• Some samples in the nRF Connect SDK are currently not designed to work out-of-tree. You may need to manually configure your sample to work correctly in nRF Connect for VS Code.

• Starting from the nRF Connect SDK v2.0.0, TF-M is the only way to use security by separation with ARM TrustZone. In addition, the TF-M implementation is enabled by default for all samples and applications in the nRF Connect SDK when you build for the */ns variant of the boards.

• All samples in the nRF Connect SDK use Fatal error handler library and are configured to perform a system reset if a fatal error occurs. This behavior is different from how fatal errors are handled in the Zephyr samples. You can change the default behavior by updating the configuration option CONFIG_RESET_ON_FATAL_ERROR.

• All samples in the nRF Connect SDK are tested and verified in accordance with their maturity level.

Subpages

• nRF5340: Empty firmware for application core
• nRF5340: SMP Server with external XIP
• nRF5340: Network core bootloader
• nRF5340: Remote IPC shell
• nRF5340: nRF RPC Entropy