Is your feature request related to a problem? Please describe.
When simulating a CPU it is difficult to match clock cycles in the waveform viewer to the assembly. The result is a lot of swapping between windows and general friction when debugging and learning how the CPU works
Describe the solution you'd like
The ROM could allow a comment to be attached to each address in its contents. The comment would be viewable as an additional signal during simulation. The comments could be provided in the ROM contents file, allowing it to be automatically entered by an assembler. Maybe RAM should support comments too for labelling variables.
Describe alternatives you've considered
There could be an additional 'radix' that displays simulation data as disassembly. This has the advantage that instructions held in registers can be decoded as well as ROM. However, the disassembler would be ISA-specific, and it would require per-signal setting of the display radix, which could clutter the UI. Another option could be some kind of binary-to-text map that could be applied to the opcode field
Is your feature request related to a problem? Please describe.
When simulating a CPU it is difficult to match clock cycles in the waveform viewer to the assembly. The result is a lot of swapping between windows and general friction when debugging and learning how the CPU works
Describe the solution you'd like
The ROM could allow a comment to be attached to each address in its contents. The comment would be viewable as an additional signal during simulation. The comments could be provided in the ROM contents file, allowing it to be automatically entered by an assembler. Maybe RAM should support comments too for labelling variables.
Describe alternatives you've considered
There could be an additional 'radix' that displays simulation data as disassembly. This has the advantage that instructions held in registers can be decoded as well as ROM. However, the disassembler would be ISA-specific, and it would require per-signal setting of the display radix, which could clutter the UI. Another option could be some kind of binary-to-text map that could be applied to the opcode field