I am using CubeOrangePlus for my testing.
As a standard way, I configure and build using commands
./waf configure --board CubeOrangePlus
./waf copter
and at the end after successful building, I am getting these results.
as I can see only 8kb is free in the default build.
I want more space to adjest some feature.
I need help for that. is there any way to do this…? @everyone @here
you can try this and see if you can remove features you don’t need to make room
Thanks for the replay,
I am trying to achieve secure Firmware using this guide.
However, I suspect I cannot achieve it due to a lack of memory.
I am fairly certain you can build the signed bootloader and sign the firmware after you’ve built the firmware somewhere else.
Thanks for this guidance,
I tried your way and was able to generate a build with less size but I am not able to sign firmware after that.
I see the steps again and found that we are configuring cubeorangeplus with --signed-fw flag and then generating the build that step is a mission in the online build.
because fo that I am not able to sign FW.
Credit to @amilcarlucas and his Methodic Configurator AI Guru!
Yes, you can sign ArduPilot firmware after it is built. To do this, you need to use the make_secure_fw.py script. Here is an example command for signing a copter firmware:
./waf configure --board BOARDNAME --signed-fw
./waf copter
./Tools/scripts/signing/make_secure_fw.py build/BOARDNAME/bin/arducopter.apj NAME_private_key.dat
This process involves signing the .apj firmware file with your private key. You can then load the signed firmware using a ground station like MissionPlanner or via Tools/scripts/uploader.py on Linux. For more details, refer to the README.md on GitHub.
My Edit:
In order to be useful, you’ll also need to build a bootloader with your keys installed, which you can do separately on your own, then later combine the firmware with the bootloader
I am happy that it helped you! Thanks for letting me know.
It’s worked for me thanks for your help