• Please review our updated Terms and Rules here

Debugging Emulex UC07 SCSI in PDP-11/03

Ok, good point. I'm going to need to figure out how to make new bootable XXDP images, I think. I don't see a TU58 image for the 11/03 CPU tests over on AK6DN's XXDP image files page. I have an RL02 image file of XXDP 2.5 that looks like it includes those tests. So, hopefully I can create a bootable TU58 image with the proper CPU tests under a simulator. Time for some more learnin'…
 
Adding to the excitement, if I set up SIMH to emulate my hardware configuration plus an RL02, it halts when I try to boot the RL02 image of XXDP 2.5 that I have. It seems happier if I configure the simulator as an 11/44.
 
Adding to the excitement, if I set up SIMH to emulate my hardware configuration plus an RL02, it halts when I try to boot the RL02 image of XXDP 2.5 that I have. It seems happier if I configure the simulator as an 11/44.

Hmm, I get the same thing with SIMH V3.9-0. I can boot the XXDP V2.5 RL02 image with an 11/73 configuration, but if I change the CPU type to 11/23 and keep everything else the same it halts during boot. I'm sure I've booted XXDP V2.5 just fine on a real M8186 or M8189 11/23 CPU using disk MSCP boot disks created from the XXDP V2.5 RL02 image. Maybe this is just an issue with the SIMH emulation.

sim> show cpu
CPU, 11/73, NOCIS, idle disabled, autoconfiguration enabled, 256KB
sim> boot rl0
BOOTING UP XXDP-XM EXTENDED MONITOR
XXDP-XM EXTENDED MONITOR - XXDP V2.5
REVISION: F0
BOOTED FROM DL0
124KW OF MEMORY
NON-UNIBUS SYSTEM
RESTART ADDRESS: 152000
TYPE "H" FOR HELP !
.

<CTRL-E>
Simulation stopped, PC: 112404 (MOV (SP)+,R1)
sim> set cpu 11/23
sim> show cpu
CPU, 11/23, FPP, NOCIS, idle disabled, autoconfiguration enabled, 256KB
sim> boot rl0
HALT instruction, PC: 000104 (JMP SP)
sim>
 
I think I'll dig out my quad width CPU board(s) and try them out first. I have a couple of spare LSI-11/02 boards, but one failed to come up with an ODT prompt, and the other is marked "NFG DO NOT USE" so I didn't even try it. :)


When I said Quad Width, I meant specifically the M8189 or M8190 boards,
since they have the bootstrap, LTC, and SLU's on-board, and are far less prone
to configuration and interrupt related problems. ;-)
 
I do have an M8189, but I don't know if it works yet. I'll try it out, but first I'll continue debugging my system as-is with XXDP.

XXDP is starting to make some sense to me. I found batch script 11V03LQ.CCC which appears to be for my machine configuration (a PDP-11V03-L), so I used that as a starting point and added in what I think are the RX02 tests. I used DIAGDIR.EXE to make a TU58 tape image, and I was able to boot my machine from it using AK6DN's tu58em and a typed-in bootloader. I'm on a Mac, but I was able to run DIAGDIR.EXE under dosbox. As an aside, I haven't been able to get Ersatz-11 to run under dosbox; it complains about being out of memory. I can run Ersatz-11 under WinXP in VMWare, but I generally prefer SIMH since I can run it natively.

The CPU tests look like they passed. The memory exerciser (assuming I used the right one) ran for a long time, then dropped to ODT sometime after printing "PASS 01". I wasn't watching at the moment, as I was outside taking out the garbage. I assume that halting the processor is a bad sign! Here's the log. Does anything jump out to folks who have used XXDP before?


Code:
MEMORY MANAGEMENT UNIT NOT FOUND


BOOTING UP XXDP-SM SMALL MONITOR


XXDP-SM SMALL MONITOR - XXDP V2.6
REVISION: E0
BOOTED FROM DD0
28KW OF MEMORY
NON-UNIBUS SYSTEM

RESTART ADDRESS: 152010
TYPE "H" FOR HELP

.D

