topic Re: Debugging issue with KEA128 in Kinetis Microcontrollers

Debugging issue with KEA128

0815 — Fri, 11 Dec 2015 08:09:28 GMT

I have an heavy debug issue with a custom designed KEA128 board:

After starting the debugger I'm not able to step through the program (F5 or F6). I'm using the PE Multilink Universal Debugger and the S32 Design Studio with PE plugin. On other workspaces and the same toolchain the debugging works flawlessly. I'm running into a similar issue if I try to debug this workspace on a TRK-KEA128 evaluation board via OpenSDA. So it seems this issue has something to do with this projects workspace.

Here is what I'm getting in the console windows:

GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.1.20141128-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
monitor preserve0 0
monitor selectcore 0
continue
Continuing.
Note: automatically using hardware breakpoints for read-only addresses.
Temporary breakpoint 1, main () at ../source/main.cpp:53
53 PE_low_level_init();
No breakpoint number 1.

and

Connection from "127.0.0.1" via 127.0.0.1
Copyright 2012 P&E Microcomputer Systems,Inc.
Command Line :C:\Freescale\S32_ARM_v1.0\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_2.2.5.201511061812\win32\pegdbserver_console -device=Freescale_KEx_S9KEAZ128M4 -startserver -singlesession -serverport=7224 -interface=USBMULTILINK -speed=5000 -port=US
CMD>RE
Initializing.
Target has been RESET and is active.
CMD>CM C:\Freescale\S32_ARM_v1.0\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_2.2.5.201511061812\win32\gdi\P&E\supportFiles_ARM\Freescale\KEx\freescale_s9keaz128m4_pflash.arp
Initializing.
Initialized.
;version 1.03, 06/02/2014, Copyright 2014 P&E Microcomputer Systems, Inc. All rights reserved. www.pemicro.com [ke_128k_pflash_ftmre_m0]
;device freescale, s9keaz128m4, pflash
;begin_cs device=$00000000, length=$00020000, ram=$20000000
Loading programming algorithm ...
Done.
CMD>EM
Erasing.
Module has been erased.
Initializing.
Initialized.
;version 1.03, 06/02/2014, Copyright 2014 P&E Microcomputer Systems, Inc. All rights reserved. www.pemicro.com [ke_128k_pflash_ftmre_m0]
;device freescale, s9keaz128m4, pflash
;begin_cs device=$00000000, length=$00020000, ram=$20000000
Loading programming algorithm ...
Done.
CMD>PM
Programming.
Processing Object File Data ...

.
Programmed.
CMD>VC
Verifying object file CRC-16 to device ranges ...
   block 00000000-000000BF ...
Ok.
   block 00000400-0000BBCF ...
Ok.
   Checksum Verification Successful. (Cumulative CRC-16=$FF3B)
CMD>RE
Initializing.
Target has been RESET and is active.
Preset breakpoint encountered.

Any ideas?

Thanks in advance!

Re: Debugging issue with KEA128

Carlos_Mendoza — Wed, 16 Dec 2015 16:12:08 GMT

Hi 0815,

Please make sure you didn't select "Skip all breakpoints" button:

And then try removing all breakpoints and setting a new one.

Hope it helps!

Best Regards,

Carlos Mendoza

Technical Support Engineer

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

Re: Debugging issue with KEA128

0815 — Thu, 17 Dec 2015 06:53:45 GMT

You are right, it is embarrassing. :smileyblush:

Re: Debugging issue with KEA128

Lukas_Frank — Tue, 31 Jan 2023 12:20:03 GMT

Hi Dear @Carlos_Mendoza ,

I have same issue. How did you solve it?

Here is my issue:

https://community.nxp.com/t5/i-MX-RT/IMXRT1064-PEMicro-Debug-Error-During-Flash-Programming/m-p/1590347#M23511

Thank you.

Re: Debugging issue with KEA128

Carlos_Mendoza — Wed, 01 Feb 2023 20:01:33 GMT

Hi @Lukas_Frank ,

Is this the first time you load a demo application into the board? Please make sure that your board is configured for internal boot and not for serial downloader mode.

Regards,

Carlos Mendoza

Re: Debugging issue with KEA128

Lukas_Frank — Thu, 02 Feb 2023 08:04:22 GMT

Hi Dear @Carlos_Mendoza ,

I used internal boot mode as you mentioned. But I think the issue related with my debug configuration. I am using J34 in EVK. But I think I need to use LPC-Link2 Debug Probe for debugging with J34. Could you please clarify me about Am I able to debug with J34 or not? Because reference manual says below and I thought that I will be able to debug my card with J34 if I use FreeLink Interface's JTAG connector. Does this JTAG Connector supports debugging?

First Clue:

Second Clue:

Thanks for your help.