![]() ![]() In the Common tab, make sure you select Shared file to force the settings to be saved in the project rather than the Workspace. The Startup tab should already be all set as well. In the Debugger tab, enter " -f board\sparkcore.cfg" to pass in the configuration file we created to the OpenOCD. The Main tab should already be good to go. Right-click on GDB OpenOCD Debugging and select New. Click OK.Ĭlick on the little green bug icon in the Eclipse toolbar and select Debug Configurations. Go to Window > Preferences > Run/Debug > String Substitution and make sure openocd_path refers to the bin folder of the OpenOCD installation. ![]() The next step would be to setup a debug configuration and begin debugging! The build should succeed and you should get a Debug folder containing a. Right click on your project and choose Build Project. Select the configurations you want to include.Ĭheck the path of the Toolchain you installed in section 2.2. Select STM32F10x C/C++ Project and Cross ARM GCC and give your project a name.įill in the Target processor settings according to the picture below.Ĭhange the directory structure if you so wish. Now since the Spark Core firmware is currently not compilable on Windows due to makefile issues, for the sake of demonstration, we will create a new project from scratch. # use hardware reset, connect under resetģ Configuration 3.1 Creating a new project ![]() This is a SPARK-CORE board with a single STM32F103MD chip. Navigate to C:\Program Files\GNU ARM Eclipse\OpenOCD\scripts\board, create a new file called sparkcore.cfg and populate it with the following lines:.Run the setup and install it preferably in the default location.Download the The GNU ARM Eclipse OpenOCD which is basically a compiled and hassle-free binary of the latest OpenOCD source from here.In my opinion, this is an incredible and priceless debugging tool. printf, right inside your Eclipse terminal. It supports many different adapters including ST-LINK/v2 and has recently added support for SWO tracing which allows you to see the output of STDOUT e.g. The Open On-Chip Debugger ( OpenOCD) aims to provide debugging, in-system programming and boundary-scan testing for embedded target devices. Select all the items and continue with the installation.Ģ.5 Installing The GNU ARM Eclipse OpenOCD Type in " GNU ARM Eclipse Plug-ins" as the Name and " " as the Location. ![]() Go to Help > Install New Software and click Add. This set of Eclipse extensions are an easy, fast, great and portable way of creating, building, debugging and managing your project. Go to Help > Install New Software and install Eclipse Git Team Provider. In order to be able to work with Git repositories, you might wanna consider installing Eclipse Git Team Provider. In order to be able to compile your projects and debug them, you need to download and install the latest version of GNU Tools for ARM Embedded Processors from here. Once you did that, you should be able to see your STM32 STLink device in Device Manager.Ģ.2 Installing GNU Tools for ARM Embedded Processors You might also want to install ST-Link Utility which not being necessary is a useful program. 2.1 Installing ST-LINK/v2 Device Driversĭownload and install the appropriate driver matching your Windows version from here. I assume you already have downloaded and installed Eclipse IDE for C/C++ Developers otherwise download it from here and unpack it to a local folder. ST-LINK/v2 ( if you're going to buy one, you might wanna check ebay too ).My aim is to make this tutorial usable for both beginners and advanced users so I'll start with the basics. Since I spent quite some time figuring out what the best way is to debug the Spark-Core using ST-Link/v2 and how to do it, I thought I'd share my findings hoping it would save someone else some time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |