When adding SPI and Serial CDC and all the other variants still need to be Out of boards.txt because vassilis only had time to work on one variant, However, all boards except the F103 are currently commented One thing I failed to mention to the OP is that original HAL MX core did have the F401Īs a variant. I'm not personally that keen on either the Nucleo or Discovery range of The very same reason why the STM32L4 core officially only supportsĭragonfly, rather than DISCOVERY & Nucleo as well. No point in wasting time supportingĮverybody's favourite board just to get bogged down in wild goose chases. With the HAL MX core, it's always wise to limit the scope as much as Really comparable to Arduino or say Teensy. Theīoards are cheap enough so that they are disposable. I kind of like the Nucleo boards for quick and dirty prototyping. Reply to this email directly, view it on GitHub You are receiving this because you were mentioned. You could also take a look at the STM32L4 being developed Īs you may be able to modify that core to suit your needs
You may also like to look at Avik De's "Koduino" STM32 core, but that repoĭoes not seem to support the F401 MCU either (see May be able to use the variant files for one of those boards, as the basis I don't know the differences between the F401 and the F405 / F407, but you
Most people install, by cloning the git repo or downloading the zip intoĪs this is a community project and is not supported in any way by STM,īoards are only added to the repo when a variant for that board is On Thu, at 4:11 PM, Roger Clark boards manager package is maintained by and is the secondary distribution method at
My goal going forward was to add F446 support if that is of interest. Support USB (none of the Nucleo boards does). Really the kind of killer is that it does not I did use the Nucleo a lot for developement, and perhaps I'll add it oneĭay for official support. STM32L4 is a bit different than STM32F401.