libopencm3-examples VS stm32-cmake

What is the relationship between the data packets? I went through a mouse emulation example and the first field seems to be the "mouse" reporting. But, following that example convention, do the buttons come first, needing "my amount" of buttons in bits (in my case, 35 buttons is 6 bytes of data), then the axes with 12 bytes taken up (2 bytes for each value of 6 axes)?

I have had success creating a PWM using a different general purpose timer on a different GPIO. So I am pretty sure I got the basic configuration correct. What throws me off a little is the fact, that Channel 2N (CH2N) seems to share registers with Channel 2 (CH2). They seem to be complementary somehow. So I stayed close to [this example]([https://github.com/libopencm3/libopencm3-examples/blob/master/examples/stm32/f1/stm32-h103/pwm_6step/pwm_6step.c) for the STM32F1 and configured all necessary settings for both channels CH2N and CH2.

Using libopencm3-examples lcd-serial as the base so that I could print the results to the onboard screen. Quickest way I could think to get the results since I don't know how to get to the serial console off the top of my head.

STM32, libopencm: https://github.com/libopencm3/libopencm3-examples

eg. see examples for stm32f4 discovery board, as an example, https://github.com/libopencm3/libopencm3-examples/tree/master/examples/stm32/f4/stm32f4-discovery

Check out stm32-cmake

My suggestion would be to use CMake. There is a great set of CMake tools for STM32 called stm32-cmake. You can use the STMCubeF1 package from GitHub, FreeRTOS from source (or from Cube which is also bundled with their GitHub source).

If your projects use different compilers or you need to compile with different architecture flags then CMake is a good option to manage this. This was an example I used when I first started with CMake and microcontroller developement. https://github.com/ObKo/stm32-cmake

I highly suggest https://github.com/ObKo/stm32-cmake Using cmake allows to build using cli commands. If you then onboard people later on, they still can work with their IDE thanks to cmake.

stm32 is really nice for getting into it. id steer clear of their IDE and probably use their code generator as a reference. Learn CMake and go with this https://github.com/ObKo/stm32-cmake

stm32-cmake, for when you don't want to touch STs IDE at all. https://github.com/ObKo/stm32-cmake

Have you seen stm32-cmake?

If you master a bit of cmake then https://github.com/ObKo/stm32-cmake will make you start very fast in vscode.