nRF21540 UICR programming

RE: nRF21540 UICR programming

Stanley — Wed, 13 Oct 2021 01:33:56 GMT

Thank you for your inquiry, the problem has been solved.

RE: nRF21540 UICR programming

greg.leach — Tue, 12 Oct 2021 13:36:24 GMT

Was there ever a resolution for this? I'm seeing the same behaviour described above. Would it be possible to provide some pseudo code showing the steps needed to set the UICR registers?

RE: nRF21540 UICR programming

Susheel Nuguru — Thu, 21 Jan 2021 09:26:05 GMT

CONFREG2 and CONFREG3 are a bit special, they are one time write and I am not very clear on the limitations on read.

Have you performed any writes to CONFREG2 and CONFREG3 and verifying your writes?

Can you please upload your project for me to reproduce this, I have not tried writing to these registers and it would help to get your project instead of me trying to make it from scratch

RE: nRF21540 UICR programming

Stanley — Tue, 19 Jan 2021 02:06:23 GMT

I have solved this problem, but there are still some things I don't understand. I can use the example in \examples\peripheral\spi of SDK17 to read and write CONFREG0 and CONFIGREG1, but I cannot read and write CONFREG2 and CONFREG3. When the spi_event_handler is cancelled, everything is fine. Do you know the reason?

RE: nRF21540 UICR programming

Susheel Nuguru — Mon, 18 Jan 2021 11:36:40 GMT

Can you try to read those values in your application code? It seems that the segger might be having some read/display issues accessing these registers.

If it is the same issue that you read 0 after write in your application, then i can try to replicate the problem.