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

Minor firmware blit flashing improvements #785

Merged
merged 10 commits into from
Jan 13, 2023

Conversation

Daft-Freak
Copy link
Collaborator

First half: fixes some issues with failed flashes. Second half: use file size from headers instead of the actual file size.

  • Fixes a crash when flashing a .blit fails
  • Prevents overwriting things stored at the start of flash when running low on space (or trying to flash something unreasonably big)
  • Simplifies size calc a little and is consistent with the size used after the file is flashed

A side effect of this is that you can append extra data to the end of a .blit and the flashing code ignores it (at least when loading from the SD card). Previously it would get flashed, but would likely get another .blit flashed on top of it later.

Results in the bar disappearing if you attempt to save a ~14MB+ file
We don't get any info about why it failed... so it's not the most helpful message
If we don't we might write some extra data at the end of the file...
But it will get overridden when the next game is flashed. (The scanning
code uses the length in the header.)
~700 bytes less code than the 64bit divide
@Gadgetoid Gadgetoid merged commit 75e837a into 32blit:master Jan 13, 2023
@Gadgetoid
Copy link
Contributor

I should probably prep a release at some point to sweep up all these changes!

Thank you, and sorry for the continued lack of attention here- I think burnout is slowly grinding me down 😭

@Daft-Freak Daft-Freak deleted the blit-size branch January 13, 2023 12:31
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

Successfully merging this pull request may close these issues.

2 participants