-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for small-sized STM32 variants? #68
Comments
Yes, this should be possible, even without the SDK (which, iirc, has licensing issues). I've got lots of STMF042 support over in altos (https://git.gag.com/?p=fw/altos;a=summary) which is where the samd21 code for snek started. You'd want parts with at least 32kB of flash and 4kB or more of SRAM. 64kB of flash and 8kB of flash is an awesome size -- you can have all of the snek code and have plenty of space for applications. You might want an off-board SPI flash to store snek source in, but if you've got spare flash in the part you can place it there as well. |
Thanks a lot for the feedback. |
Ok, digikey appears to have TSSOP20-packages with 32kB flash - and even in stock. |
I'd encourage you to choose the larger chip, even though it's in a LQFP -- 64kB of flash will be enough to hold most of snek (you might have to skip the math library), and probably leave space in flash to store snek programs themselves, without an external SPI flash part. 32kB is "enough" for the atmega328, but that's with some pretty serious compromises, and on an architecture with a denser ISA. https://www.digikey.com/en/products/detail/stmicroelectronics/STM32G030K8T6/10326689 |
ooo, they've got this one with 64kB in a tssop-20 package: https://www.digikey.com/en/products/detail/stmicroelectronics/STM32G031F8P6/10326693 |
Is there any chance for support of variants of the STM32 family which are too small to run MicroPython, such as the TSSOP20-packaged ones, e.g. STM32F030F4P6*?
The SDK/HAL seems fairly well understood and stable and snek would be a great choice to run these SoCs.
I would have asked on the mailing list, however there seems to be some issue (#67)
The text was updated successfully, but these errors were encountered: