Arduino for STM32

Bare Metal is the closest you can get to the processor,

you can always code assembly. or even hand-generate binary.

A potential problem about Bare Metal is how portable your code will be.

I usually code to cmsis. it has the most portability.

result

you will notice that your reading changes a little bit, partly because of the sequence of reading the timer can differ based on if you are trying to read the leading edge or the trailing edge.

one way to do that is to always read the timer first in the isr

analogwrite() produces a digital output whose duty cycle carries the analog information.

what you observed is expected.

most of the code you find will be developed against CMSIS and a set of vendor header files. so I would encourage you to at least try to align there.

I use Keil and an old version of CoIDE.

coding to the datasheet may sound challenging initially but it is not that hard. it allows you to migrate away from vendor libraries and develop a better understanding of the hardware -> the essence of "bare metal programming".

the cubemx code generator

I guess there are differing flavors of "bare metal".

It is not complicated at all - reading the datasheet will get you there. and if you don't care about code modularity / re-usability, you can simply dump all the files into one .ino file and call it a day. To me, that's the wrong way of doing things. as to your code below, I would suggest 1. use comm...

a good idea. but difficult to implement with the arduino ide. this approach would requirement multiple .c/.h files -> each dealing with a specific functionality / hardware modules. a typical project for me is 20+ files. unfortunately that's where the arduino ide fails. it has the ability to use mult...

yea. super-duper cheap e-bike version of the stm32f103.