nRF52 FICR registers

[chris]

Reading from the FICR seems to produce some results other than what I would expect. For example, reading from offset 0x10C seems to return the flash size (instead of 0x110).

J-Link>mem 0x1000010c 4 1000010C = 12 05 00 00

Reading from 0x110 returns 0xFFFFFFFF

INFO.PACKAGE and INFO.VARIANT also seem to return 0xFFFFFFFF. Is this just a 'feature' of the A0 silicon?

[Susheel Nuguru]

Because these registers are written by production tool, seems like there is a fault in writing to these info registers at time of production. I have created an internal ticket for this. But I am not sure what could be done to already shipped kits. We will atleast make sure that this is fixed soon and the current chips going out.

Do you use this registers in your application? It does not stop you in your development right

[RK]

I came across this today as well. However it seems that not-only is the value for FLASH size in the place where the value for RAM size should be, it's also the wrong number. The value there is (as chris notes) 0x00000512, which is 512 in binary coded decimal, the manual however says it should be 0x00000200, as in 512 in binary.

So is it just the flash size is in the wrong place but is correctly '512' as a binary coded decimal, and the manual is wrong, or is it not only in the wrong place, but is also the wrong number, and the manual is correct?