Hi@ladyada
Nice to see you here 😉
Thanks for this variant. I will review it carefully.

Hi@ladyada
if I'm not wrong this is an STM32F405RG ?

yes thats' right
good news - last night i tested all featherwings with the feather. only a few oddities:

• usually when using USB serial, the hardware serial port is called Serial1, but instead stm32duino names them after the USART so the hardware serial is Serial3 - not a big deal but like i said, unusual
• RFM69/RFM9X library wouldn't work, not sure why
• variant doesnt allow creation of multiple SPI / I2C ports like modern arduino does. you can do it by hand, so it isn't blocking - but would be nice if it were possible.
• STM32F4 often have a USB dfu bootloader built in, which is great, but you have to kick into the bootloader each time. it would really help workflow a lot if it was automatic. for example, opening USBSerial port at 1200 baud would trigger a jump to the USB DFU bootloader.

The third item would be by far the most useful for workflow support because right now workflow is optimized for boards which have built in debugger (expensive) or STLink dongle (unecessary!)

• usually when using USB serial, the hardware serial port is called Serial1, but instead stm32duino names them after the USART so the hardware serial is Serial3 - not a big deal but like i said, unusual

In fact choice has been made to nameSerialx wherex is the same thanU(S)ARTx.

• RFM69/RFM9X library wouldn't work, not sure why
  I've never tested. So probably required some investigations.

• variant doesnt allow creation of multiple SPI / I2C ports like modern arduino does. you can do it by hand, so it isn't blocking - but would be nice if it were possible.

As far as I know Arduino create only one instance per type (oneWire and oneSPI)? They pre-instantiate all possible one now? Any example are welcome and an issue could be open to track this.

• STM32F4 often have a USB dfu bootloader built in, which is great, but you have to kick into the bootloader each time. it would really help workflow a lot if it was automatic. for example, opening USBSerial port at 1200 baud would trigger a jump to the USB DFU bootloader.

Right, I've plan to do it as the mechanism is already there (used for HID and Maple bootloader). This only require to write the jump code.

The third item would be by far the most useful for workflow support because right now workflow is optimized for boards which have built in debugger (expensive) or STLink dongle (unecessary!)

I don't well understand this point about workflow support?

Hiya here's an examples of how to create multiple I2C/SPI peripherals.

https://github.com/adafruit/ArduinoCore-samd/blob/master/variants/grand_central_m4/variant.h#L177

they are auto-generated here:

https://github.com/adafruit/ArduinoCore-samd/blob/master/libraries/SPI/SPI.cpp#L469

Thanks, will check that.
Why did you closed this PR?

oh i see this is the same one. sorry about that! late nite hacking :D

ok for workflow question - the great thing about the arduino is that before it, you had slow workflow - to program a new chip you had to manually launch the bootloader. that means pressing a button or something the dev board. with the stm32f405 feather now, because we don't have a built in stlink or openocd chip, you have to manually enter the bootloader my holding BOOT0 high and then pressing reset. If this was done automatically when you click UPLOAD it would allow for very fast iteration. that's the only thing missing :)

Ok understood.
As said this is planned 😉

ok thanx - how can i help get it implemented

Firstly, could you open an issue for:

• [SPI|WIRE]_INTERFACES_COUNT
• Automatic restart in DFU Bootloader mode

This will allow to track them.

ok done!

ok thanx - how can i help get it implemented

Hi@ladyada,
You can try the automatic restart, see#710 .
I did not had time to update script under Windows anyway you can test it manually or update the windows scripts based on what I've made for the linux one.
Let me k ow if you meet any issue.
Thanks

ok great, i use windows 10 :)

could you merge this PR, and rebase the#710 branch - so i only have to follow one branch :)

done

💙 thank u 💙

Welcome and welcome as contributor 😉

hiya i'm about to release the hardware for this, do you know if there's an eta for when the BSP is going to get the next minor update? i will have folksgit clone the BSP for now

Well I don't think before december. I try to make a release every 3 months.

oki