Hi, I watched your talk and it looks like exactly what I need but sadly I still couldn't get it to work. I set up the baremetal plugin as described here:
http://doc-snapshot.qt-project.org/qtcreator-3.1/creator-developing-baremetal.html But I had two problems: a) what to use as the debugger, and b) what to use in the run settings. a) As you can see in the screenshot on the linked page they don't define a debugger. If you don't do this, when you start debugging it prompts you for a debugger executable. In your talk I saw you have a debugger defined, but I don't really understand why it needs a debugger executable at all if it is just connecting to a remote GDB server. b) The page says you can use the default run settings, but for me that is an empty edit box for a custom executable which you are prompted to supply when you try to debug the program. Please can you explain a bit more? Thanks, Tim On 5 June 2014 21:49, Tim Sander <[email protected]> wrote: > Hi Tim > Am Donnerstag, 5. Juni 2014, 21:30:03 schrieb Tim Hutt: > > Ah fantastic. I didn't know about the Bare Metal plugin. And fortunately > I > > already have a working QBS file! > Please let me know how good the j-link worked for you. It was flaky when i > tried it last year. But if the j-link gdbserver is to flaky you can also > use > openocd which also has an j-link backend. > > Best regards > Tim >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
