updated readme.md

This commit is contained in:
hneemann 2016-12-17 17:54:14 +01:00
parent 591be2c9cb
commit 97b790f4be

View File

@ -117,13 +117,13 @@ in assembly language programs. So the debugging of assembly programs becomes ver
### Debugging ###
In Logisim there is no way to debug an assembly program in a simulated processor.
If an assembler is available which creates a LST file of the source code (code address followed by the source code line)
Digital can view this listing in a trace window with the current instruction being highlighted.
So the simulator can run an assembly program in a debug friendly single step mode.
Since Digital has a simple TCP-based remote control interface, also an [assembler IDE](https://github.com/hneemann/Assembler)
can be used to control the simulator and load assembly programs in the simulated processor, start the program, perform
single steps and so on.
In Logisim there is no easy way to debug an assembly program in a simulated processor.
Digital has a simple TCP-based remote control interface, so an [assembler IDE](https://github.com/hneemann/Assembler)
can be used to control the simulator and load assembly programs into the simulated processor, start the program, perform
single steps and so on. If a "single step" or a "run to next BRK instruction" is triggered by the assembly IDE, the
actual used address of the program memory is returned to the assembler IDE.
This allows the assembler IDE to highlight the actual executed instruction. In this way it is very easy to debug an
assembly program executed by a simulated processor.
### Circuit Synthesis ###