![tools path atollic truestudio tools path atollic truestudio](https://i.imgur.com/p1RJqHW.png)
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.
![tools path atollic truestudio tools path atollic truestudio](https://i.imgur.com/z1nawoz.png)
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.
![tools path atollic truestudio tools path atollic truestudio](https://www.feaser.com/en/blog/wp-content/uploads/2020/09/import_projects.png)
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. Double-click the file to open it in the editor and copy/paste the following code: /*