-
Notifications
You must be signed in to change notification settings - Fork 83
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
Is posible reduce size of the final binary ? #120
Comments
I have the same issue. Trying to build katapult for the voron 0 display and expander MCUs. The "Initial Release" has some compiled binaries that are below 4096 byte, but I'm wondering if this is still doable make output
|
I was able to flash the old canboot binary from "Initial Release" and use it to update klipper on the v0 display and klipper expander MCUs. Now the boot jumper isn't necessary anymore. |
@WegnerDan the configuration you posted comes out to 3928 bytes using master of today with compiler version: arm-none-eabi-gcc (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614 That compiler version was released in 14th of June after your comment, so perhaps you may want to revisit it to use a new version of katapult? (I haven't actually tested the compiled binary) |
Hi, i used katapult on multiples MCU and work great, but i tried on stm32f042 this contains 32kb flash. I tried to compile katapult using application start offset 4k but final binary is more large than this size. My intention is install klipper but the size of the binary and katapult is more than 32k.
Is posible reduce this binary ? reduce the number off features ?
The text was updated successfully, but these errors were encountered: