A UICR write operation has been requested but UICR has not been erased

RE: A UICR write operation has been requested but UICR has not been erased

bjorn-spockeli — Wed, 20 Sep 2017 08:54:20 GMT

Alternatively, you can run make erase and then make flash.

RE: A UICR write operation has been requested but UICR has not been erased

bjorn-spockeli — Wed, 20 Sep 2017 08:53:39 GMT

Ah, its because the make flash only performs a sectorerase, which does not erase the UICR registers.Could you try flashing the board using nrjfprog directly, i.e. just run make and then erase chip using the --eraseall option and flash the compiled hex file that in the _build folder, i.e.

nrfjprog -f nrf52 --eraseall
nrfjprog -f nrf52 --program _build\nrf52832_xxaa.hex

This will erase the entire chip, so if you're using a SoftDevice you will have to flash it as well.

RE: A UICR write operation has been requested but UICR has not been erased

Chris — Wed, 20 Sep 2017 08:30:22 GMT

Thanks Bjorn, I have to admit I'm pretty new to the low-level coding (coming from C# in comfortable Visual Studio :) )

After the changes I tried (in this order): Make flash_softdevice Make flash

here's the output of flash:

$ make flash Flashing: _build/nrf52832_xxaa.hex nrfjprog --program _build/nrf52832_xxaa.hex -f nrf52 --sectorerase Parsing hex file. Erasing page at address 0x1F000. Erasing page at address 0x20000. Erasing page at address 0x21000. Erasing page at address 0x22000. Erasing page at address 0x23000. Erasing page at address 0x24000. Erasing page at address 0x25000. Erasing page at address 0x26000. Erasing page at address 0x27000. Erasing page at address 0x28000. Erasing page at address 0x29000. Erasing page at address 0x2A000. Erasing page at address 0x2B000. Erasing page at address 0x2C000. Erasing page at address 0x2D000. WARNING: A UICR write operation has been requested but UICR has not been WARNING: erased. Please verify that the result is correct. Applying system reset. Checking that the area to write is not protected. Programing device. nrfjprog --reset -f nrf52 Applying system reset. Run.

RE: A UICR write operation has been requested but UICR has not been erased

bjorn-spockeli — Wed, 20 Sep 2017 07:34:36 GMT

@chrismakaio: You should only have to add CFLAGS += -DCONFIG_NFCT_PINS_AS_GPIOS to the Makefile, the nRF52 will then run this snippet on startup(see the system_nrf52.c file)

#if defined (CONFIG_NFCT_PINS_AS_GPIOS)
        if ((NRF_UICR->NFCPINS & UICR_NFCPINS_PROTECT_Msk) == 
               (UICR_NFCPINS_PROTECT_NFC << UICR_NFCPINS_PROTECT_Pos)){
            NRF_NVMC->CONFIG = NVMC_CONFIG_WEN_Wen << NVMC_CONFIG_WEN_Pos;
            while (NRF_NVMC->READY == NVMC_READY_READY_Busy){}
            NRF_UICR->NFCPINS &= ~UICR_NFCPINS_PROTECT_Msk;
            while (NRF_NVMC->READY == NVMC_READY_READY_Busy){}
            NRF_NVMC->CONFIG = NVMC_CONFIG_WEN_Ren << NVMC_CONFIG_WEN_Pos;
            while (NRF_NVMC->READY == NVMC_READY_READY_Busy){}
            NVIC_SystemReset();
        }
    #endif

However, adding

const uint32_t UICR_ADDR_0x20C __attribute__ ((section(".uicrNfcPinsAddress"))) __attribute__((used));

to main.c and modifying the linker script by adding

UICR_NFCPINS(r) : ORIGIN = 0x1000120C, LENGTH = 0x04

under MEMORY in the linker script and adding

.uicrNfcPinsAddress : 
  { 
     KEEP(*(.uicrNfcPinsAddress)) 
  } > UICR_NFCPINS

under SECTIONS should also work. Are you using nrfjprog to flash the compiled hexfile?

RE: A UICR write operation has been requested but UICR has not been erased

Chris — Tue, 19 Sep 2017 18:52:19 GMT

just another data point: I'm NOT using the DK :)