Re: [STM32F103] - Porting MicroPython to the "BluePill" board
Posted: Wed Nov 29, 2017 5:34 pm
Hello everyone, I took a look at continuing the effort of porting micropython. I mostly continued from the work here https://github.com/mcauser/BLUE_PILL_F103C8 done by @mcauser.
I didn't notice the other repositories so I also got the stm32cube fw into the right folder (didn't change it).
There are many function that are not available on the STM32F103, so I had a two step approach:
- For functions that I could patch, I did
- For files with too many errors, I removed them from the build.
I also had to remove startup_stm32.o from Makefile in order to get past linking stage (of course, it produces an empty .dfu file but it's useful for porting).
I pushed everything on my fork on https://github.com/slurdge/micropython/commits/master
I have several questions: it seems that a lot a functionality used by the stm32 port is not actually available, what is the best way to disable them for this port? Do you think we can get under 128K?
Am I duplicating effort here?
I didn't notice the other repositories so I also got the stm32cube fw into the right folder (didn't change it).
There are many function that are not available on the STM32F103, so I had a two step approach:
- For functions that I could patch, I did
- For files with too many errors, I removed them from the build.
I also had to remove startup_stm32.o from Makefile in order to get past linking stage (of course, it produces an empty .dfu file but it's useful for porting).
I pushed everything on my fork on https://github.com/slurdge/micropython/commits/master
I have several questions: it seems that a lot a functionality used by the stm32 port is not actually available, what is the best way to disable them for this port? Do you think we can get under 128K?
Am I duplicating effort here?