How can you program microcontrollers using an IDE?

When started learning Embedded Software, I think a lot about IDE but the later I realize that we don't really need the IDE. What we really need is: - Compiler - Editor (recommend notepad++ and visual studio code) - makefile project With this set, we are fully flexible to program for any microcontroller. And when less depend on the IDE, we will focus more on mechanism and optimization of the project.

One thing I would find helpfull is that usually IDE will ease the pain of installing toolchain and debugger as well as the makefile and project config. It would be very convinient but usually will come with a price, that is why most open source projects on github will not tie to any IDE. Still using an IDE is a good way to get started in coding in general.

IDE are often helpful to utilize some of the features like autocomplete code, add version control, hide the toolchains complexity, enable runtime step-by-step debugging, visual repesentation of software execution, which can be challenging at times with barebone gdb command. This speed up the development and help build confidence through easier navigation around code.

With generative AI to auto complete the code in specific context, adding test-vectors based on the generated code, unit tests based on corner cases, can be game changer for software development and time to market for software based products.

The most important feature is an integrated debugging, which allows step-by-step debugging of the embedded source code. The most important feature is that the IDE allows easy debugging.

Normally It should have following components with their corresponding proper configuration options: Editor, Compiler, Assembler, Linker, Debugger, Flash Programmer, Simulator etc.

From my perspective, the most practical IDE is Eclipse, which has been adopted by many vendors, such als ST Micro. But also chinese brands, like WCH have adopted eclipse to their MounRiverStudio.

I have used many such as Keil uVision, IAR, MPLAB from Microchip, Tasking, Eclipse, Metroworks Code Warrio, Net Beans, MS Visual Studio, Code::Blocks, etc. I have seen many are based on Eclipse.

Most IDEs let you view and change the registers of the microcontrollers. Basically you can change certain settings directly without programming. For example if you set registers dedicated for GPIO output, you can turn them on/off. And if there is an LED connected to the pin, it will glow as well. One good advice from my side would be to check with the data sheet what registers you need for certain peripherals (e.g. PWM) and then set them on in the IDE and see if the peripheral was turned on. Another interesting feature is that you can see your variables changing while the MCU is running. It is either in variables or expressions window.

When trying out a new chip manufacturer (or your new to embedded development in general) it often times makes sense to use the Vendor IDE to increase your chances of success. My first recommendation to anyone once they become comfortable with the general development flow however is to ditch the vendor IDE and switch to a suite of tools that give you a more consistent environment no matter the vendor, give full control of the build system, and give the developer an opportunity to truly understand what happens behind the curtain. The recommended stack is CMake for build orchestration and "project management", ARM GCC for your toolchain (assuming your developing on an ARM core), PyOCD for a GDB debug server, and VSCode for your editor.

One very easy to-get-going approach is to look at the sample code provided by the vendors. They tell you, how to best initialize a periferal, say a UART. Then you, as the developper does not have to set up everyhting yourself. This can be especially handy if tricky periferals, such as DMAs are to be used.