feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: Update information about developing for Bare Metal devices

Browse Source 
Change-Id: I6bfbf01c5204f3bcf53375d84cb4604f91c0c7a2
Reviewed-by: Denis Shienkov <denis.shienkov@gmail.com>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
Leena Miettinen
2020-08-20 16:06:53 +02:00
parent daea5358c8
commit de5858a5a8
1 changed files with 37 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
doc/qtcreator/src/baremetal/creator-baremetal-dev.qdoc
View File

@@ -30,26 +30,52 @@
\title Connecting Bare Metal Devices
You can connect bare metal devices to a development host to run and debug
You can configure build and run kits to use Bare Metal tool chains installed
on the development host to build applications for Bare Metal devices. You
can connect the devices to the development host to run and debug
applications on them from \QC using GDB or a hardware debugger. This enables
you to debug on small devices that are not supported by the generic remote
Linux device plugin. However, if the device does not have Qt libraries, you
need a fake Qt installation.
Linux device plugin.
\note If you use qmake to build the project and the device does not have
Qt libraries, you need a fake Qt installation.
The following tool chains are supported for building applications:
\list
\li GCC: Microchip Technology (AVR, AVR32, PIC16, PIC32),
NXP Semiconductors (ColdFire, M68K), Texas Instruments (MSP430),
National Semiconductor (CR16C), Renesas Electronics (M32R, M32C,
RL78, RX, SuperH, V850), Tensilica XTENSA (ESP8266, ESP32), RISC-V,
Arm
\li \l{https://www.iar.com/iar-embedded-workbench/}{IAR EW}:
Microchip Technology (AVR, AVR32), NXP Semiconductors
(ColdFire, M68K), Texas Instruments (MSP430),
National Semiconductor (CR16C), Renesas Electronics (78K,
M16/R8C, M32C, R32C, RH850, RL78, RX, SuperH, V850),
STMicroelectronics (STM8), 8051, RISC-V, Arm
\li \l{https://www.keil.com/product/}{Keil}: Arm, C51 (8051),
C251 (80251), C166 (C16x, XC16x)
\li \l{http://sdcc.sourceforge.net/}{SDCC}: STMicroelectronics (STM8),
8051
\endlist
The bare metal device type accepts custom GDB commands that you specify in
the device options. You can specify the commands to execute when connecting
using a particular debug server provider.
The following debug server providers are supported:
The following debug server providers are supported when using GDB:
\list
\li \l EBlink
\li \l J-Link
\li \l OpenOCD
\li \l ST-LINK
\li \l {uVision IDE}
\li \l ST-Link
\endlist
ST-Link and J-Link debug server providers can be used together with
the \l {uVision IDE}.
\section1 Enabling the Bare Metal Device Plugin
To enable the Bare Metal Device plugin:
@@ -200,7 +226,11 @@
\l{http://www.keil.com/support/man/docs/uv4/uv4_overview.htm}{uVision} is
an IDE for developing applications for embedded devices. Applications can
be debugged by using uVision Simulator or directly on hardware by using
St-Link.
St-Link and J-Link.
You can view the current state of peripheral registers in the
\uicontrol {Peripheral Registers} view in Debug mode. The view
is hidden by default.
\section3 uVision Simulator