2414684_en-US

[#1]

UTEST write data process

Hello

Does writing data to Utest require erasing?

UTEST_program.jpegUTEST_program.jpeg

The AN13388 said the process to write a data in the UTEST Sector is the same process used to program in other blocks.

However, UTEST is a one-time program, so does it need to be erased before writing?

Lika

回复： UTEST写数据流程I'd also like to know which areas of UTEST can be modified using DEBUG debugging.Re: UTEST写数据流程

Do not erase first; UTEST Sector is an OTP (One Time Programmable).

Example_S32K344_decouple_RTD400_Ip_C40_DS35 contains a UTEST example for your reference.

I apologize, I didn't understand "Which areas can be modified via DEBUG during UTEST". Do you mean executing a standard Flash Program sequence (the same process described in AN13388) by manipulating registers during debugging? See "Table 837" in S32K3XXRM.pdf Rev12.The phrase "Debug access based on LifeCycle and bit configurations" mentions debug permissions at different LifeCycle stages. Are you referring to this?

The Accessibility and Programmed by columns of the UTEST Memory Map table in the attachment S32K3xx_DCF_clients.xlsx to S32K3XXRM.pdf specify the permissions. Additionally, different colors indicate read/write permissions for different Lifecycles.

Re: UTEST写数据流程Yes, during debugging, can the UTEST content be modified in the CUST_DEL LC stage by executing a standard Flash Program sequence through register manipulation? I want to clear some positions of 1 to 0.Re: UTEST写数据流程

Please refer to the answer in utest nvm user space programming .

Re: UTEST写数据流程Okay, thank you very much.