KDS 3.2.0 Behavior

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

KDS 3.2.0 Behavior

6,687 Views
richardfox75
Contributor III

I randomly suspend execution of the program being debugged. When I resume

execution, the program breaks at the instruction that was being executed at

the time of the suspend. This is causing me trouble because I am trying to

collect function execution times. I cannot reach the breakpoint which is where

I want to suspend to observe timings, without hitting this temporary breakpoint

which is always applied. It only gets removed by manually removing it. And

then it comes back.I have been using KDS for several months, and this never

happened before.

 

Also, I have been planting breakpoints in a particular file for many weeks. Now

suddenly whenever I attempt to plant a breakpoint, KDS prompts for entering

a "Book Mark". I have not been able to resolve this by performing a clean build.

Changing code in the file, re-compiling, and restarting the program execution

does not fix this. This just all of a sudden happened. For the past week I have

not been able to plant breakpoints in this file. What will resolve this?

Labels (1)
0 Kudos
Reply
23 Replies

588 Views
richardfox75
Contributor III

Jorge,

Yes the temporary breakpoint that I see is the same as your picture.

I have removed the breakpoint only to have it re-appear. Again it

happens following suspending program execution. I realize that the

breakpoint is due to halting the program. But once it is set I can never

get rid of it. It keeps coming back. The only way that I have been able

to get around this is by pressing the "skip all breakpoints". The

breakpoint

still shows up at the same address, but at least the program does not

halt.

Dick Fox

Firmware Engineer

NATIONAL CONTROLS CORPORATION BUSINESS UNIT

INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION

1725 Western Dr | West Chicago, IL 60185 | http://www.ametekncc.com

Phone: (630)621-3118 | email: Dick Fox@ametek.com

0 Kudos
Reply

588 Views
jorge_a_vazquez
NXP Employee
NXP Employee

Hi Richard Fox

I could replicate your issue, it just happened when you use the P&E interface to debug, hence I am not sure if this problem is because the KDS 3.2. I reported this behavior with P&E micro and I'll keep you informed.


Best Regards
Jorge Alcala

0 Kudos
Reply

588 Views
richardfox75
Contributor III

Thanks

Dick Fox

Firmware Engineer

NATIONAL CONTROLS CORPORATION BUSINESS UNIT

INSTRUMENTATION AND SPECIALTY CONTROLS DIVISION

1725 Western Dr | West Chicago, IL 60185 | http://www.ametekncc.com

Phone: (630)621-3118 | email: Dick Fox@ametek.com

0 Kudos
Reply