Arduino for STM32

there is a traditional finger dance for stm32f4xx pill boards.
- press boot0 and reset
- release reset but hold boot0
- release boot0 1 sec later
that is the correct way to get into the *real* USB DFU mode, the on-chip USB DFU mode that is. it should flash with the STM32cube programmer and dfu-util ...

oops i'd need to catch up, i stashed it in the box.
g0 is 'slightly improved', e.g. the adc etc.
I'd likely try HSI, as I'd use one of those SOIC-20 'adaptor' boards and my breadboard.

with STM core to use the USB (virtual) com port, you need to compile your sketch with USB (CDC) Serial selected.
then you can use a sketch as like

void setup() {
Serial.begin();
while(!Serial);
}

void loop() {
println("hello world");
delay(1000);
}

virtual com port is Window's notion of a ...

you need to ensure that you have selected USB (CDC) Serial in your sketch as your default Serial device.
then your Serial would be USB Serial.
and you can test that with things like

I've not visited this in a while, I've made a fork of it sometime back.
https://github.com/ag88/Adafruit_ILI9341_SPI_stm32duino
https://www.stm32duino.com/viewtopic.php?t=896
https://www.stm32duino.com/viewtopic.php?t=895

note that I've not tested it on a stm32f103c8, and that it has been a while ...

stm32g030 is quite a different and new chip
https://www.stm32duino.com/viewtopic.php?t=1848

among the things that is "unusual" (different), PC15 pin is shared between OSC32_EN (default) and OSC_EN
https://www.stm32duino.com/viewtopic.php?t=1848&start=10
so I'd guess either a 32k crystal can be used ...

try doing CMake, I think it is a better 'platform' to build the firmware. A trouble, is due to the huge portfolio of MCU series, STM32 F1, F3, F4, F7, H7, G0, C0, WB, MP1 etc, doing things with #includes and #ifdef is sooner than later going to tie up a huge amount of dependencies.

CMake allows the ...

openocd (at least on linux) is quite tricky, it runs as a server and has its own console.
Hence, I'd normally start openocd separately in its own terminal session, normally driven by a script.

Then from the IDE, i start gdb or more correctly arm-none-eabi-gdb.
The key is arm-none-eabi-gdb
1 - needs ...

I've not yet tried this out, but I'm thinking about it and just some 2 cents suggestions.

I'd think it is probably adequate for the IDE to start arm-none-eabi-gdb
so that it probably does a
(gdb) target remote :3333
gdb has to locate the local elf file with all the symbols and source.

this is so ...

To a good extent, yup, we can probably 'daisy chain' 2 stm32g030f6p6, so that one handles 'extra' IO, but it seemed like a 'waste' of transistors :lol:
i'm thinking there could be other designs as well, e.g. one could simply be a 'display driver' say driving an LCD, possibly including decoding a ...