topic S32K144 no access via debug interface in S32K

S32K144 no access via debug interface

koehlerl — Mon, 22 Mar 2021 15:58:37 GMT

Hello Together,

i have some problems with a S32K144. I was able to debug and flash the device for quite some time.
I have prgrammed the S32K144 from a seond controller via SWD but I must done somting wrong.
Now it is not more posibble to connect the prozessor with debug interface.

The content of console:

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link V10 compiled Jan 7 2019 14:00:10
Hardware: V10.10
S/N: 50111539
Feature(s): GDB
Checking target voltage...
Target voltage: 3.28 V
Listening on TCP/IP port 2331
Connecting to target...
J-Link found 1 JTAG device, Total IRLen = 4
JTAG ID: 0x1993D01D (Cortex-M4)
Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00000000 (Data = 0x20007000)
Read 2 bytes @ address 0x00000000 (Data = 0x7000)
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0000069C)
Received monitor command: regs
R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000, R13= 20007000, MSP= 20007000, PSP= 00000000
R14(LR) = FFFFFFFF, R15(PC) = 0000069C
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x0000069C (Data = 0xF04FB672)
Read 2 bytes @ address 0x0000069C (Data = 0xB672)
Received monitor command: speed auto
Select auto target interface speed (4000 kHz)
Received monitor command: flash breakpoints 1
Flash breakpoints enabled
Received monitor command: semihosting enable
Semi-hosting enabled (Handle on BKPT)
Received monitor command: semihosting IOClient 1
Semihosting I/O set to TELNET Client
Read 4 bytes @ address 0x0000069C (Data = 0xF04FB672)
Read 2 bytes @ address 0x0000069C (Data = 0xB672)
Downloading 1024 bytes @ address 0x00000000 - Verified OK
Downloading 16 bytes @ address 0x00000400 - Verified OK
Downloading 220 bytes @ address 0x00000410 - Verified OK
Downloading 4 bytes @ address 0x00000500 - Verified OK
Downloading 44 bytes @ address 0x00000504 - Verified OK
Downloading 24 bytes @ address 0x000005C0 - Verified OK
Downloading 24 bytes @ address 0x000005E0 - Verified OK
Downloading 16152 bytes @ address 0x000005F8 - Verified OK
Downloading 16160 bytes @ address 0x00004510 - Verified OK
Downloading 15920 bytes @ address 0x00008430 - Verified OK
Downloading 16048 bytes @ address 0x0000C260 - Verified OK
Downloading 16304 bytes @ address 0x00010110 - Verified OK
Downloading 13168 bytes @ address 0x000140C0 - Verified OK
Downloading 4 bytes @ address 0x00017430 - Verified OK
Downloading 4 bytes @ address 0x00017434 - Verified OK
Downloading 1908 bytes @ address 0x00017438 - Verified OK
Downloading 8816 bytes @ address 0x00017BAC - Verified OK
Downloading 16368 bytes @ address 0x00019E20 - Verified OK
Downloading 16 bytes @ address 0x0001DE10 - Verified OK
Read 4 bytes @ address 0x0000069C (Data = 0xF04FB672)
Read 2 bytes @ address 0x0000069C (Data = 0xB672)
Read 2 bytes @ address 0x000030B2 (Data = 0xF002)
Read 2 bytes @ address 0x000030B2 (Data = 0xF002)
Received monitor command: clrbp
Received monitor command: reset
Comparing flash [....................] Done.
Erasing flash [....................] Done.
Verifying flash [....................] Done.
ERROR: Timeout while restoring target, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x81000003)!
Failed to restore target. RAMCode never stops
Failed to erase sectors 8 @ address 0x00008000 (unspecified error)
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0000069C)
Read 2 bytes @ address 0x000030B2 (Data = 0xF002)
Read 2 bytes @ address 0x000030B2 (Data = 0xF002)
Read 2 bytes @ address 0x000030B2 (Data = 0xF002)
Received monitor command: regs
R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000, R13= 20007000, MSP= 20007000, PSP= 00000000
R14(LR) = FFFFFFFF, R15(PC) = 0000069C
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x0000069C (Data = 0xF04FB672)
Read 2 bytes @ address 0x0000069C (Data = 0xB672)
Setting breakpoint @ address 0x000030B2, Size = 2, BPHandle = 0x0001
Starting target CPU...

Lutz

Re: S32K144 no access via debug interface

petervlna — Tue, 23 Mar 2021 12:51:54 GMT

Hello,

Is it possible to attach to running target?

Try some example code instead of the current one. It is possible that your project is rewriting RAM where is Segger code, etc...

Could you try it with PEMicro?

best regards,

Peter

Re: S32K144 no access via debug interface

koehlerl — Tue, 23 Mar 2021 16:07:32 GMT

It is possible to connet the target.

But it does not work.

There are wrong things in the memory?

It is possible to damge or lock the prozessor with wrong flash programming.

BR Lutz

Re: S32K144 no access via debug interface

petervlna — Wed, 24 Mar 2021 10:54:53 GMT

Hello,

It is possible to damage or lock the processor with wrong flash programming.

Sure that's possible. You can lock it by erasing the boot header.

You also have lots of ECC errors in flash, which can cause a lot of issues. Looks like your programming wasn't finish or done properly.

Is it possible to load any example code to the device?

Best regards,

Peter

Re: S32K144 no access via debug interface

koehlerl — Wed, 24 Mar 2021 12:14:26 GMT

Hi,

yes it possible to load code to the device.

But the result is what you see in the last post in the memory browser.

Some flash is ok, but some regions have the problem with the error '?'

How can I 'repair' the fash?

BR Lutz

Re: S32K144 no access via debug interface

petervlna — Thu, 25 Mar 2021 09:42:41 GMT

Hello,

You can simply reprogram (by any example code) flash or erase it via debugger or via application.

Have in mind to not leave empty boot vector at address 0x0 or the device will be locked.

best regards,

Peter

Re: S32K144 no access via debug interface

koehlerl — Thu, 25 Mar 2021 09:54:09 GMT

Hi,

the problem ist, that the erase, reporgramming via debugger don't work correct.

Some memory regions have the problem with flash error. See meomery browser '?'.

So the application don't run. What must I do, that the flash is reprogrammed correct?

Lutz

Re: S32K144 no access via debug interface

koehlerl — Tue, 30 Mar 2021 07:32:31 GMT

I need support to solve the problem !!!

Re: S32K144 no access via debug interface

petervlna — Tue, 30 Mar 2021 10:14:40 GMT

Hello,

the problem ist, that the erase, reporgramming via debugger don't work correct.

Did you try it with PEMicro or Lauterbach? Or only via Segger? If you erase the memory from debugger, do you see success erase and the memory is still corrupt?

Do you see the issue on all devices or on just one?

So the application don't run. What must I do, that the flash is reprogrammed correct?

You need to erase/program memory correctly to have matching data with ECC syndrome in memory.

best regards,

Peter