• Please review our updated Terms and Rules here

KDF11-B diagnostics

jmdhuse

Experienced Member
Joined
Apr 30, 2022
Messages
145
Location
USA - Arizona
Hello All,

I have a couple of KDF11-B CPU boards and I have been running diagnostics on them, with some puzzling results. The diags I have been running are:

JKDJB0: KDF11-B CPU-BOARD M8189 GO-NOGO TEST
JKDL5B0: KDF11-BE CPU-BOARD M8189 GO-NOGO TEST

The first diagnostic always fails with the message: "FAILED DURING THE BDV TESTS", while the other passes without error. I have tried using different versions of the boot ROM, and I have manually set the PCR to all values and check that the proper ROM memory locations as accessed as expected.

Has anyone else seen this and can shed some light on it? Or, could anyone else run that first diag on a known-good KDF11-B CPU board and let me know what they see?

Thanks, Jon.
 
Originally JKDJ would stop with the same error.

I read the documentation - it says - the memory is not more than 32 kilowords, otherwise edit the software register of the switch - some tests will be disabled. I installed a 64 kb memory module.

I read more documentation - as I understand it - you need to close the input to the output for slu2. Ok closed.

Launched the test. It typed - the test started and ... nothing more. I'll wait :)
 
Originally JKDJ would stop with the same error.

I read the documentation - it says - the memory is not more than 32 kilowords, otherwise edit the software register of the switch - some tests will be disabled. I installed a 64 kb memory module.

I read more documentation - as I understand it - you need to close the input to the output for slu2. Ok closed.

Launched the test. It typed - the test started and ... nothing more. I'll wait :)
Hmmm. you have found more documentation than me. I only have the "PDP-11 Diagnostic Handbook 1988", which does mention the SLU2 turn-around connector (which I have installed), but doesn't say anything about memory size (I have a 64kW with parity memory card). Can you give me a pointer to the documentation you have?

Thanks, Jon.
 
Ah, I think I might have the answer...

I found the diagnostics database at "http://retrocmp.com/tools/pdp-11-diagnostic-database" and started digging through the documentation for these to tests. In the abstract for JKL5B0, it states that it was derived from JKDJB0 with changes made to the BDV test for 8kx8 boot ROMs. This makes sense because the earlier KDF11-B CPU boards had 2kx8 boot ROMs. I can't test this because the earlier 2kx8 boot ROMs don't support booting DU devices, which is where my XXDP system is stored. But it all makes sense.

I might try typing in a DU boot loader via ODT or set up the tu58 emulator so I can boot into XXDP with the small boot ROMs and then verify that JKDKB0 passes with the smaller boot ROMs installed.
 
Can you give me a pointer to the documentation you have?
Page 7, 1.4 - "The software assumes that there is no memory or devices located at or beyond address bit 17 (64 kw)."
Sorry, my mistake - not 32 kw, but 64 kw
In the abstract for JKL5B0, it states that it was derived from JKDJB0 with changes made to the BDV test for 8kx8 boot ROMs.
Yes, it makes sense. I don't have 2 kb ROM, but I can try to connect the ROM from KDF11-B to my PDP-11X (I have ROM content) and examine the test under the "microscope". But it's not until the weekend. And now I'll try to find a ROM test from the listing and bypass it with a patch.
 
Code:
HX 2.2  XXDP  Cold boot..
 
 
 
BOOTING UP XXDP-XM EXTENDED MONITOR
 
 
XXDP-XM EXTENDED MONITOR - XXDP V2.5
REVISION: F0
BOOTED FROM HX0
124KW OF MEMORY
NON-UNIBUS SYSTEM
 
RESTART ADDRESS: 152000
TYPE "H" FOR HELP !
 
.R JKDJ??
JKDJB0.BIN
 
START TESTING
FAILED DURING THE BDV TESTS
 
054474
@54404/104000 240
@200G
START TESTING
END OF PASS CJKDJB0
END OF PASS CJKDJB0
END OF PASS CJKDJB0
END OF PASS CJKDJB0

The patch "turns off" the error of the test trying to determine the type of ROM.
 
I also did some work this morning... I replaced the 8kx8 EPROMs with the 23-339E2/23-340E2 EPROMs (which are 2kx8), booted the system using the tu58 emulator, ran the JKDJB0 diagnostic with the SLU2 test disabled (because I'm using SLU2 as the connection to the emulator), and the test passed without complaining.

Looks like we've pretty much confirmed by two different approaches... thanks for your help!!!
 
Back
Top