![]() ![]() Then also copy the contents of the Common folder, which contains the DasmDataInspectorPlugin.ini and the various CPU definition. dll version (based on your Windows installation), and copy the content of this folder into your HxD installation directory, creating (or updating) the "Plugins" sub-directory of your HxD installation directory. If a later HxD version requires changes to the plug-in interface, I will update the plugin here (as required).Īs per Maël's instructions for the plugin framework, the files should all be installed into a "Plugins" sub-directory of your HxD installation directory.įirst select either the Win64 or Win32 folder. This plugin is currently compiled for 2.5.0.0. Installationįirstly, ensure you are running HxD 2.5.0.0 version. Specifically, where a CPU has a significantly more complex instruction set, resulting in an excessively large number of resulting possible opcode + operand combinations. ![]() However, I suspect limitation may be found if attempting to define more advanced / modern ISA's. These generally have relatively simple instruction sets and addressing modes, which the definition files easily cater for. Note that while this implementation provides great flexibility for adding additional CPU Disassembly support, it's target audience is retro microprocessors. csv file parsing and format errors (typos?) that are identified. ini file provides for a log file to be enabled. csv files (or any changes you might want to make), the. ![]() To assist with debugging your own definition. (refer below), and also the more complex MC6809 8/16 bit processor definition file. I've now also added several other processor definition files including 6502 family etc. To get started, I initially created a Motorola MC6800 definition file as: Dasm6800.csv csv based instruction definition file is also included. ini file (DasmDataInspectorPlugin.ini) for parameters, including details of the configured CPU's / Disassembly types.įor each configured CPU, a. dll (DasmDataInspectorPlugin.dll) references a. In other words, create a Disassembly plugin that anyone could add support for another CPU, without needing to write a whole new instruction disassembler / without having to make any code changes. To allow support for different CPU instruction Disassembly, I decided to implement a generic Disassembly plugin, that would allow additional CPU's to be supported by dropping-in new CPU definition files. which I have now done), and maybe even 68000, and looking at existing disassemblers, I really didn't like the "hard-coded" processor specific parsing approach. Plus, with my retro CPU interests, I could see that I'd potentially want to also add 68 code disassembly (ed. I initially looked for a pre-written Disassembler that I could integrate via Maël's published plugin framework: īut I quickly came to the conclusion that there wasn't really anything substantial that I could (relatively easily) migrate for this purpose. I was immediately impressed that Maël had included support for Motorola S-record files, and when I noticed the Data inspector included x86 Disassembly I immediately thought how useful 6809 Disassembly would be.Īs I was seeing byte differences in my 6809 ROM comparisons, I was having to manually identify what the code differences were. I came across HxD while looking for a good hex editor, to allow visually comparing & analysing the differences between some retro Motorola MC6809 Monitor ROM images. This plugin is compiled for HxD v2.5.0.0 Background This plugin is for Maël Hörz's excellant HxD hex and disk editor, which is available at: Disassembly Plugin for HxD's Data inspector ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |