[READY] Reduce hex size

[mcgalliard]

6 months ago gap fill was added to post build hex copying. This caused some hex inflation - up to 1GB....
This needed to be removed

[zyonse]

Why was gap fill originally enabled?

[mcgalliard]

Why was gap fill originally enabled?
See https://github.com/PurdueElectricRacing/firmware/commit/1248be27d0e4654c988086544c2231785b8e73e2
"Main module output had multiple segments (only a few bytes away). The bootloader doesn't support jumps in address, so we will just send some zeros to fill the gap"

We will need to add bootloader support for jumps in address

[AdityaAsGithub]

Underlying issue necessitating gap fill should be fixed before this gets merged into master.

[ColexDev]

The link you sent in response to Gavin leads to a 404 for me. I would also like to see the original reasoning behind why we added the gap-fill flag as well.

The bootloader doesn't support jumps in address

What? Why is this? The bootloader is not able to jump and has to run sequentially?

[zyonse]

@ColexDev this is the commit he linked: 1248be2

im testing sum out

The base branch was changed.

[AdityaAsGithub]

This MR should not merge, for the same reason I mentioned earlier

Testing something out I still don't this

I was testing the CODEOWNERS file

[LukeOxley]

Test :•)

🐢