topic Re: S32K144 EEPROM partition error in S32K

S32K144 EEPROM partition error

lengrudie — Tue, 06 Dec 2022 01:53:53 GMT

I use S32K144-Q100 .

By default, the FlexNVM partition of the chip is 4 (that is, 64k E-Flash), but I want to change it to partition code 3 (that is, 32k E-Flash), but after using the 0x80 command, an ACCERR error is prompted. Please give me a suggestion on how to change the partition code?

Look forward to your reply.

Re: S32K144 EEPROM partition error

Robin_Shen — Tue, 06 Dec 2022 09:06:24 GMT

Hi lengrudie,

Please read the "3.1.1.1 Program partition command requirements" of AN11983: Using the S32K1xx EEPROM Functionality – Application Note

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: S32K144 EEPROM partition error

lengrudie — Wed, 07 Dec 2022 01:04:50 GMT

I did not notice this information, thank you! I tried to use the erase instruction 0x44, but this instruction will also prompt an ACCERR error after it is executed. What's the matter? I hope you can give me some advice and look forward to your reply! thank you!

Re: S32K144 EEPROM partition error

Robin_Shen — Wed, 07 Dec 2022 02:33:05 GMT

Partitioning must only be done once. Please mass erase the MCU.

Re: S32K144 EEPROM partition error

lengrudie — Wed, 07 Dec 2022 05:37:41 GMT

When I use JLINK to execute, the chip locks and prompts "Device is secure, Erase to unsecure?"Does that mean the chip will not work?Can I solve it?

Re: S32K144 EEPROM partition error

Robin_Shen — Wed, 07 Dec 2022 05:47:32 GMT

How did you mass erase? SEGGER J-Link Commander and J-Flash is able to mass erase. Click Yes when prompts "Device is secure, Erase to unsecure?" should also trigger mass erase. After mass erase, you should able to program the chip again. If not, please check the values of MDM-AP status and control registers by refer to: Unbricking S32K146