Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSRAM saves are incorrect size. #883
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
...wait what |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cheatfreak47
Sep 23, 2017
Yep, that's how it is, the Static RAM chip or Ferroelectric RAM chips used in GBA games are only ever have 32kb of actual storage, If games need 64KB of storage, they use FLASH512kbit (64KB) chips.
cheatfreak47
commented
Sep 23, 2017
•
|
Yep, that's how it is, the Static RAM chip or Ferroelectric RAM chips used in GBA games are only ever have 32kb of actual storage, If games need 64KB of storage, they use FLASH512kbit (64KB) chips. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
how did I never know that |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cheatfreak47
Sep 23, 2017
¯\(º_o)/¯
I think VBA-M is still doing this wrong too actually, I should make an issue on their tracker
but I like mGBA more ^_^
the 3DS AGBFIRM mode gets this right since it's effectively a real GBA, it's files are only 32kb.
cheatfreak47
commented
Sep 23, 2017
•
|
the 3DS AGBFIRM mode gets this right since it's effectively a real GBA, it's files are only 32kb. |
endrift
closed this
in
5dfa036
Sep 23, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
endrift
Sep 23, 2017
Member
I dug through a bunch of my SRAM saves and verified. I'm not sure how OOB works yet so I'm not gonna backport this to 0.6.1 until I do.
|
I dug through a bunch of my SRAM saves and verified. I'm not sure how OOB works yet so I'm not gonna backport this to 0.6.1 until I do. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cheatfreak47
Sep 23, 2017
@endrift http://problemkaputt.de/gbatek.htm#gbacartbackupsramfram there's some really good data on this page if you want to read up sometime.
cheatfreak47
commented
Sep 23, 2017
|
@endrift http://problemkaputt.de/gbatek.htm#gbacartbackupsramfram there's some really good data on this page if you want to read up sometime. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
endrift
Sep 23, 2017
Member
You say that as though I don't have that as a pinned tab and have for years ;)
|
You say that as though I don't have that as a pinned tab and have for years ;) |
added a commit
that referenced
this issue
Sep 23, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
sergiobenrocha2
Sep 30, 2017
Contributor
Qt frontend is not changing from 64 to 32 kB automatically. You get 32 kB only with new saves.
|
Qt frontend is not changing from 64 to 32 kB automatically. You get 32 kB only with new saves. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
endrift
Sep 30, 2017
Member
Yeah, the frontend will never shrink files. It's not really a big deal I don't think.
|
Yeah, the frontend will never shrink files. It's not really a big deal I don't think. |
cheatfreak47 commentedSep 23, 2017
SRAM / FRAM saves should be 32KB in size, fixing this would not break compatibility with VBA save either I don't think, as those simply pad out the extra 32KB with
FFbytes, to fix that, simply accept 64KB saves for SRAM and when outputting a new save, overwrite it with 32KB.This shouldn't matter really but I figured it was worth mentioning anyway.