Progress on the disassembler

Progress is being made on the disassembler; going in alphabetical order, I am now at MOV. Note that many instructions not used within zeptoforth are being omitted, and even then it will almost certainly be very large in memory footprint (it will likely have to be compiled to flash, as if it fits in RAM in the first place it will likely take up a good portion of it).

Discussions

Thomas wrote 05/10/2020 at 08:30

I assume that your use case for the disassembler is debugging in a self-contained development environment. In that case it might be interesting to decode what you use but also detect (but not necessarily decode) instructions that you don't intend to use. This could even be turned into a safety feature.

Are you sure? yes | no

Travis Bemann wrote 05/10/2020 at 19:29

I am really implementing a disassembler so the user has access to SEE. About detecting instructions that I do not decode, I still need to add entries to my instruction tables, which would still take up more memory. Whether I do that depends on just how much memory it takes up.

Are you sure? yes | no

Thomas wrote 05/10/2020 at 20:00

I see, this makes sense :-)

Are you sure? yes | no

​Progress on the disassembler

A disassembler is in the works

Initial coding of the disassembler is done, now time for debugging

Discussions

Become a Hackaday.io Member