3 ms·
That's correct. The data was also extracted using probes under a microsope in this case. From Dr Decapitator's page: "The data was extracted by laser-cutting
by Leynos 15y ago
That's correct. The data was also extracted using probes under a microsope in this case.
From Dr Decapitator's page:
"The data was extracted by laser-cutting the top two ROM bits from the actual CPU logic (so it would read all opcodes as OP(00) or LD(11) opcodes depending on whether lines were pulled high or low, and neither OP nor LD can branch address), then microprobing, 8 bits at a time, the ROM outputs from before the cut. The program counter was also monitored to ensure that the data read started at 0×000 and didn’t jump anywhere."
(http://decap.mameworld.info/2010/12/16/snes-dsp1b/ http://decap.mameworld.info/2010/12/16/snes-dsp1b/)
You can read more about chip decapping here: http://guru.mameworld.info/decap/index.html http://guru.mameworld.info/decap/index.html And here: http://www.defcon.org/images/defcon-12/dc-12-presentations/Grand/dc-12-grand.ppt http://www.defcon.org/images/defcon-12/dc-12-presentations/G...
- byuu 15y agoOh, good. I was intentionally vague there, as I wasn't sure how much was public knowledge. Yes, basically we bypassed the JP (jump) and RT (return) opcodes, so that the program counter always stepped by one. Externally clock the CPU to move to the next instruction, and keep logging the data lines prior to the OP/LD cuts.