Embedded programming often needs to extract operational stability and performance from limited resources, so it is frequently written in C. (In my case) especially when using a 32bit MCU, all code execution must flow almost identically to what I predict, so I rarely use complex higher-level concepts. The pointer of the function was about the highest concept. I hardly used classes either.
One of the most troublesome parts of embedded C projects is setting up the toolchain and managing make. Some projects have a small number of files, so processing is done by simply adding source code to the make file. To upload middleware such as FAT or USB on commercial MCUs, you need to install the MCU manufacturer's toolchain and vscode extension or eclipse plugin, so it was possible to create a working environment somehow. Since I used the tools without knowing much about them, make file management and toolchain setup felt a bit distant.
Recently, while coding personally with commercial MCUs, I have been constantly checking the toolchain settings and make management in the antigravity + gemini environment. Although the combination of CMake + Ninja + gcc + vscode extension does it automatically, it's reassuring to know how it works. I also feel like I might be able to figure out what to look for if there is a build error due to tool problems.
It's not my main job, but AI is very helpful in filling the gaps that I've been hesitant about.
Have a great weekend everyone~~~.
