S32K144W flash programming

[johandahlberg]

Hello,

I have a board with two S32K144 processors which is currently in serial production, but which I am trying to migrate to using S32K144W.

After completing migration of the code for one of the two processors I attempted to flash the second MCU as well. According to the log the SEGGER J-Link tool I use successfully connects to and identifies the second MCU, but fails programming the flash memory. I tried replacing the possibly faulty second MCU, but nothing changed.

I have contacted SEGGER, but they respond that they officially don't support the -W series yet and don't have any time plan for that either.

Are there any differences in flash memory programming between S32K144 and S32K144W which the programming tool must be aware of?

What other programming tools are available, which DO support S32K144W?

Best regards,

/Johan

[Robin_Shen · Accepted solution]

Hi Johan,

I am able to debug S32K144W with onboard(S32K14W-Q064)OpenSDA debugger(PEMicro firmware) in S32DS v3.4.

hello_world_s32k144w S32DSv3.4 SDK RTM4.0.3.png

Here you can see that S32K144WF512M8 and S32K142WF256M8 are in the Supported devices list of PEMicro: https://www.pemicro.com/arm/device_support/NXP_Automotive/S32K1xx/index.cfm

I remember that I could use J-Link to debug S32K14W-Q064 in S32DS v3.4 before.

There are some differences between S32K144 and S32K144W, please do not use the S32K144 project to test on S32K144W. It is recommended to test the project of S32K1 SDK for S32K144W.

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.
-------------------------------------------------------------------------------