storing critical data in S32K144

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

storing critical data in S32K144

680件の閲覧回数
d_shivamkumar
Contributor III

Problem background:

I am using S32K144 for storage of credentials (critical data). 

Generally S32 is having 2 options to store data: 1. using MPU module 2. using cSEC module

I am using FTFC module for protecting a portion of memory. This credential will be stored in a plain text and communicated via encryption (encryption keys is stored in cSEC module). 

Problem statement:

For the first time when I'm trying to store the data into either p-flash or d-flash I need a dedicated code for that which uses memory erase and write functions for the same. After that I am running the actual application code where I'm using those credentials. When I'm flashing the new code (application code), entire memory portion gets erased. 

How to store the credentials in some portion of memory, which won't affect even after flashing the new code??

 

0 件の賞賛
1 返信

662件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @d_shivamkumar,

You can use the Program Once field that can't be erased, but there is only 64bytes available.

danielmartynek_0-1625670993119.png

If you use a PE Micro programmer, the PE Micro Plugin in S32DS IDE allows preserving certain parts of memory during programming.

danielmartynek_1-1625671241155.png

danielmartynek_2-1625671273232.png

 

Regards,

Daniel

 

0 件の賞賛