stm32f103-example VS stlink

If you want to do bare-metal programming, you may want to take a look at my stm32f103-example project. It's for a different microcontroller than the one you're using, obviously, but converting it to work with an F4 part should be fairly straightforward. (I use the same framework for all of my STM32 projects.)

Use the CMSIS definitions of registers. They will save you a lot of time. If you're unhappy with having to repeat the names of peripherals, consider using something like the FIELD macros I wrote here.

The VECTOR macro expands to a sequence of assembler directives which uses .org. It'll end up creating gaps as needed.

And with a helper macro, you can rewrite the first bit as:

I see stlink clones on ebay for $7. The stlink software runs on linux : https://github.com/stlink-org/stlink. Or use pyocd.

This one?

I did do a little bit of digging since this post. I think my distro has this set of tools:https://github.com/stlink-org/stlink

I flashed mine using the flasher included into a Stm32f4 discovery board I had laying around. Used this toolset https://github.com/stlink-org/stlink to flash the firmware. Not sure if you can use UART to flash, if that's so, you might be able to use a raspberry pi or Arduino as an interface which is far way more accessible than the stlink flasher.

Usually the better tools (eg. Segger's J-link, st-link with st-util, OpenOCD) can emulate a GDB-server to which you can connect from a gdb or from the debug session at your IDE.

In order to get into stm32 development I bought a cheap stm32 blue pill clone (STM32F103C8T6) and a ST-LINK v2. I tried to get the info by using the st-info --probe command in the open source version of STlnk tools. I pluged in the stlinkv2 connecting the headers correctly to the dev board and the boot1 and boot0 was in 0 position, no additional connection was given.

Have a look here: https://github.com/stlink-org/stlink/issues/651 Maybe you have the same problem.