I have used both ST-Link and Mikroe bootloader without any issue. The bootloader is a bit tricky due to double reset of the USB port after few second of timeout.
PS: The guys at Mikroe doesn’t expose BOOT0 pin free & accessible in any of their boards… damned!
In case your board is completely erased then you need a ST-link like programmer and connect SWC/SWD/GND (PA14-PA13) pin to the MINI-M4
Note: The mikroe bootloader sits in the topmost sector of the F4. So don’t expose the sector to tinyclr via DEPLOYMENT sector. I need to check the address, now I’m out of office sorry.
To your original question, you had the right idea. The third party boards we added ourselves were based off of the G30 or another device and only gotten to a point where they function. They were not optimized after the fact. As you discovered, clock rate is one of those areas and there’s certainly more that they can take advantage of. We’ll happily take a PR that further aligns a board’s Device.h with what it can fully support.
just copied/edited CLICKER source (as Mini M4) and did some modification on Device.h
only (since CLICKER is STM32F415) to meet requirements for MINI M4
compiled HEX uploaded with MikroElektronika bootloader