0 Members and 5 Guests are viewing this topic.
Quote from: Kristaba on February 19, 2011, 08:06:49 amFirstly, what do you know about the G3A header checksum...it's the last information I need for my G3A wrapperIt's the last information I do not know either. But I experienced, that it is not essential. I assembled a little memory-viewer-G3A and did not care about this field. The G3A works without any problems. But anyhow, I like to know how this value is computed, too.
Firstly, what do you know about the G3A header checksum...it's the last information I need for my G3A wrapper
How that works is that every byte is added to a tally except for the four bytes at 0x20 and the last four bytes which are a copy of the checksum.
sh3_disass.py -s 10070 -e 10080 -p 80010070 ISSetupFile.SetupFile3 80010070: d202 .. MOV.L @($02*4+PC),R2 = #801B013080010072: 4008 @. SHLL2 R080010074: 002e .. MOV.L @(R0+R2),R080010076: 402b @+ JMP @R0 80010078: 0009 .. NOP8001007A: 0000 .. 0000 ?8001007C: 801b .. .data 801b0130 dword ref:80010070
000290: wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww0002b0: wwwwwwwwwp...wwwwww..wwwwwwwwwww0002d0: wwwwwwwwp.....wwwww..wwwwwwwwwww0002f0: wwwwwwww..ww..wwwwp..wwwwwwwwwww000310: wwwwwwwp.wwww..wwwp..wwwwwwwwwww000330: wwwwwwwp.wwwwp.www....wwwwwwwwww000350: wwwwwww..wwwwp.www.wp.wwwwwwwwww000370: wwwwwww.wwww........p.wwwwwwwwww000390: wwwwwww.wwww........w.wwwwwwwwww0003b0: wwwwwww.wwww.w.ww...w..wwwwwwwww0003d0: wwwwwww.wwww.w.ww.w.wp.wwwwwwwww0003f0: wwwwwww..www.p.wp.w.wp.wwwwwwwww000410: wwwwwwwp.www.p.wp.w.ww.wwwwwwwww000430: wwwwwwwp.www...w..w.ww..wwwwwwww000450: wwwwwwww..ww..ww.ww.wwp.wwwwwwww000470: wwwwwwwwp.....wp........wwwwwwww000490: wwwwwwwwwp...wwp........wwwwwwww0004b0: wwwwwwwwwwww.wwwwww.wwwwwwwwwwww0004b0: wwwwwwwwwwww.wwwwww.wwwwwwwwwwww0004b0: wwwwwwwwwwww.wwwwww.wwwwwwwwwwww0004b0: wwwwwwwwwwww.wwwwww.wwwwwwwwwwww000530: wwwwwwwwwwww........wwwwwwwwwwww000550: wwwwwwwwwwww........wwwwwwwwwwww000570: wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww
I notice that wiki claims that 0x0290-0x058F is garbage, but it's actually a small (64x24) black-and-white icon.
Quote from: z80man on February 19, 2011, 10:40:53 amHow that works is that every byte is added to a tally except for the four bytes at 0x20 and the last four bytes which are a copy of the checksum.Isn't the CRC checksum ignored too when creating the 0x0020 checksum?
I don't understand how you're supposed to read the data that's in files...
It would be annoying the Prizm processor isn't like a 7705, and I don't understand why Casio would do that
F. i. the RTC base-address h'FFFFFEC0 has been changed to h'A413FEDC.