good luck&welcome
i'm also new on that midway system but it's good to share knowledge..
first examine "already found" cheats, as you see:
example: mk2
drain all energy now:
<action>maincpu.pb@10602F0=01</action>
what you notice here? it's a RAM cheat (p) and memory is at 1xxxxxx
as you check mk2.xml briefly, other (p) cheats are around 1030000 - 1060000
these are "real" memory addresses, so in debugger you can get its value with ctrl+m and entering 10602F0
but byte structure is "reversed" as explained.
Code: Select all
in monitor you'll see
1060280 0000000000000000 00A1000000000000
| | |
real memory 1060280 10602F0 10602C0
got it? first block's rightmost real value is 1060280, 2nd block's rightmost real value is 10602C0 and
10602F0 has the value A1.
so, for one byte catching, use this search in debugger:
ci ub,1000000,70000 (will search between 1000000-1070000)
yes, as you're aware, for ROM cheats,
<action>maincpu.mw@0003FD8=0300</action> (always secret game over)
use this to calculate REAL address: (or do the reverse for cheat.xml entry)
3FD8 * 8 = 1FEC0 + FF800000 = FF81FEC0
0300 is the NOP (no operation) opcode, so this ROM cheat stores 0300 to FF81FEC0, check in debugger, ctrl+D.
i can share other tips if needed..