Difference between revisions of "Atollic TrueSTUDIO"
(8 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | __TOC__ |
||
− | Eclipse is a universal customizable IDE, which is also the base for many common commercial IDEs. |
||
− | In order to work with Eclipse and debug with J-Link, you also need to install a toolchain which includes compiler, assembler, linker + GDB (GNU Debugger) for debugging (e.g. [https://launchpad.net/gcc-arm-embedded/ GNU Tools for ARM]). |
||
− | Moreover, in order to allow hardware debugging on embedded systems via GDB + GDB Server, there is also an Eclipse plugin needed, which enables hardware debugging via GDB (e.g. the CDT plugin). |
||
− | After setting up Eclipse + Plugin, Eclipse will use GDB as debugger where GDB communicates via the GDB protocol with J-Link GDB Server, allowing to debug the target hardware which is connected to a J-Link. |
||
+ | '''Atollic TrueSTUDIO''' is a commercial IDE based on Eclipse that comes with J-Link and J-Trace support. |
||
− | The tutorials in this article are based on Eclipse Neon.3 setup with the [http://gnuarmeclipse.github.io/ GNU ARM Eclipse] environment by following the [http://gnuarmeclipse.github.io/install/ official install instructions]. |
||
+ | In order to use J-Link with Atollic TrueSTUDIO, it is usually not necessary to separately install the J-Link software and documentation package since TrueSTUDIO already comes with a J-Link GDB Server that is automatically started when starting the debug session. In the following, a short explanation on how to create a simple project for an eval board with TrueSTUDIO is given: |
||
− | The GNU ARM Eclipse project is a collection of plug-ins for Eclipse CDT and ARM toolchains including extensions for easy embedded development in Eclipse. |
||
− | It is recommended to use this plug-in when working with a standard Eclipse installation. |
||
− | |||
− | |||
− | '''Note:''' J-Link GDB Server is part of the [https://www.segger.com/downloads/jlink/ J-Link Software and Documentation Pack] and can be used free of charge. |
||
__TOC__ |
__TOC__ |
||
+ | = Creating a simple Project= |
||
+ | == Used components == |
||
+ | {| class="wikitable" |
||
+ | |- |
||
+ | ! IDE !! Emulator !! J-Link SW Version !! Evalboard |
||
+ | |- |
||
+ | | TrueSTUDIO for ARM V2.3.0 || J-LInk || V4.40c || STM32F103ZE-EVAL (STM32F103ZE) |
||
+ | |} |
||
+ | == Setup Instructions == |
||
+ | * Start TrueSTUDIO and click '''File | New | C Project ...''' from the main menu |
||
+ | * Enter a project name |
||
+ | *Select '''Embedded C Project''' |
||
+ | *Click '''Next''' |
||
+ | |||
− | == Getting started == |
||
+ | [[File: TrueSTUDIO_Tutorial_1.png]] |
||
− | |||
− | |||
− | === Creating a J-Link Debug Configuration === |
||
− | * Open '''Run''' -> '''Debug Configurations...''' |
||
− | * Double click '''GDB SEGGER J-Link Debugging''' |
||
− | * [[File:Eclipse_CreateJLinkDebugConf.png]] |
||
− | * Eclipse will create a New Debug Configuration and set setting to defaults based on the workspace and project |
||
− | * [[File:Eclipse_JLinkDebugConfDefault.png]] |
||
− | |||
− | |||
− | |||
− | === Configuring the target interface type === |
||
− | |||
− | * Open '''Run''' -> '''Debug Configurations...''' |
||
− | * On the left side, select the used Debug configuration in the group '''GDB SEGGER J-Link Debugging''' |
||
− | * Switch to the tab '''Debugger''' |
||
− | * The target interface can be selected in the area marked below |
||
− | * [[File:Eclipse_JLinkDebugConf_Debugger_TargetInterface.png]] |
||
− | |||
− | |||
− | |||
− | === Configuring the target interface speed === |
||
− | |||
− | # Initial interface speed before/during connect |
||
− | #:* Open '''Run''' -> '''Debug Configurations...''' |
||
− | #:* On the left side, select the used Debug configuration in the group '''GDB SEGGER J-Link Debugging''' |
||
− | #:* Switch to the tab '''Debugger''' |
||
− | #:* The interface speed before connect can be specified in the field '''Initial speed''' marked below |
||
− | #:* [[File:Eclipse_JLinkDebugConf_Debugger_TargetInterfaceSpeed_Initial.png]] |
||
− | # Interface speed after connect to target before/during reset & halt |
||
− | #:* Open '''Run''' -> '''Debug Configurations...''' |
||
− | #:* On the left side, select the used Debug configuration in the group '''GDB SEGGER J-Link Debugging''' |
||
− | #:* Switch to the tab '''Startup''' |
||
− | #:* The interface speed after connect to target before/during reset & halt can be specified in the field '''Low speed''' marked below |
||
− | #:* [[File:Eclipse_JLinkDebugConf_Startup_TargetInterfaceSpeed_ResetHalt.png]] |
||
− | # Interface speed after initialization |
||
− | #:* Open '''Run''' -> '''Debug Configurations...''' |
||
− | #:* On the left side, select the used Debug configuration in the group '''GDB SEGGER J-Link Debugging''' |
||
− | #:* Switch to the tab '''Startup''' |
||
− | #:* The initial speed can be specified in the area '''JTAG/SWD Speed''' marked below |
||
− | #:* [[File:Eclipse_JLinkDebugConf_Startup_TargetInterfaceSpeed.png]] |
||
− | |||
− | |||
− | |||
− | === Specifying the target device === |
||
− | |||
− | * Open '''Run''' -> '''Debug Configurations...''' |
||
− | * On the left side, select the used Debug configuration in the group '''GDB SEGGER J-Link Debugging''' |
||
− | * Switch to the tab '''Debugger''' |
||
− | * The target device can be specified in the field '''Device name:''' marked below |
||
− | * [[File:Eclipse_JLinkDebugConf_Debugger_TargetDevice.png]] |
||
− | |||
− | |||
− | |||
− | === Specifying J-Link GDB Server commandline options === |
||
− | |||
− | For a list of available commandline options, please refer to UM08001. |
||
− | Commandline options for GDB Server can used for various J-Link features, e.g. |
||
− | * specifying a J-Link Settings file |
||
− | * specifying a J-Link script file |
||
− | * specifying a J-Link Command String |
||
+ | * Select the eval board the project shall be created for and what configuration (debugging in Flash or RAM) is desired |
||
− | Commandline options can be specified by editing the field '''Other options''': |
||
+ | * Click '''Next''' |
||
− | * Open '''Run''' -> '''Debug Configurations...''' |
||
− | * On the left side, select the used Debug configuration in the group '''GDB SEGGER J-Link Debugging''' |
||
− | * Switch to the tab '''Debugger''' |
||
− | * Commandline options can be specified by editing the field '''Other options''' marked below |
||
− | * [[File:Eclipse_JLinkDebugConf_Debugger_GDBServerCLO.png]] |
||
+ | [[File: TrueSTUDIO_Tutorial_2.png]] |
||
+ | * Select J-Link from the list of supported emulators |
||
− | === J-Link Settings File === |
||
+ | * Click '''Next''' |
||
+ | [[File: TrueSTUDIO_Tutorial_3.png]] |
||
− | Please refer to [[Eclipse#Specifying J-Link GDB Server commandline options | Specifying J-Link GDB Server commandline options]] |
||
+ | * Select which configurations shall be created (Debug configuration / Release configuration) |
||
+ | * Click '''Finish''' to create the project |
||
+ | [[File: TrueSTUDIO_Tutorial_4.png]] |
||
− | === Using J-Link Command Strings === |
||
+ | * Click the '''Build''' button from the toolbar |
||
− | Please refer to [[Eclipse#Specifying J-Link GDB Server commandline options | Specifying J-Link GDB Server commandline options]]<br> |
||
+ | * In order to start a debug session, click '''Debug'''. A debug configuration with default settings, based on the information given when creating the project, will be automatically created by TrueSTUDIO (if it is necessary to configure custom settings click '''Run | Debug Configurations...''' from the main menu). |
||
− | Please note that J-Link Command Strings can also be executed from J-Link script files. |
||
+ | [[File: TrueSTUDIO_Tutorial_5.png]] |
||
+ | == Ready to Go == |
||
+ | You can start debugging and use J-Link with Atollic TrueSTUDIO for ARM. |
||
− | === Using J-Link script files === |
||
+ | [[File: TrueSTUDIO_Tutorial_6.png]] |
||
− | Please refer to [[Eclipse#Specifying J-Link GDB Server commandline options | Specifying J-Link GDB Server commandline options]] |
Latest revision as of 13:42, 8 October 2020
Atollic TrueSTUDIO is a commercial IDE based on Eclipse that comes with J-Link and J-Trace support.
In order to use J-Link with Atollic TrueSTUDIO, it is usually not necessary to separately install the J-Link software and documentation package since TrueSTUDIO already comes with a J-Link GDB Server that is automatically started when starting the debug session. In the following, a short explanation on how to create a simple project for an eval board with TrueSTUDIO is given:
Creating a simple Project
Used components
IDE | Emulator | J-Link SW Version | Evalboard |
---|---|---|---|
TrueSTUDIO for ARM V2.3.0 | J-LInk | V4.40c | STM32F103ZE-EVAL (STM32F103ZE) |
Setup Instructions
- Start TrueSTUDIO and click File | New | C Project ... from the main menu
- Enter a project name
- Select Embedded C Project
- Click Next
- Select the eval board the project shall be created for and what configuration (debugging in Flash or RAM) is desired
- Click Next
- Select J-Link from the list of supported emulators
- Click Next
- Select which configurations shall be created (Debug configuration / Release configuration)
- Click Finish to create the project
- Click the Build button from the toolbar
- In order to start a debug session, click Debug. A debug configuration with default settings, based on the information given when creating the project, will be automatically created by TrueSTUDIO (if it is necessary to configure custom settings click Run | Debug Configurations... from the main menu).
Ready to Go
You can start debugging and use J-Link with Atollic TrueSTUDIO for ARM.