KDS 3.2 debug mode not working with KL03Z32M4

[thomasedel]

I'm trying to get the new 3.2 KDS software to work on Windows 7 with PEMicro Interface Debugging.  The 3.1 software was working fine with my target application.  When I try to run the 3.2 software, with the same project imported to it, it seems to build fine, and loads the firmware fine.  When it is run in debug mode it will run for a while (to a breakpoint not too far along), but at some point the debug interface seems to  loose control.  The target keeps running, but the debug interface stops.  With at typical failure the debug pane shows the following:

KL03Z-SPCM3_Debug_PNE [GDB PEMicro Interface Debugging]

KL03Z-SPCM3.elf

  Thread #1 (Suspended : Signal : SIGTRAP:Trace/breakpoint trap)

    0x200005e0

    0x200005e0  C:\Freescale\KDS_v3\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_2.3.6.201602211227\win32\pegdbserver_console

  arm-none-eabi-gdb

Seems like my problem has something to do with the "Suspended : Signal : SIGTRAP:Trace/breakpoint trap".  Seems like I'm lacking some basic understanding about what is happening with that.  Any help would be appreciated.  Please let me know if the info I have provided is not enough. 

Note:  When the debugger stops, the disassembly view shows stopping at line 0x200005e0 (at the end of SRAM).  With no associated source code.  Not sure how it gets there, or why.

[Alice_Yang]

Hello Thomas,

Which emulator do you used ? And  where did you download the  12.3.0 driver?I will test it on my side .

BR

Alice

[thomasedel]

Greetings Alice:

I am using a modified FRDM-KL03Z board, with the built-in Open SDA interface (USB connection) along with the P&E Micro driver for it.

I’m pretty sure the P&E Micro 12.3.0 driver was included with the recent KDS 3.2 software download from the NXP website, but it is also available from the P&E website.  The 11.7 P&E driver was downloaded from P&E Micro last August (no longer on their website).

Thanks for your help.

-Thomas

[Alice_Yang]

Hello Thomas,

About use which driver to debug , please go to the OpenSDA Serial and debug adapter web

OpenSDA Serial and Debug Adapter|NXP

to check , input your board name , then it will show the result :

After you download the P&E Micro v114(binary) folder , you can find the driver for FRDM-KL03:

Hope it helps

Alice

[thomasedel]

Greetings Alice:

Thanks for the info.  I'm running ok now with KDS 3.1, PE Micro 11.1.1 driver, and PE Micro v114 firmware.  If I have further problems, I'll try the PE Micro v118 firmware.

Thanks for your help.

-Thomas

[Alice_Yang]

Hi Thomas,

Ok !

BR

Alice

[thomasedel]

After doing some more comparisons and re-installations, it appears that the problem lies with the P&E Micro debug driver version.  Only the version 11.1.1 driver originally supplied with the KDS 3.0.0 software appears to work for my application.  The version 11.7.0 version driver (downloaded last August from P&E Micro) and the 12.3.0 version (supplied with KDS 3.2, or available from P&E Micro) apparently do NOT work with my application.

I would appreciate any help regarding how to make the new 12.3.0 driver work, as the previous 11.* versions apparently are not compatible with Windows 10, and it would be nice to be able to install and use the latest KDS software.

-Thomas

[Alice_Yang]

Hello Thomas,

How many breakpoints do you set ?

And what about your project ,  in order to quickly check ,

you can send your project to me , i can test it on my side .

BR

Alice

[thomasedel]

Greetings Alice:

Clarifying my original post:  I'm trying to get KDS 3.1 or 3.2 to work on a 2nd computer, which is running Windows 10.  The original post refers to my (1st) computer running Windows 7.  I am getting the same error on either install on the 2nd computer (KDS 3.1 or KDS 3.2).  This seems to show that the problem is not new to the KDS 3.2 version.  I have KDS 3.1 working on my computer (the 1st computer), but KDS 3.2 will not (as described in the original post).  Looks like a configuration issue at this point. 

I'm now focusing on a warning at the end of the debug initiation, which occurs in all non-working installs on both computers (in the debug perspective, console pane), which does not show up on my working KDS 3.1 version on the 1st computer.  The warning reads:

"WARNING - NO RESET SCRIPT FILE HAS BEEN CONFIGURED TO RUN!!!

TO MODIFY THE RESET SCRIPT SETTINGS, USE THE FOLLOWING MENU OPTION:

CONFIGURATION -> AUTOMATED SCRIPT OPTIONS"

I am unable to find where these "reset script file" settings are defined.  The referenced "menu option" does not appear to exist. Please comment if you can help with resolving that warning.  Thank you in advance!

-Thomas

[Alice_Yang]

Hello Thomas,

Please create one simple project on the KDS 3.2 to check whether it can work well .

Then run another  KDS 3.1 proejct on KDS3.2 to check .

BR

Alice

[thomasedel]

Greetings Alice:

The problem seems to be independent of the number of breakpoints set.  I've disabled all breakpoints I'm aware of, except the automatic one at the beginning of the program, and the debug interface still fails.  I recall, however, that it seems as though turning off all breakpoints globally (via the button left of the run button) did not seem to work (the program still stopped at breakpoints that were set, if it didn't fail first).  So, it does seem like the problem may be related to breakpoints.

I'm not comfortable sending my program in at this point, but thanks for the offer.  Seems like it's a KDS issue, since my program runs well on KDS 3.1, but not 3.2.  I'm don't think you could meaningfully run my program without the custom hardware it runs with, and I'm not comfortable disclosing too much about my application.  Maybe I'm missing something here.  I might be willing to change my mind on that point.  Feel free to clarify.

Thanks for your help with this.

-Thomas