The S32K144\S32K148 program cannot be burned.

Peterzp

The S32K144\S32K148 program cannot be burned. [Copy link]

(S32K144 development board and S32K148 development board) I used the EB configuration tool provided by NXP to configure the MCU module and the PORT module. The port only configured PTB5 as the CLKOUT output. The frequency is 4MHz. After the program was downloaded, the oscilloscope tested that the PTB5 frequency was 4MHz. But then I couldn't re-burn the program (the debugger couldn't connect to the chip). I tried restarting, changing the computer, changing the debugger, and changing the compiler, but I couldn't burn the program again. However, after each charge, the oscilloscope tested that the PTB5 frequency was still output normally, so there should be no problem with the program inside the board, but it can't be re-written. I suspected that the chip was locked before, and I wanted to use the debugger to unlock it, but after powering on, the debugger couldn't find the chip. I don't know what the problem is. The same problem occurred on both S32K144 and S32K148 boards.

prayer_hong

Encountered the same problem

Peterzp

prayer_hong posted on 2018-10-10 08:21 I encountered the same problem

What did you do to cause this problem? Can you describe it? Thank you!

prayer_hong

Peterzp posted on 2018-10-10 09:40 May I ask, what did you do to cause this problem? Can you describe it? Thank you!

It's not me who did it. My colleague downloaded a program and changed the memory area. Originally it was like this: m_interrupts (RX): ORIGIN = 0x00000000, LENGTH = 0x00000400 m_flash_config (RX): ORIGIN = 0x00000400, LENGTH = 0x00000010 m_text (RX): ORIGIN = 0x00000410, LENGTH = 0x0007FBF0 It was changed to this: m_text1 (RX): ORIGIN = 0x00000000, LENGTH = 0x00000100 m_interrupts (RX): ORIGIN = 0x00000100, LENGTH = 0x00000400 m_flash_config (RX) : ORIGIN = 0x00000500, LENGTH = 0x00000510 m_text2 (RX) : ORIGIN = 0x00000510, LENGTH = 0x0007FAF0

Peterzp

The problem has been solved. https://community.nxp.com/thread ... 7127#comment-857127

prayer_hong

Peterzp posted on 2018-10-12 14:25 The problem has been solved. https://community.nxp.com/thread/439921?commentID=857127#comment-857127

I have tried all these methods, maybe it is because mass erase has been turned off