Skip to content
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

Builds that do not fit within the FC's flash should produce a better failure message #114

Open
rmackay9 opened this issue Dec 9, 2024 · 0 comments

Comments

@rmackay9
Copy link

rmackay9 commented Dec 9, 2024

This issue is in response to this 4.6.0-beta1 user report in which the user saw a linker error and was unable to produce a firmware for their autopilot.

The issue turned out to simply be that the build would not fit in the autopilot's flash. We should improve the message so that the user knows they can resolve the issue by de-selecting some features.

The current message is something like this

[1215/1222] Linking ../CubeOrangePlus/bin/arducopter
/home/custom/gcc-arm-none-eabi-10-2020-q4-major/bin/../lib/gcc/arm-none-eabi/10.2.1/../../../../arm-none-eabi/bin/ld:common.ld:202 cannot move location counter backwards (from 0000000008201e60 to 0000000008200000)
collect2: error: ld returned 1 exit status

Waf: Leaving directory `/mnt/volume_nyc3_01/custom/base/tmp/copter:CubeOrangePlus:4d31a7320a1d2c38e2d742ae63c34f914febaa8f:a440fcafd32cc20580367b5d6fc30a97/CubeOrangePlus'
Build failed

A better message would be something like, "flash overflow, reduce the number of features selected"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant