kinetis k60 twr osbdm problem

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

kinetis k60 twr osbdm problem

904 Views
Kantaro
Contributor I

Hi all,

 

i am trying to debug my app via osbdm on twr-k60n512.

i am using openocd(version 0.6.0), and the target is recognized well.

also some basic commands like "reset init" or "target halt" works fine(in terminal).

 

Info : OSBDM has opened
Info : clock speed 1 kHz
Info : JTAG tap: k60.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
Info : k60.cpu: hardware has 6 breakpoints, 4 watchpoints

 

 

when i am starting debugger in eclipse it's look OK but when i press RESUME i've got

target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
Error: GDB missing ack(2) - assumed good
Warn : acknowledgment received, but no packet pending
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1001). Workaround: increase "set remotetimeout" in GDB

 

 

i am using arm-eabi-gdb debugger with this commands:

target remote localhost:3333
monitor reset init
monitor halt
load

break main

 

am i missing something?

 

best regards,

 

Filip.

 

 

 

 

0 Kudos
1 Reply

318 Views
JanDakinevich
Contributor I
> target halted due to debug-request, current mode: Thread > xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc > Error: GDB missing ack(2) - assumed good > Warn : acknowledgment received, but no packet pending > Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1001). Workaround: increase "set remotetimeout" in GDB > > i am using arm-eabi-gdb debugger with this commands: I am not sure that your question is still relevant. But did you try to build gdb for arm-none-eabi target, not arm-eabi?
0 Kudos