[Qt-creator] BareMetal Target Plugin Configuration

[Tim Sander]

Hi Jeandet
> We discuss a little about your plugin on the Qt mailing list, first your
> plugin a very good feature for Qtcreator.
> I tried to look how to use it, I started with this help:
> http://doc-snapshot.qt-project.org/qtcreator-3.0/creator-developing-baremeta
> l.html
Well you need a hardware debbuger backend which qtcreator needs to connect to.
The backend is not started automatically as some of the hw debuggers have 
their own gui and it seemed the simplest to just let the user start the hw 
debugger on its own.

I have tested OpenOCD and some comercial offerings. 
> But few things are unclear to me, is this version allowing me to debug
> (step by step and breakpoint) my code? If yes I don't understand what
> are all the fields for the configuration:

> For the device I use the same as you (localhost same port ...)
This should work. Basically you can test your hw debugger by starting your
gdb on command line and test the the session over there.
The commands would be 
gdb-arm-none-eabi executable
target remote localhost:<portnr>
monitor reset halt
load
monitor reset halt
cont

> But for for the kit I have my own qt kit for STM32F4 which works. I just
> set the debugger to arm-none-eabi-gdb.
So you are using the qmake build system. I would recommend you to use the
qbs build system where you don't need a fake-qt setup. 

> Then for the run settings I really don't understand. In my case use
> st-util -p 3333 on linux to start a gdb server, if I put this as custom
> executable, on run it load the code on the target but on debug it says
> that /usr/bin/st-util: not in executable format...
I have not tested with st-util. But as it offers an gdb server it should work 
fine. But you have to start the st-util backend alongside qtcreator by 
yourself. The host and port describe the port of the debugger.
The command window lets you enter the custom hw debugger monitor commands
to load the code into the device and reset the pc to the start command.

If its not working, you should post the debugger log output from the debugger 
log output window.

Best regards
Tim