ENTRY# FILNAM.EXT        DATE          LENGTH  START   VERSION

    1  XXDPXM.SYS       1-MAR-89         39    000047    F.0
    2  XXDPSM.SYS       1-MAR-89         29    000116    E.0
    3  DRSXM .SYS       1-MAR-89         48    000153    C.0
    4  DRSSM .SYS       1-MAR-89         24    000233    G.2
    5  DIR   .SYS       1-MAR-89          7    000263    D.0
    6  DATE  .SYS       1-MAR-89          2    000272    B.0
    7  DD    .SYS       1-MAR-89          3    000274    D.0
    8  DY    .SYS       1-MAR-89          3    000277    D.0
    9  LP    .SYS       1-MAR-89          1    000302    B.0
   10  UPDAT .BIC       1-MAR-89         29    000303
   11  VKAAC0.BIC       1-MAR-89         16    000340
   12  VKABB0.BIC       1-MAR-89         16    000360
   13  VKACC1.BIC       1-MAR-89         16    000400
   14  VKADC1.BIC       1-MAR-89         13    000420
   15  VKAEB2.BIC       1-MAR-89          7    000435
   16  VKAFE0.BIN       1-MAR-89          5    000444
   17  VKAHA1.BIC       1-MAR-89         16    000451
   18  VKAIB0.BIN       1-MAR-89         15    000471
   19  VKAJB0.BIN       1-MAR-89         16    000510
   20  VKALA1.BIC       1-MAR-89         12    000530
   21  ZKMAF0.BIC       1-MAR-89          9    000544
   22  ZRXCA0.BIN       1-MAR-89          7    000555
   23  ZRXDC0.BIC       1-MAR-89         30    000564
   24  ZRXEA2.BIC       1-MAR-89         17    000622
   25  ZRXFB0.BIC       1-MAR-89         31    000643
   26  11V3LQ.CCC       1-MAR-89          1    000702
   27  11V3LH.CCC       1-MAR-89          4    000703
   28  HELP  .TXT      44-DEC-70C        29    000707

.C 11V3LQ.CCC
;
;
;      11V03L QUICK VERIFY DIAGNOSTIC CHAIN
;
;      LSI BASIC INSTRUCTION TEST (MAINDEC-11-DVKAA)
R VKAA??

 END PASS;      EIS INSTRUCTION TEST (MAINDEC-11-DVKAB)
R VKAB??

END PASS;      FIS INSTRUCTION TEST (MAINDEC-11-DVKAC)
R VKAC??

DVKACC - LSI-11 FIS  INSTRUCTION TEST
END PASS;      LSI TRAPS TEST (MAINDEC-11-DVKAD)
R VKAD??

CVKADC0 LSI-11 TRAPS TEST

EIS/FIS OPTION PRESENT
DIBOL INSTRUCTION SET NOT PRESENT

END OF PASS;      DLV11 TEST (MAINDEC-11-DVKAE)
R VKAE??
MAINDEC-11-DVKAE-B      DLVII TEST
01 DEVICES UNDER TEST
;      LSI SYSTEM EXERCISER (MAINDEC-11-DVKAH)
R VKAH??

DVKAH-ASQSJU
            :::2j

PASS=000001 ERROR=000000 RXERROR=000000 TIME=000000
;      MOS/CORE MEMORY EXERCISER (MAINDEC-11-DZKMA)
R ZKMA??

000000-157776
RELOC
PASS#   01
152012
@
 
I ran it again with the same results. This time I watched a bit more closely, and observed:

  • After printing "000000-157776" it ran for around 15 minutes.
  • Next it printed "RELOC" and ran for a few more minutes.
  • Finally it printed "PASS# 01" and then dumped to ODT at 152012.

Is this what a memory failure would look like in XXDP?
 
Another data point: I dug through my pile of inherited cards and found an M8044-DH RAM board that looks like it's in its original, unopened antistatic bag, with an original DEC tag hanging off of it. After plugging it in to my system in place of its original RAM board, the ZKMA test drops to ODT at the same address. Hmm…
 
You can find a listing for this diagnostic by googling for "MAINDEC-11-DZKMA" (maybe only an earlier version). It should tell you what you need to know, including halt points and how to figure out what they mean. Maybe you should run just the ZKMA diagnostic and see if it acts differently.
 
Last edited:
Just running the ZKMA diagnostic was a good idea. I get different results when I run it by itself right after a reboot. It's still running, so I don't know if it's passing or failing yet, but this gives me something else to work with.

Thanks for pointing out the need for the listings, too. I found a big cache of them at Bitsavers, and I plan to download all of them when I'm near better network access; either tonight or tomorrow.

I ran the RX02 functional diagnostic and got errors. I'll need to study them to figure out what's wrong. It's disappointing that my hardware doesn't seem to be running perfectly, but I'm also excited that I'm learning some new diagnostic tools and techniques.
 
When I start ZKMA right after a reboot, it appears to be passing.

I tried out my 11/23 CPU board. It's at least functional, though I haven't run diagnostics on it yet. The bootstrap didn't come up, but I don't know what's in the EPROMs (not mask ROMs) that are on it, so maybe I need to burn the proper bootstrap. I was able to bring up the UC07 utility from its ODT at least, so that's good.

At the moment, my gut feeling is that either there's something wrong with my LSI-11/02 CPU that I haven't detected, or maybe the UC07 doesn't work with the LSI-11/02 processor. The seller says he's going to try testing one with an M7270 to see if they'll work together.
 
Is it halting due to the fact it is runing a quick "chained" set of xxdp tests? i.e. after pass 1 is complete it has finished running the diags. It also only runs one pass of the CPU diags.
 
Hmm, I don't know if that's what's going on, but it makes sense. When I run ZKMA alone, it appears to repeat endlessly. In this case, I infer "endlessly" from 3 runs, because I only have so much patience. :)
 
Back
Top