michalkowalik / pdp11 Goto Github PK

an example of machine code causing a trap is needed.

.. to wrap the writeWord and writeByte / readWord and readByte methods on all the CPU instructions.

This way the core of the byte / word instructions can stay unchanged.

when using the new MMU18 struct mmu implementation, the system hangs before showing the unix prompt.

It was not the case with the previous mmu implementation (which failed otherwise, but anyway).

compare the memory dumps and the debug information to find any kind of possible reason, that could explain the behaviour.

• compare the results from fix/write-to-readonly-page with master
• compare the resulsts from fix/write-to-readonly-page with DC's implementation

• log register status
• log icoming instruction
• log to file
• make it relatively easy to turn off / on
• follow the logging method used in teletype

The main cpu loop should be able to happily stay forever with either a wait state or looping back and forth in a loop.

Currently it effects in cpu and memory usage explosion and complete lack of responsiveness on the console.

Map registers to Unibus address, modify GetVirtualByMode

Full set of 17 instructions.

the bootstrap code from the aiju pdp implementation will be used initially.

• return string from cpu, update view in main.

• implement the interrupt channel handler

• re-implement,
• make sure it doesn't explode CPU and memory usage