S32K3 1/2MB C40asf Program Erase Cycle – How to detect failure

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

S32K3 1/2MB C40asf Program Erase Cycle – How to detect failure

328件の閲覧回数
not_a_duck
Contributor III

The Datasheet states that the plfash sectors can handle at least 1000 P/E cycles for the 1mb and 2mb flash block variants. 
Aside from the fact that this seems horrendously low, how is this meant to work in practice?

Does this mean you can only update the firmware 1000 times in the field?

What is the failure mode after the 1000 cycles?
How can i detect if it is failing?
Do i need to track my number of p/e cycles to prevent exceeding it?

I don't expect to update 1000 times in the field, but I certainly will update firmware more than 1000 times during development and also for automated test setups. 

0 件の賞賛
返信
1 返信

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

Hi Luis-Johannes,

1000 is the minimum guaranteed number of cycles.

Above that, there is a risk the flash might be incorrectly erased/programmed resulting in ECC issues.

 

Regards,

Daniel

 

0 件の賞賛
返信