Reading UICR

RE: Reading UICR

Marbro1965 — Tue, 21 Jan 2025 14:06:12 GMT

The error code is NRF_ERROR_INVALID_PARAMS.

I thought it was address but I cheched and it is &UICR->OTP[0], The same define in ranges. In 2.9.0 I have only one ranges file, while in 2.7.0 there are many.

Now I went back to 2.7.0 because of many problems on intellisense. But I did not check if in 2.7.0 it works. I have to modify all ranges file because i do not know which is used.

Anyway i do not like The idea to modifica sdk, and was looking to a way to override those ranges. But it is quite difficult to find information about.

RE: Reading UICR

Sigurd — Tue, 21 Jan 2025 13:24:21 GMT

[quote user="Marbro1965"] I rebuild all but it does not read the OTP[0].[/quote]

Did you get any error codes? What did it read?

RE: Reading UICR

Marbro1965 — Fri, 17 Jan 2025 19:19:17 GMT

I applied to nrf9160. Modified the ranges in C:\ncs\v2.9.0\zephyr\modules\trusted-firmware-m\nordic\include\tfm_read_ranges.h. In my case &UICR->OTP[0] is 0xFF8100. I rebuild all but it does not read the OTP[0].

How do I know that it is compiling the new ranges?

Thanks

RE: Reading UICR

Marbro1965 — Fri, 17 Jan 2025 07:18:36 GMT

As I promised, this is a quote from Ask AI.

You mentioned that since 2.8.0 it is easier to read UICR register in nrf9160

Yes, that's correct. According to the nRF Connect SDK v2.8.0 Release Notes, there has been an improvement in reading UICR registers for Trusted Firmware-M (TF-M). Specifically:

A possibility to read UICR.OTP registers through platform services has been added.
The TF-M version has been updated to v2.1.0.

This change makes it easier to access UICR (User Information Configuration Registers) OTP (One-Time Programmable) registers in the nRF9160.

nRF Connect SDK v2.8.0 Release Notes

This improvement should simplify the process of reading these registers during runtime for applications using the nRF9160.

RE: Reading UICR

Marbro1965 — Fri, 17 Jan 2025 05:42:41 GMT

Hello Sigurd.

I was using 2.7.0 and moved to 2.9.0 because in the site somewhere (I will look for this quote later and attach) it was written it was easier to read ucir without modifying tfm_read_ranges.h

My client wants to save some data unique for every board in production.

They must be read only.

They must be programmed using nrfjprog as I mentioned before

Best

RE: Reading UICR

Sigurd — Thu, 16 Jan 2025 21:00:27 GMT

[quote user="Marbro1965"]

is that enough to write

CONFIG_TFM_PARTITION_PLATFORM=y

in prj.conf and call

uint32_t

secure_read_word(intptr_t ptr)

[/quote]

As mentioned in the post I linked to, you would also need to modify the tfm_read_ranges.h

[quote user="Marbro1965"]Can you please tell me how call for address 0x00FF8000?[/quote]

This is the APPROTECT register.

Could you explain what you are trying to achieve ?

RE: Reading UICR

Marbro1965 — Thu, 16 Jan 2025 13:57:01 GMT

Hi,

is that enough to write

CONFIG_TFM_PARTITION_PLATFORM=y

in prj.conf and call

uint32_t

secure_read_word(intptr_t ptr)

{

uint32_t err = 0;

uint32_t val;

enum tfm_platform_err_t plt_err;

plt_err = tfm_platform_mem_read(&val, ptr, 4, &err);

if (plt_err != TFM_PLATFORM_ERR_SUCCESS || err != 0) {

printk("tfm_..._mem_read failed: plt_err: 0x%x, err: 0x%x\n",

plt_err, err);

return -1;

}

return val;

}

Can you please tell me how call for address 0x00FF8000?

And for programming, can I make a hex file (MyHex.hex) with this content:

:0200000400FFFB
:1080000031323334353637380000000000000000CC
:00000001FF

and use

nrfjprog --program MyHex.hex --chiperase --reset

Best Regards

RE: Reading UICR

Marbro1965 — Thu, 16 Jan 2025 13:37:06 GMT

Hi,

looks a little bit complicated. Does it change my not secure application in a secure application?

RE: Reading UICR

Sigurd — Thu, 16 Jan 2025 13:00:50 GMT

See this post, it's for nRF54, but the same methods apply to nRF91 as well.
RE: Static Partition Alignment
see also https://github.com/nrfconnect/sdk-nrf/blob/main/samples/tfm/tfm_hello_world/src/main.c

RE: Reading UICR

Marbro1965 — Wed, 15 Jan 2025 19:55:24 GMT

Unfortunately does not work in this way.

Thanks

RE: Reading UICR

qarnet — Wed, 15 Jan 2025 19:32:22 GMT

You can just read the register directly. For example, reading out the first entry in the one time programmable memory (Source of registers):
uint32_t reg_val = *(volatile uint32_t *) 0x00FF8108;

That is at least what I used to be able to do with something like the nRF52840. I don't know if the nRF9160 has extra security measures.