You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to add a couple of 6805 variants to Ghidra. These are unusual in that the wiring to the instruction latch has been shuffled -- and in one case, a few bits have been inverted.
It appears that the quick-and-obvious way to implement this is to copy-paste the 6805 SLEIGH definition for each chip and change the opcode byte and field comparisons to account for the bit twiddling.
Is there a way I can tell Ghidra to map the input opcode bytes into standard 6805 opcodes? That is to say, tell it that when it reads on opcode, it needs to shuffle some bits around and XOR the result with another constant?
This discussion was converted from issue #1462 on March 21, 2023 14:38.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'd like to add a couple of 6805 variants to Ghidra. These are unusual in that the wiring to the instruction latch has been shuffled -- and in one case, a few bits have been inverted.
It appears that the quick-and-obvious way to implement this is to copy-paste the 6805 SLEIGH definition for each chip and change the opcode byte and field comparisons to account for the bit twiddling.
Is there a way I can tell Ghidra to map the input opcode bytes into standard 6805 opcodes? That is to say, tell it that when it reads on opcode, it needs to shuffle some bits around and XOR the result with another constant?
Beta Was this translation helpful? Give feedback.
All reactions