Empty firmware for multiple core SoCs

The sample demonstrates how to generate an empty network (or other) core firmware. The sample is used only by the applications that do not use the other core(s). An empty image can be added to a project using the following options (depending upon if an SoC has the CPU):

Core	Sysbuild Kconfig
Network/radio processor	SB_CONFIG_NETCORE_EMPTY
Fast Lightweight peripheral processor (FLPR)	SB_CONFIG_FLPRCORE_EMPTY
Peripheral processor (PPR)	SB_CONFIG_PPRCORE_EMPTY

Requirements

The sample supports the following development kits:

Hardware platforms	PCA	Board name	Board target
Thingy:53	PCA20053	thingy53	thingy53/nrf5340/cpunet
nRF54L15 DK	PCA10156	nrf54l15dk	nrf54l15dk/nrf54l15/cpuflpr
nRF54H20 DK	PCA10175	nrf54h20dk	nrf54h20dk/nrf54h20/cpuppr nrf54h20dk/nrf54h20/cpuflpr
nRF5340 DK	PCA10095	nrf5340dk	nrf5340dk/nrf5340/cpunet

Building and running

This sample can be found under samples/basic/empty in the nRF Connect SDK folder structure.

To build the sample, follow the instructions in Building an application for your preferred building environment. See also Programming an application for programming steps and Testing and optimization for general information about testing and debugging in the nRF Connect SDK.

Note

When building repository applications in the SDK repositories, building with sysbuild is enabled by default. If you work with out-of-tree freestanding applications, you need to manually pass the --sysbuild parameter to every build command or configure west to always use it.

Testing

The sample does not build firmware for the application core and because of that the sample cannot be tested separately.