tree 55b86d91e702ccc4ecf35f1b699f0f2713ffd0b7
parent 24acc7d43ddeb55d036b293c4a0ca37a8d5eb4c2
author Rafał Kuźnia <rafal.kuznia@nordicsemi.no> 1716889422 +0200
committer Fabio Baltieri <fabio.baltieri@gmail.com> 1717066511 +0100

scripts: west_commands: runners: nrf_common: optional UICR cleanup

The flasher was unconditionally cleaning the UICR area, even when the
application didn't have a new configuration generated. This can happen,
when CONFIG_NRF_REGTOOL_GENERATE_UICR=n. In such case, keep the old UICR
configuration on the device.

A real scenario where we should set CONFIG_NRF_REGTOOL_GENERATE_UICR=n
is when building multiple firmware images that are meant to run one
domain. The primary application build generates the UICR configuration
and secondary images don't. Before this change, the flashing process of
the primary application would write new UICR configuration, but the
flashing process of secondary images would erase it.

Signed-off-by: Rafał Kuźnia <rafal.kuznia@nordicsemi.no>