PDP-11/45: MS11-L debug
Sat 18 June 2016 by Fritz MuellerAfter addressing the -15V problem on the MS11, most of the bad behaviors seem to have cleared up except a stuck (on) bit 6 in the first 16K words of address space (000000-077776). Hooked up the new logic analyzer, and it has been very useful in troubleshooting the board -- can easily capture and inspect the timing of complete memory cycles. Definitely worth the investment!
Using the analyzer, I was able to verify the refresh and chip select logic on the board, then track down the stuck bit to what seems to be a single failed DRAM chip (E96 on the MS11-L engineering drawings). I'd like to test the entire card before ordering replacement parts, but need to set up address translation to get beyond the first two banks from the console.
Here is the address translation register setup that I used for testing. This was followed by a deposit of 000001 to KT11 SR0 (777572) to enable translation. KT11 SR3 was left all zeros to keep D space disabled. This setup allows console access to physical addresses in banks 1 through 7 by appropriate settings of virtual address bits 13 through 15. I wanted to reserve PAR7 to map I/O space, so I left out bank 0 since it was one of the two already tested.
772340 | 001000 |
772342 | 002000 |
772344 | 003000 |
772346 | 004000 |
772350 | 005000 |
772352 | 006000 |
772354 | 007000 |
772356 | 007600 |
772300 | 077406 |
772302 | 077406 |
772304 | 077406 |
772306 | 077406 |
772310 | 077406 |
772312 | 077406 |
772314 | 077406 |
772316 | 077406 |
This worked as expected according to panel PROG PHY and the logic analyzer, so the KT11 option which I had not previously tested is at least working for kernel I space. Tested each bank on the MS11 from the front panel using this setup, and uncovered that bank 4 bit 10 also has a stuck on condition. Since bank 1 is working now, I can use that as work space for the time being in order to continue the CPU debug while awaiting some replacement DRAM chips in the mail.
Pics here of the logic analyzer setup, and captured traces of a write and subsequent read to one of the misbehaving chips: