[Qt-creator] QtC vs BareMetal vc CMake

Wolfgang BETZ wolfgang.betz at st.com
Mon Mar 23 09:23:29 CET 2015


On 03/23/2015 09:00 AM, Tim Sander wrote:
> Hi Wolfgang
>> On 03/20/2015 09:47 PM, Tim Sander wrote:
>> So please check at first that you have really the baremetal kit configured.
>> If the kit is baremetal, check the run config of your project. You can
>> create different run controls and there should be a baremetal runcontrol in
>> the list available.
>>
>> thanks a lot, I found my problem! I didn't realize that the different run
>> controls in the list were not just different executables but also the
>> versions with the additional text "(on GDB server or hardware debugger)"
>> and that these referred to using the baremetal runcontrol ...
> Glad you found the error. If you have any idea how to improve that usability
> wise or any other point just let us know.
Well, I simply failed seeing that for each executable in my project 
there were to versions in the run configuration list, also because these 
did not appear in the list of potential run targets under the general 
left pane button for selecting the target (the one with the terminal 
image just above the green start button). For a Target which uses 
BareMetal, it might make sense to enable these targets by default.

>
>> Thanks a lot again and sorry for my interruption :-(
> I guess you are working with st chips, so i would recommend using one of the
> latests openocd's master branch version.  Also looking at your e-mail address:
> The openocd backend for the st-link is -as far as i know- reverse engeneered,
> so if you know someone in your company which could improve that situation that
> would be nice.
Actually I am working in a R&D organization and am not dealing with the 
standard ST products like e.g. the STM32 families, so I am not in 
contact with the business org which deals with these chips, but I will 
forward your suggestion to one of my colleagues who is in charge of 
taking care for the development environment for the prototype 
architecture I am working with. He will know much better who to ask to.

>
> Also i have seen that you have not set the available number of breakpoints und
> watchpoints in you init commands, so i would recommend to add s.th. like:
> set remote hardware-breakpoint-limit 6
> set remote hardware-watchpoint-limit 4
> Where the number is of course depending on your hardware.
Yes, you are completely right, but you know, working with prototypes is 
often about reducing the number of commands issued in order to 
understand better why things are not working and actually I am not only 
struggling with bringing up QtCreator to work with my target board but 
in general to bring up the target board to get it to be more friendly 
when trying to debug it ;-)

Thanks again & have fun!
Ciao Wolfgang


More information about the Qt-creator mailing list