That said, if doing this sort of configuration is new to you, then I highly recommend that you stick to my method and attempt it your way once you are happy with the process. So in this post I will try my best to leave a comment where possible to highlight what was as a personal preference so that you have the choice to do it the way you want to do it. if I have to, I will make sure that I make it clear why and comment on what you will need to look out for if you are using a different vendor MCU.Īs final note, I wanted to say that it always bothers me when you find a tutorial online that goes through the step of doing something and the person doesn’t bother to briefly mention that a particular steps was done in such way because of personal preference. I’m going to be using the NUCLEO-F030R8 Board by STMicroelectronics and I’m going to be doing the whole configuration on a linux ( ubuntu) OS.īecause ARM is trying so hard to make it easier for us developers to migrate project code between vendor microcontrollers, If I can help it, I will be avoiding the use of vendor specific library and tools. My objective for this post is to document the process of how I go about configuring a development environment for the ARM cores. However, if you know how OpenOCD device profiles are created and used, then you can simply roll your own. Look at it this way, if you are using the latest micro-controller that is only a few weeks old, chances are that the OpenOCD that you are using for programming and debugging wont have support for that micro. However, knowing how to configure your own development environment will help in situation where you are developing at the edge of technology, as I quite often do. I feel that I should first start by pointing out that you can download various pieces of software that makes this process easier. To be honest, the post acts more of a logbook for my work and for that reason i will only maintain this post as when new technology changes my workflow. For a while now, I’ve been meaning to document my development configuration for a clean ARM CMSIS development environment.
0 Comments
Leave a Reply. |