Closed rattboi closed 3 years ago
The Arch-based stm32-build docker image started using gcc 11, which broke the linkerscript hack to embed the menu into the firmware.
I made a new Dockerfile that is alpine-based, uses arm-none-eabi-gcc 10.2, and also includes uf2conv.py for future UF2 support
run make docker-build to build the new stm32-build container
make docker-build
for non-UF2 firmware, use the previous process: make clean all USE_HW=v0.3
make clean all USE_HW=v0.3
for UF2 firmware, use the following command: make clean all uf2 USE_HW=v0.3 USE_UF2=1
make clean all uf2 USE_HW=v0.3 USE_UF2=1
I, Bradon Kanyid, agree to license my contributions to this project under the terms of the GPL 3.0 or any later version.
Bradon Kanyid
Please add your full legal name above, for this PR to be mergeable. If you would prefer to sign a CLA via email, please request that.
Problem
The Arch-based stm32-build docker image started using gcc 11, which broke the linkerscript hack to embed the menu into the firmware.
Solution
I made a new Dockerfile that is alpine-based, uses arm-none-eabi-gcc 10.2, and also includes uf2conv.py for future UF2 support
Steps to Test
run
make docker-build
to build the new stm32-build containerfor non-UF2 firmware, use the previous process:
make clean all USE_HW=v0.3
for UF2 firmware, use the following command:
make clean all uf2 USE_HW=v0.3 USE_UF2=1
Contributor License Agreement
I,
Bradon Kanyid
, agree to license my contributions to this project under the terms of the GPL 3.0 or any later version.