-
Notifications
You must be signed in to change notification settings - Fork 133
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
Bluepill template built with arm-gcc does not fit 128K Flash #139
Comments
maybe you can add the -Os option for size optimization. |
I believe it has fitted, but not sure because my STM32 is 64K:
|
I'm trying to use the STM32CUBEMX auto-generated makefile to fix that. For more details: https://github.com/Chandler-Kluser/pikascript_gcc_bluepill/pull/1 |
Compiled with the merge request you made, I have got:
It would be great if there was ANYTHING that could be not used to make it fit in 64kB, but it worked in my PC! I will also improve the Makefile you did, thanks a lot! |
I remember a week ago if we commented the line: import STM32F103 in main.py and recompile with pikascript compiler and then build the entire image again we could make the image fit in 64kB, but I am not finding that anymore in this new template. |
the STM32F103 is imported by mchine.pyi now. |
I did comment mchine.pyi file, recompiled that with pikascript compilar and then build the project again. But the image did not get smaller, do you have any idea? |
the 57k image is after commend the machin.py file. if not commend the machin.pyi, the imagesize would be 71K
|
Great, thanks a lot!! |
I have got the bluepill template for pikascript and then made a Makefile to compile with arm-none-eabi-gcc, the code is in this repository.
I was able to compile all .c files in the template into objects and them link them successfully, I could also build a binary firmware.
The issue is that the size is WAY too big for 128K bluepill flash memory, so I would like to know what objects may not be compiled to build a smaller binary.
Thanks in advance!
The text was updated successfully, but these errors were encountered: