hello
I have three questions:
<1>
The following command description is conflict
The first picture description:secure byte is erase , MCU is security
but the second picture description: release MCU security
which one is wrong?
thanks in advance.
<2>
when MEEN=10, mass erase can't be erase, is it right? but why the follwing command can't be supported?
<3> I didn't understand when the order would be used, for example Erase all block & erase all block unsecure? when execute the code is erased, MCU is not working, so what is the necessity of these two commands?
Hello Kui Wu,
1.
I don't see any conflict.
Erase All Block Command only releases the security in the FSEC[SEC] register.
Whereas
Erase All Block Unsecure Command programs the SEC bits in the Flash Configuration field to the unsecure state (0b10).
2.
This is the mass erase command
3.
It allows either erasing the whole memory including flash configuration field (SEC = 0b11) or erasing the whole memory and program the flash configuration field to unsecure state (SEC = 0b10).
Regards,
Daniel
hello Daniel,
Erase all blocks unsecure command is the same command with Debugger's mass erase?
Hello Kui Wu,
Please take a look at AN12130 Production Flash Programming Best Practices for S32K1xx MCUs
BR, Daniel
Dear Daniel,
So Erase all blocks unsecure command and debugger mass erase command is the same command? because their
action are the same.
Hello Kui Wu,
The difference is that Erase All Blocks Unsecure is available internally whereas Mass Erase is available externally but they both do the same.
Regards,
Daniel
Hello,
I'm sorry for the delay.
When MEEN = 0b10, Mass erase is disabled.
So yes, it will fail.
Regards,
Daniel