You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SPM_PAGESIZE varies between platforms; 328p = 128, 2560 = 256.
Memory is currently read byte per byte, but no such functionality exists for writes, instead writes are per page. On the 328p this is straightforward as page sizes match the PS1 memory card at 128bytes per frame. The 2560 would require a more advanced scheme.
A page buffer could be used, assuming that each sector write would occur in sequential order.
In the event of a timeout or non-sequential write, one part of the buffer is filled with the missing frame, written, and committed, repeat for other frame? Store address for both frames etc.
Read code must also be adapted for address space beyond 64Kb:
far_away
far_far_away
far_far_far_away
Maximum array sizes are 0x7FFF, need to split data between const arrays and align with page sizes.
The text was updated successfully, but these errors were encountered:
SPM_PAGESIZE varies between platforms; 328p = 128, 2560 = 256.
Memory is currently read byte per byte, but no such functionality exists for writes, instead writes are per page. On the 328p this is straightforward as page sizes match the PS1 memory card at 128bytes per frame. The 2560 would require a more advanced scheme.
A page buffer could be used, assuming that each sector write would occur in sequential order.
In the event of a timeout or non-sequential write, one part of the buffer is filled with the missing frame, written, and committed, repeat for other frame? Store address for both frames etc.
Read code must also be adapted for address space beyond 64Kb:
far_away
far_far_away
far_far_far_away
Maximum array sizes are 0x7FFF, need to split data between const arrays and align with page sizes.
The text was updated successfully, but these errors were encountered: