thunter0512
Veteran Member
Recently I got a second RK8-E board set (M7104/M7105/M7106). Unfortunately all 3 boards have faults.
Multi-board subsystems are more difficult to debug, but fortunately @Roland Huisman has created H851 extenders which make debug-life much easier:
https://github.com/Roland-Huisman/Digital_PDP8_debug_tool_for_H851_connections
Thank you Roland!
I have built 8 of these and with 4 IDC cables of 30 cm length and a quad extender board I have a realistic chance of debugging and fixing this controller.
Here are some photos of my initial debug setup (click on the photo to see full size):
I am using the "DHRKA RK8E Diskless Control Test" maindec-08-dhrka-e-pb to trigger the faults and attempt to capture the relevant context via the attached oscilloscope.
The first problem I see is that DRST ("Read Status") IOT reads an invalid status with the "Control Busy" bit spuriously set. The DRST part of the logic is implemented on the M7104 board.
It turns out that the DRST IOT correctly reports what it sees. The problem is that the controller is not in the IDLE state as indicated by the active low IDLE input being always high.
Here are the relevant parts of the schematic with the interesting parts highlighted (click to see full size):
Of course the IDLE bit is implemented on another board, the M7106. This means rearranging my debug setup.
I already have a suspect without even probing the board. The most likely candidate is the IDLE flipflop E18 a 7474 which seems to have a high failure rate.
Multi-board subsystems are more difficult to debug, but fortunately @Roland Huisman has created H851 extenders which make debug-life much easier:
https://github.com/Roland-Huisman/Digital_PDP8_debug_tool_for_H851_connections
Thank you Roland!
I have built 8 of these and with 4 IDC cables of 30 cm length and a quad extender board I have a realistic chance of debugging and fixing this controller.
Here are some photos of my initial debug setup (click on the photo to see full size):
I am using the "DHRKA RK8E Diskless Control Test" maindec-08-dhrka-e-pb to trigger the faults and attempt to capture the relevant context via the attached oscilloscope.
The first problem I see is that DRST ("Read Status") IOT reads an invalid status with the "Control Busy" bit spuriously set. The DRST part of the logic is implemented on the M7104 board.
It turns out that the DRST IOT correctly reports what it sees. The problem is that the controller is not in the IDLE state as indicated by the active low IDLE input being always high.
Here are the relevant parts of the schematic with the interesting parts highlighted (click to see full size):
Of course the IDLE bit is implemented on another board, the M7106. This means rearranging my debug setup.
I already have a suspect without even probing the board. The most likely candidate is the IDLE flipflop E18 a 7474 which seems to have a high failure rate.