Replies: 3 comments
-
The You could also install taps on it with a Lua script. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you. That sounds promising, although it doesn't work: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Use Lua script (either with vspace = manager.machine.devices['c117'].spaces['program']
action = function(offset, data) print("Watchpoint hit"); manager.machine.debugger.execution_state = 'stop'; end
wpr = vspace:install_read_tap(0x2fc000, 0x2fc000, "wp", action)
wpw = vspace:install_write_tap(0x2fc000, 0x2fc000, "wp", action) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am looking into the Namco System 1 driver. It has a hack related to the MCU marked in the driver as a very obscure point and I am trying to make sense of it by measuring the real MCU on the board.
Related to this, I am trying to see how the CPUs interact. But, I find it very hard to catch writes to memory because two of the CPUs use a memory mapper. This mapper has a virtual_map address space (in namcos1.cpp)
It looks like I cannot normally add watchpoints to this memory map. I have to use the CPU regular memory map, which keeps changing as the CPU programs the mapper.
Is there a way to watch virtual memory maps in the debugger?
Beta Was this translation helpful? Give feedback.
All reactions