Edit: 21st Jan 2008. Thought I would add this to the top of the forum as a few of our newer members and visitors were unaware of it. You can grab it from my site (source included in zip): http://www.4shared.com/file/40141635/c1a4571/ez5s.html
Not my work but I figured it would be of some interest. GBADev thread and download: http://forum.gbadev.org/viewtopic.php?t=13879 If you want to post your results here I will happily convey them.
Joined: Wed Feb 22, 2006 1:11 pm Posts: 903 Location: earth, you idiot
sorry for my stupidity (make that 437+ sorries
but does this mean there is a problem with the original DLDI??
could this be why EZV homebrew isnt perfect compatible??
sorry for my stupidity (make that 437+ sorries but does this mean there is a problem with the original DLDI?? could this be why EZV homebrew isnt perfect compatible??
This means that some homebrews (e.g. wolfenstein 3d) didn't work
correctly 100 % (sometimes wrong data was read from files. Writing
to micro sd worked correct).
The reason is that DLDI works with pointers to bytes (8-Bit) (that
can theoretically be any memory address), and some DLDI drivers
(and also the original source code from EZ-V) works with
instructions that works with a 32-bit word (that are 4 bytes).
These 32-bit data reads/writes only work correct on
4-byte aligned memory addresses (e.g. address 0, 4, 8, 12,16,20,
...,400,404,408,...,1200,1204,1208,1212,...) on the ARM microprocessor
in the GBA/NDS.
Some applications are providing non-aligned pointers for
file operations (e.g. a pointer to adress 1201), and then
wrong data is read by the application.
Users browsing this forum: Google [Bot] and 0 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum