UICR reading and writing issues

RE: UICR reading and writing issues

KatoTakayuki — Tue, 10 Mar 2026 00:19:27 GMT

Thanks, your constant support.

Is that this description?

Added a possibility to read UICR.OTP registers through platform services.

I understand that this is a limitation.

It's difficult to understand. However, this is considered to be the current operating specification.
The error codes(TFM_PLATFORM_ERR_INVALID_PARAM) are also difficult to understand.

It's difficult to cover all the release notes.
Please let me know if there's any other explanation beyond the release notes.

Best regards,
Kato.

RE: UICR reading and writing issues

Hakon — Mon, 09 Mar 2026 11:32:24 GMT

[quote user="KatoTakayuki"]But the write error still occurs.[/quote]

Writing OTP from non-secure region is not supported, just reading.

RE: UICR reading and writing issues

KatoTakayuki — Mon, 09 Mar 2026 00:24:39 GMT

I understood, I'll check that.
And then report.

I updated to v3.2.3.

As a result, the read issue(tfm_platform_mem_read()) has been resolved.

But the write error still occurs.
The function tfm_platform_mem_write32() returns an error(TFM_PLATFORM_ERR_INVALID_PARAM),

I would also like support for writing problem.

Best regards,
Kato.

RE: UICR reading and writing issues

Vidar Berg — Fri, 06 Mar 2026 17:08:57 GMT

Hello,

Please check out this thread: https://devzone.nordicsemi.com/f/nordic-q-a/127271/nrf9151-otp-memory-read-corrupts-zephyr-os-kernel. It looks like you may be experiencing the same issue.

Best regards,

Vidar