LPC55s16 Read/Write protect

[dmiv]

Hi,

i read the manual up and down, backward and forward and could not find the answer to simple question whether LPC55s16 has a volatile or non-volatile readout protection. According to 

https://community.nxp.com/t5/LPC-Microcontrollers/Do-LPC5500-Series-MCUs-support-Code-Read-Protectio...

NXP TechSupport wrote "...This would need to be done directly in software...". But the main question is if this thing is volatile or non-volatile.

And what exactly, practically,  i have to do to set up this protection in one or the another case?

Thank you

[Alexis_A]

Hello @dmiv,

In the table 287, Lifecycle state descriptions mention that depending of the state some of the features are lock or unlock. So in some case the CMPA and the ISP are locked.

Best Regards,

Alexis Andalon

[dmiv]

Please let me know if you need more accurate and detail question.

Please let me know if you do not want to answer. 

Please let me know if you do not possess enough information.

Please let me know if you couldn't give a Kanga-rat's balls about me, LPC55s16, answers and questions combined.

I'd be appreciated in any case.

[dmiv]

Hi

Please let me know if you need more accurate and detail question.

Please let me know if you do not want to answer. 

Please let me know if you do not possess enough information.

I'd be appreciated in any case.

[dmiv]

Thank you for answer

You mean table 286. I saw it. Thank you. 

Let me see if i can put it another way. I can use PFR to develop appropriate protection. Should i do it "directly in software"? Can i do it from outside, from MCUXpresso, for example? 

[AleGuzman]

The Protected Flash Region PFR is the persistent storage for specific areas. This memory area is only accessible using ROM APIs or through blhost commands while in ISP mode. 

PFR is composed of 3 regions

CFPA Customer Field Programmable Area
CMPA Customer Manufacturing Programmable Area
NMPA NXP Programmed Area

Inside the CMPA, a key storage area including the PUF activation code and several key codes. 

Each region has a SHA256 hash digest field in the last 32 bytes. This digest is used during the deployment life-cycle state to cross-check integrity.