Please check S32K RM document error (flash part)

[kmh48301]

Hello.

I found some error in s32k rm document. so please check and fix it.

This source code is just flash_partitioning example.

1.

as you can see, MCU security status is unsecure. before erase all block

 but, after erase all block, the sec field is still same.

so the mcu security status is still unsecure.

s32k rm p844

but, in rm, erase all block command make the MCU status secured....

and weird thing

 rm 863p

On this part in RM, 

I'm confused.

 

In my opinion, after erase all block command (no reset yet)

in data flash IFR, SEC field is secured state (erased state)

but in FSEC, SEC field is unsecured state. (because not loaded from IFR yet)

so, right after erase all block, I can use flash commands.

but after reset, i can't use flash commands becuase the FSEC[SEC] field became secured.

Check my understand please

2 I think this is mistyping error  (rm 824p 36.4.4.1.7 FPROT)

the number of the region is 32.

but on this table last number of the region is 32. so this table is saying the number of the region is 33.

As I calculate those 'start address' and 'end address' in that table, that contents is right.

(0x0011_c000 is came out when I put region number 31 into formula)

Please check

Thanks

Best regards,

Phillip

 

[danielmartynek · Accepted solution]

Hello Phillip,

1.

Your understanding is correct, the FSEC register is loader during the system reset.

When the MCU is secure, the FTFC commands can still be  internally by the application itself, but the debugger does not have access to it. 

2.

Yes, this is a typo, there should be 31.

Sorry for the confusion and thank you for pointing it out.

Regards,

Daniel

[kmh48301]

Thanks for replying!

https://community.nxp.com/t5/S32-SDK/P-amp-E-Connection-Assistant-error-occured-in-a-rush/td-p/11508...

Please check this post, too.. This is in a hurry.

Thanks

Best regards,

Phillip