punkkerop.blogg.se - Atollic truestudio debug tool

#Atollic truestudio debug tool how to
#Atollic truestudio debug tool code

When everything is OK, after a short time, the debugging perspective should open.

Select the correct Debug probe (ST-Link when using a Nucleo board) with SWD Interface.įrom the Atollic main window, start the debugger by clicking the Debug button. Then, review settings in the Debugger tab. Both C/C++ Application and Project fields should be populated with project binary file (.elf) and project name: Review the new configuration settings, starting with the Main tab. In the Debug Configurations dialog, select Embedded C/C++ Application category and click the New Launch Configutation button. With the project beeing selected, click the Configure Debug button.

A Debug folder that contains all the files generated during the build process (including the blink.elf binary file).

Note that project structure has been populated with new items: With the project beeing selected, click the Build button and watch the Console window: When you're done, click OK at the bottom of the Properties window. It should be in your workspace/blink folder: Then, use the Browse button to find the linkerscript file you've saved earlier. Select the C Linker → General subcategory: If not already selected, select the category (in the left treeview) C/C++ Build → Settings.

For the need of this tutorial, we will provide our own linkerscript file, therefore select Cancel to avoid the generation of an automatic linkerscript.Ĭlick the Build Settings button again. Next, Atollic prompts you about the linkerscript that should be generated based on the previous target selection. Here, select STM32F0 → MCU → STM32F072RB as the target: Then select the device you want to build the project for. Void (* const table_interrupt_vector)(void) =ĭefault_handler, // 3 - Hardfault handlerĪ dialog window appears telling you that no target been set for this project.Ĭlick OK. g.Double-click the file to open it in the editor and copy/paste the following code: /* > Tool Settings -> C Linker -> Libraries)Īdd the libs without "lib" and file extension (e. add the pre-compiled PlatformPackage libs (libewrte and ewgfx-eval) > Tool Settings -> C Compiler -> Drectories / Symbols) (Project -> Properties, Open C/C++Build Folder and select Settings add the needed include paths and defines according to the delivered > Resource Configurations -> Exclude from build) right click on RGB888 below PlatformPackage in Project Explorer Exclude the unneeded examples and color formats (/PlatformPackage) Or add the Embedded Wizard Build Enviroment as Linked Folder similar (either copy the Embedded Wizard Build Enviroment to your workspace add the complete Embedded Wizard Build Enviroment to the project > Exclude from build -> mark one or more configurations) Linked Folder in Project Explorer -> Resource Configurations right click one or more Folders or single files within the Exclude all the unneeded stuff from from the build * After Pressing Finish, the Linked Folder will be added to the project * Press the 'Advanced>' Button and select 'Link to alternative location' * Right click to the root object in Project Explorer -> New. add the STM32Cube_FW_Fx folder as linked folder to the project

#Atollic truestudio debug tool code

In case of Atollic TrueSTUDIO it is a good starting point to build an Embedded C Project for a specific STM32 EVAL or DISCOVERY board as described in the Quick Start Guide of Atollic TrueSTUDIO.īased on this simple application the Embedded Wizard code and libs can be added. Nevertheless, Embedded Wizard generates ANSI C code, that can be integrated to each STM32 IDE. Providing some simple Embedded Wizard projects newcomers have the first applications up and running on the STM32 target after a few minutes. We decided to do this with the GNU make approach, since there are only few dependencies (ARM tool chain, STM32Cube package and STM Link) and no specific issues concerning the different IDEs available for the STM32 devices.

#Atollic truestudio debug tool how to

It is our intention to allow newcomers a very quick end easy way how to build Embedded Wizard projects and how to get it run on a target platform.