Writing to UICR Customer Registers

RE: Writing to UICR Customer Registers

Jared — Tue, 27 Oct 2020 09:34:01 GMT

Hi,

Yes you can write to the UICR register if you have not already done it before during production.

regards

Jared

RE: Writing to UICR Customer Registers

mmak — Mon, 26 Oct 2020 16:55:27 GMT

Hi Jared,

Thanks for the clarifying!

Me and my colleague will attempt to write custom bytes to the UICR customer registers with j-flash once the device has been flashed with our hex application. To my understanding, as long as the target address was not written prior during the initial flashing process, the custom bytes should be able to be written to the UICR customer registers.

Matthew

RE: Writing to UICR Customer Registers

Jared — Fri, 23 Oct 2020 13:51:12 GMT

Hi,

[quote user=""]

I've read that a previously written UICR register cannot be written without erasing it (https://devzone.nordicsemi.com/f/nordic-q-a/7163/can-i-write-to-the-uicr-registers-with-a-segger-and-jlink), hence the question.

[/quote]

Yes, the UICR is not meant to be written to multiple times, but rather once during production.

[quote user=""]Also, just wanted to verify if Customer[0] can still be used for sdk16.0.0 and does not contain device type and revision information as specified here: https://devzone.nordicsemi.com/f/nordic-q-a/13030/trouble-writing-nrf52832-s-uicr--customer-through-j-flash[/quote]

Yes, the information in the linked thread is old and not valid anymore. The register is free to be used.

regards

Jared