Changes

Jump to navigation Jump to search
m
When I finally load the firmware (I still haven't at this point) I spend ages looking for what calls these strings. I find it difficult to navigate but fascinating. It is difficult to navigate any production firmware disassembly I expect. I have no prior experience, but it seems the H8300H is kind of a different level, a bit of an oddity. It's used a lot in Japanese electronics. It is in a lot of Roland devices. Apparently it interleaves code and data frequently which makes static disassembly trickier. '''''Especially in Cutter, which won't decompile H8 instructions (it either links to Ghidra method, which does not support the H8, or JS, which can't de-compile either)'''''
===User / Diagnostic Monitor Strings -===
One or two strings can be discovered, which have a different call system to the diagnostic strings (the ones I'm most interested in) especially because I have to repair so many subsystems, ICs, and traces.
135

edits

Navigation menu