chmanie.com - (very) random texts written by Chris Maniewski

It might not come as a surprise to you that I’m a heavy vim user. Whenever I write anything, I’d like for it to be inside of vim. This has been true for almost anything except note-taking. Why? Because I like to take a lot of notes on the go (in fact, I started the draft of this blog post on my phone) and sync them with my laptop. The number of iOS-apps that play well with vim based solutions and have pleasant use interface is quite small.

Let's say you have flashed your STM32 MCU but accidentally overwrote a GPIO configuration used for ST-Link communication (discovery boards are prone to this). You might get the error message when trying to flash:

I guess you found this post because you want to flash the superparasites firmware to Typhoon. As this is a custom firmware it's not as easy as building and flashing the official MI firmware images. Here's how it worked for me.

Coming from the JavaScript world, I'm used to the amazing debugging capabilities that browsers offer these days. I wanted to find a way to do debugging in a sensible way, covering the basics like setting breakpoints, skipping through them and doing variable inspection at runtime. Ideally I wanted to use vim for that as this is where I do all of my coding! I ended up finding an elegant solution (at least in my opinion) that I would like to share with you.

In this post I will try to document my journey of setting up a modern C(++) development environment in (neo)vim.