TASEmulators / TASEmulators/BizHawk
Code Data Logging (CDL) support in PicoDrive (MD/32X)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Currently, Code Data Logging is only supported with GenesisPlusGX, but not PicoDrive. It would be great if PicoDrive had CDL support as well, since it can also emulate 32X games. Having a code/data logger for 32x games would be immensely useful, as it can label data that's accessed by either the 68K, Z80, or the twin SH2 processors, as well as the two VDPs (the Mega Drive's and the 32X's). It would help with creating disassemblies, as data and code can be accurately marked as to what part of the ROM correlates to a specific CPU. Prototype research (or just research for TCRF/rom hacking in general) would greatly benefit from it as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the existing GenesisPlusGX CDL support with the PicoDrive core and its handling of the 68K, Z80, twin SH2 processors, and both VDPs. Done means CDL data and code accesses are logged and correctly attributed for 32X games; the issue names no files or tests, so the relevant integration points must first be mapped.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100