S32KのトピックRe: FPROT runtime unlock

FPROT runtime unlock

luca_toso — Tue, 08 Mar 2022 12:57:36 GMT

Hi all,

Is it possible without using debugger access or erasing the flash to unlock the FPROT bits at runtime?

Use case: we have some flash area that needs to be protected by erase and/or programming during normal product cycle.

It may be possible to require to update such areas during the lifetime of the product, i.e. sw update via bootloaders, parameters change or other.

If the FPROT is set in the NVM, how can we re-set the FPROT bits without erasing the FPROT flash sector?

K.R.

Re: FPROT runtime unlock

danielmartynek — Wed, 09 Mar 2022 11:41:11 GMT

Hi @luca_toso,

It is not possible to remove this FPROT protection.

And reprogramming the first sector is not recommended.

Ony the areas that do not get reprogrammed should be protected.

But access to the flash controller (FTFC) can be restricted in the Peripheral Bridge (AIPS-Lite) (OPACRA register)

Regards,

Daniel

Re: FPROT runtime unlock

luca_toso — Wed, 09 Mar 2022 15:47:46 GMT

Hello Daniel,

one more related question.

Is it possible to set only one bit in flash?

I am picturing following scenario: FPROT are unlocked and at some point of the development I want to protect some sectors without re-flashing the uC (e.g switching from development to production and then protect sectors).

In my understanding the minumum writable size in P/D-Flash with FCCOB0..BB is 64 bit (8 data byte), but the RM states that "In NVM Normal mode: The protection can only be increased, meaning that currently unprotected memory can be protected but currently protected memory cannot be unprotected. Since unprotected regions are marked with a 1 and protected regions use a 0, only writes changing 1s to 0s are accepted. This 1-to-0 transition check is performed on a bit-by-bit basis. Those FDPROT bits with 1-to-0 transitions are accepted while all bits with 0-to-1 transitions are ignored. "

How can we change only one bit in the NVM?

Re: FPROT runtime unlock

danielmartynek — Thu, 10 Mar 2022 13:45:51 GMT

Hi @luca_toso,

If one phrase is programmed (bits 1 -> 0), ECC checksum is generated for the data in that phrase (also bits 1 -> 0 in the inaccessible flash that holds the checksum).

To reprogram that phrase, the whole sector must be erased (all bits 0 -> 1 including the ECC checksum).

So that the new data can match the new ECC checksums.

But the FPROT registers (that are loaded from the NVM IFR during the reset sequence) can be ovewritten (to increase the protection only).

So, the application code can decide which sectors will be protected on top of the regions already protected in NVM.

Regards,

Daniel