[Qt-creator] Crash while Bare-Metal Debugging on Windows
tim at krieglstein.org
Mon Oct 6 22:40:08 CEST 2014
Sorry for the late reply...
> > I am trying to debug applications running on a TI CC3200 (Cortex-M4)
> > device using QT Creator's Bare Metal plugin. I got to the point where
> > I can load and debug, however, QT Creator crashes when I attempt to
> > interrupt the program or set a breakpoint while the program is running.
> > I found the earlier discussion on this list and have checked the "use
> > asynchronous mode to control the inferior" option, however this makes
> > no difference.
> Yes there is unfortunatly a bug i have get around.
> > In case this is relevant, I see the note "INFERIOR STILL RUNNING IN
> > STATE InferiorRunOk" in the debugger log.
> > This is on Windows 7. The connection to the target is done using a
> > Cygwin-built OpenOCD 0.8.0 started separately on the console and
> > using a TCP/IP connection to gdb.
> > Any suggestions?
> Could you open the debugger log window pane and copy attach the gdb commands
> and replys. Also it would be interesting which gdb version of the debugger
> you are working with.
> You could also try to start a debug session by hand:
> gdb binary
> target remote 3333
> monitor reset halt
I have not seen anything suspicious in the logs. But i think you haven't set
up the debug hardware in your cortex m4. You must switch off the powerdown of
the jtag interface in wfi. You can put this in your openocd startup script.
See http://nuttx.org/doku.php?id=wiki:howtos:jtag-debugging for some details.
More information about the Qt-creator