Arduino for STM32

ok hopefully you've got the *special* stm32f103c8 where they give you 128k flash for 64k, that used to be *real*, but that literally even at 90nm, giving extra 64k flash as a 'gift' is quite modest probably an mm2 of sand
it seemed sram is the thing that consume more silicon foot print

it is necessary to review the ref manual for your particular soc e.g. STM32F4xx
for F405/F417/F437/F439 it is apparently rm0009
https://www.st.com/resource/en/reference_manual/rm0090-stm32f405415-stm32f407417-stm32f427437-and-stm32f429439-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
(for ...

you can probably make one from scratch, or to adapt the library, the key is to review
RM0009 to see how it works
https://www.st.com/resource/en/reference_manual/rm0090-stm32f405415-stm32f407417-stm32f427437-and-stm32f429439-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

it isn't too difficult ...

I'd need to catch up on this. on a different note, i've got a 'brainy' idea about 'io extender'
chips like PCA9535 cost a 'little fortune' on AliX
https://www.nxp.com/products/interfaces/ic-spi-i3c-interface-devices/general-purpose-i-o-gpio/16-bit-ic-bus-and-smbus-low-power-i-o-port-with-interrupt ...

Serial.print() and write a little program to save it from the host/pc side

e.g.
https://github.com/ecm-bitflipper/Arduino_ZModem

I'm just thinking aloud.
I think we can maintain a separate tree (in a separate repository, quite like a 'library') for c++ templates based common devices e.g. spi, uart, i2c, adc etc, they wouldn't fit right in in the Arduino API, but can be deemed an alternative API. This would allow us to ...

you can skip that while(!Serial); it waits for the host to connect.

these days practically 'everything' is 'virtual' com ports, in Windows that is. USB isn't RS232 and it doesn't have any of the signals that is used in RS232.
at usb full speeds it is 12 Mbps (but this did not account for all the ...

if you use USB (CDC) serial, that one consumes quite a bit of flash. then ADC etc. For what is worth, the codes isn't catering to a simple 'Uno' type scenario, but practically across the swatch of stm32 series.
get an mcu with more flash and ram e.g. stm32f401/f411 ce or better f401re,ve/f411re,ve ...

for f4xx I won't bother with a custom bootloader, it takes flash memory and it takes the traditional 0x8000000 start of flash address.
and much less fuss bothering with custom bootloaders e.g. that your sketch is compiled for an incompatible address etc.
you would more than likely need a custom ...

Actually, I hardly calibrate the adc maybe as I'm lazy to do it and hence, don't know about it.
the ref manual rm0008 is a place to start looking up about it, the chapter about ADC etc.

those register patches simply configure the registers to enable VREFINT and the temperature sensor.
and setting ...