https://devzone.nordicsemi.com/f/nordic-q-a/83831/nrf52832_xxab-secure-bootloaderHello everyone, Because of problem with availability we were forced to change our ready-for-production project from nRF52832_xxAA to nRF52832_xxAB which has 2x less FLASH and RAM memory. From application point of view it wasn&#39;t a problem - we easilyen-USTelligent Community 13Thu, 20 Jan 2022 07:54:40 GMThttps://devzone.nordicsemi.com/thread/348631?ContentTypeID=1Thu, 20 Jan 2022 07:54:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:89574b43-c194-46f1-a6fc-916f65fd6ae2Michal<p>I have found the issue, the problem was that my Makefile had the following definitions:</p> <p><pre class="ui-code" data-mode="text">... CFLAGS += -DNRF52 CFLAGS += -DNRF52832_XXAB ... ... ASMFLAGS += -DNRF52 ASMFLAGS += -DNRF52832_XXAB ...</pre></p> <p></p> <p>But it came out that <span style="font-family:monospace;"><span style="background-color:#ffffff;color:#000000;">nRF5_SDK_15.3.0_59ac345/modules/nrfx/mdk</span>/nrf.h </span>has the following statement:</p> <p><pre class="ui-code" data-mode="c_cpp">/* Redefine &quot;old&quot; too-generic name NRF52 to NRF52832_XXAA to keep backwards compatibility. */ #if defined (NRF52) #ifndef NRF52832_XXAA #define NRF52832_XXAA #endif #endif</pre></p> <p>which caused that patch for bootloader didn&#39;t work and still took definitions for nRF52832_XXAA processor.</p> <p>Removing `NRF52` definition from CFLAGS and ASMFLAGS solved the problem.</p><div style="clear:both;"></div>