1. 20 Apr, 2016 1 commit
  2. 30 Mar, 2016 1 commit
  3. 19 Jan, 2016 1 commit
  4. 16 Jan, 2015 1 commit
  5. 06 Jan, 2015 1 commit
    • Denis Shienkov's avatar
      BareMetal: Allow to manage configurations of HW GDB servers · 165f008d
      Denis Shienkov authored
      The user has only one possibility to setup of the remote GDB server
      when a new device is created (or to modify it for existing device).
      It is possible only in the host/port fields for connection to the
      GDB server. It is a little inconvenient for the user. If the user
      wants to use other configuration of the GDB server, then need every
      time to edit the current configuration.
      Improving this it is introduction a new concept with a new entity
      named as "GDB server provider". Now to the device debugging purpose
      the user can choose any of the GDB provider from the list (by analogy
      with toolchain and so on). Each configuration of GDB provider is
      created by the user manually on the new "GDB Server Provider" options
      page. This can be made before or after creation of device.
      A GDB server provider can work in three startup modes (depends on
      implementation of concrete provider):
      1) NoStartup mode.
      This means that we do not want to startup a provider, we just trying
      to connect to the already started GDB provider server. This mode uses
      the TCP/IP connection with manually specifying of remote host and port.
      2) StartupOnNetwork mode.
      This means that we want to launch of the GDB provider automatically
      before connect to it in process of remote debugging. This mode also
      uses the TCP/IP protocol. In addition to it, a GDB provider can has
      additional options which are contains a paths to provider executable
      file, to configuration files and so on (it is depends on concrete
      provider implementation). This mode (with NoStartup) covers about 90%
      of usecase, and is supported by most set of the GDB server providers.
      3) StartupOnPipe mode.
      This is similar to StartupOnNetwork mode and we also automatically
      starts the GDB server provider before debugging. But in this case is
      used the Pipe mode instead of TCP/IP. Not each of the GDB provider
      can support debugging via pipes.
      This patch has concrete implementations for a following set of the
      GDB server providers:
      * "Default" provider which supports only the NoStartup mode.
      * "Open On-Chip Debugger" (http://openocd.sourceforge.net/)
        provider which supports all modes.
      * "STLinkUtil" (https://github.com/texane/stlink)
        provider which supports NoStartup and StartupOnNetwork modes.
      Tested on Windows and Linux with:
      * target HW: ARM Stm32F4Discovery board with HW debugger STLink-v2
      * provider: OpenOCD v0.8.0 (tested on Windows and Linux)
      * provider: STLink-Util (tested on Linux only)
      * toolchain: ARM GCC v4.9.2
      * debugger: GDB v7.8.1 (with Python support)
      * QtCreator with QBS project
      Task-number: QTCREATORBUG-13686
      Change-Id: I59c775d91b0a4227d931188879850c536290e1ba
      Reviewed-by: default avatarLeena Miettinen <riitta-leena.miettinen@theqtcompany.com>
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
  6. 09 Oct, 2014 1 commit
  7. 20 Jun, 2014 1 commit
  8. 05 Jun, 2014 1 commit
  9. 08 Jan, 2014 1 commit
  10. 26 Sep, 2013 1 commit
  11. 20 Sep, 2013 3 commits
  12. 17 Sep, 2013 1 commit
  13. 23 Apr, 2013 1 commit
  14. 09 Apr, 2013 1 commit
  15. 29 Jan, 2013 1 commit
  16. 05 Oct, 2012 1 commit
  17. 02 Aug, 2012 1 commit
    • Christian Kandeler's avatar
      Device support: Introduce IDevice helper classes. · 753c62d7
      Christian Kandeler authored
      These are for configuration of process and ports gathering activities,
      This couples related functionality more tightly, while keeping
      the number of IDevice methods at a reasonable level.
      For ports gathering, the patch also adds the ability to configure
      both the command and the parsing function; the latter used to be
      hardcoded in the PortsGatherer class.
      Change-Id: I1b8940397a51efa7ddc05dd15cf861777d118c1a
      Reviewed-by: default avatarhjk <qthjk@ovi.com>
  18. 27 Jul, 2012 1 commit
  19. 19 Jul, 2012 1 commit
  20. 04 Jul, 2012 1 commit
  21. 24 Apr, 2012 1 commit
  22. 26 Jan, 2012 1 commit
  23. 09 Jan, 2012 1 commit
  24. 03 Nov, 2011 1 commit
  25. 06 May, 2011 1 commit
  26. 13 Apr, 2011 1 commit
  27. 12 Jan, 2011 2 commits
  28. 17 Dec, 2010 1 commit
  29. 05 Mar, 2010 1 commit
  30. 07 Jan, 2010 1 commit
    • Tobias Hunger's avatar
      Make method naming more consistent. · a6ad7737
      Tobias Hunger authored
        * Use id() for methods returning a string used to represent
          some type of object.
        * Use displayName() for strings that are meant to be user
        * Quieten some warnings while touching the files anyway.
        * Move Factories to their products in the plugins where that
          was not done before.
      Reviewed-by: dt
  31. 14 Aug, 2009 1 commit
  32. 29 Jul, 2009 1 commit
  33. 21 Jul, 2009 1 commit
  34. 17 Jul, 2009 1 commit
  35. 16 Jun, 2009 2 commits
    • con's avatar
      Cherry-pick: Update license headers and sales contact details. · 2919c210
      con authored
      Reviewed-by: Trust Me
    • Jason McDonald's avatar
      Update license headers and sales contact details. · 884b7af7
      Jason McDonald authored
      Reviewed-by: Trust Me
  36. 25 Feb, 2009 1 commit