Arduino for STM32

stevestrong wrote: ↑Sun Mar 22, 2020 9:09 am That is true, just that it requires non-standard solutions. The mentioned bootloaders do not require any additional hack, they work out of the box with Arduino.

+1 And HID requires no driver installation which is even nicer - although the supplied code is 407 specific.

Remove the underscores from the pin names.

And the HID (ST-LINK) The HID bootloader is a software bootloader, it does NOT require ST-LINK (although you may use ST-LINK to actually flash the bootloader to the device). When activated it allows the device to be flashed via USB Serial (CDC). This means you must have USB Serial enabled in the ID...

that DTR magic sequence is a feature of libmaple (roger's) core. only if you make a libmaple sketch compile do you get that DTR magic sequence. This should also work with STM's core, I know as I helped port the code to detect this from STM32GENERIC -> https://github.com/danieleff/STM32GENERIC/blob/...

Ok thank you for your time for looking into this. I understand that it takes time to put a new byte to the buffer but the thing that bothers me is that the time changes exactly as the baudrate does. It is always 1bit long and I don't understand how the CPU can put the new byte in to the buffer fast...

And you have USART support set to enabled 'generic serial'

And USB Support set to "CDC generic 'serial' supercede USART"

And you've loaded a sketch with serialusb enabled after reflashing with each bootloader? Roger's bootloader will stay in DFU mode if there's not sketch resident.

My (perhaps errant) memory is telling me that I had read @arpruss was doing this abstraction in order that it may make porting to STM's core easier, am I making that up?

I'd be happy to help test, I've got ~15 or so variants here F1, F3, F4

That link still doesn't explain how your fork of roger's core differs from his.

@Bakisha he was asking about the differences between Roger's core and Stevestrongs fork of it which is F4 focused.