Cellular samples

This section lists the available nRF Connect SDK samples for the cellular IoT development. Additionally, you might want to check the Memfault sample and the Networking samples.

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.

If you want to list samples available for one or more specific boards, use the nRF Connect for Visual Studio Code extension to filter them.