• Please review our updated Terms and Rules here

What are the Steps for getting TU58 Running ??

Hi All;
THANK YOU, Don !!!
""Second, if the address LEDs at halt show '000225' that is a problem, as the PC on the PDP-11 must ALWAYS be even. Something is really wrong if your PC is ODD.""
That is The Greatest Piece of News that I could get !! THANK YOU !!! It Gives me a clue as to where to look.. I'll Bet That somewhere in the code a bit is set in the PC and that it, isn't set correct or looses what was Set..
Or Maybe something is wrong on some of the steering logic, since there is some half byte swapping going on, maybe when its supposed to be one register, that the PC as well gets swapped by "accident" because of some steering logic problem.. Or under the programs that I have Run so far a certain bit has Not been Used, that is now being used, and its stuck either High or Low..
Secondly, "" First, 'boot.dsk' was meant to be a generic name in that documentation, it is not the name of a specific disk. 'boot.dsk' could be 11xxdp.dsk, 1123_1.dsk, 1144_1.dsk, etc, or any bootable disk from my TU58EM files web page. ""
That is Also what I didn't know or Understand.. THANK YOU for the Clarification of that Point.. It is Exactly what I didn't Follow.. I am Sorry that I was/is confused.. Please Forgive my lack of UnderStanding..
''''And lastly, all the TU58 info I have is on these two pages: http://ak6dn.dyndns.org/PDP-11/TU58/ and http://ak6dn.dyndns.org/PDP-11/TU58/tu58em/ so I don't know how much more specific I can be.""
Its Easy to Trip up someOne like me, sometimes its takes some explaining for me to get it into my Thick head..
You are Doing a Great Job, Keep up the Good and Great Work !!!!!!!!!!

THANK YOU Marty
 
Last edited:
Hi All;
Maybe I got some good news..
Don the Address when the Machine on the Front Panel (console) is like I stated before is '000225, and the Data is '000226.. I didn't look at any of the Registers, I will do so at a later time..
Anyway, I got an XXDP.Tap file from RSX11M, for running under E11.. So I copied it to my Tu58 directory and renamed it XXDP.DSK..
After the Halt, I restarted it, and got lots of puts and gets, but the outcome IS that --
I got XXDP to come up on the screen and it seems like it is working, as well as the TU58 unit.. I tried to ask for help, it went looking for that file and reported that, that file Doesn't exist, which I think is True, at least its not in my TU58 Directory..
I now need to find and look in the XXDP Users Manual and see what commands there are and if I can make them work.. That will be the Real Test to see IF it is actually working..
And I can Restart it at '152010..
When I did a "D" command or a "D/F" command it states that it has a Read error on DD0.. Since (I think) this machine Doesn't have DD0, I would expect as much.. Unless the TU58 is DD0.. I will have to look and see what the TU58 is called in DEC speak..
THANK YOU Marty
 
Last edited:
Marty - we need screen captures. I'm not able to make out where you are.

For those in the know - this tape contains XXDP+ (labeled 2.2) with DRIVERs, UTILS, UPD1 and UPD2 plus a few files of 11/45 diags (see my earlier post) I expect he'll need me to create another tape with a customized CCC file on it.

I'll wait for Marty's next response. I don't want to speculate on where he is only to find I'm in the wrong pew again.
 
Last edited:
Hi All;
RSX11M, OK, This is the Screen shot of Tera-Term which is my Monitor for the PDP 11/45..



CHMDDC0 XXDP+ DD MONITOR
BOOTED VIA UNIT 0
28K UNIBUS SYSTEM

ENTER DATE (DD-MMM-YY):

RESTART ADDR: 152010
THIS IS XXDP+. TYPE "H" OR "H/L" FOR HELP.

.H
? NOT FOUND: HELP .TXT
.H/L
? NOT FOUND: HELP .TXT
.
.DIR
? INVALID COMMAND
.D
? RD ERR WHILE READING DD0DIRECTORY

.D
?RD ERR

.D
? RD ERR WHILE READING DD0DIRECTORY

.F
000001

.D/F
?RD ERR

.
.D
? RD ERR WHILE READING DD0DIRECTORY

.D/F
? RD ERR WHILE READING DD0DIRECTORY

This is where I Stopped it.. I most likely can give a screen shot for the TU58em But it would be Horribly long..
How can I Increase the Buffer size or How is kept on the screen on the DOS Command Prompt Screen ??
I have only some of what was put out by the TU58.. I can show You the Tail End of the TU58 screen..
THANK YOU Marty
 
Last edited:
Ok, that's excellent. You indeed have booted XXDP. I need to think on this a bit. I suggest you go back to E11 - boot the tape there and practice XXDP to familiarize yourself with how it is when it works. BTW- I may not have included the HELP.TXT file in the tape, but D should have worked.

My suspicion is that your 11/45 is not able to talk to the TU58 emulation software perfectly enough. A post of the gobble-d-gook on the TU58 screen may be of help. If you can scroll back - we'd really like to see where it goes from good to bad. That may not be possible... if so just post 10 lines or so.

Give me a bit to think while you practice on E11.
 
Hi All;
RSX11M,OK, Well Here goes, this is what I have.. Its not the whole program but it is the last part of it..


info: putpacket()
01 80
6E 7D BB 7A 06 33 00 00 7D 00 02 00 7E 00 00 00 A4 32 6E 96 BB 7A 06 33 00 00 7
F 00 03 00 81 00
00 00 A4 32 AE 9C BB 7A 06 33 00 00 82 00 03 00 84 00 00 00 AB 32 EE 0C BB 7A 0
6 33 00 00 85 00
01 00 85 00 00 00 AC 32 46 64 BB 7A 06 33 00 00 86 00 01 00 86 00 00 00 AD 32 2
E 77 BB 7A 06 33
00 00 87 00 03 00 89 00 00 00 B0 32 6E 19 BB 7A 06 33 00 00 8A 00 03 00 8C 00 0
0 00 B0 32 6E 64
12 C1
info: putpacket()
01 80
BB 7A 06 33 00 00 8D 00 01 00 8D 00 00 00 B0 32 EE 70 BB 7A 06 33 00 00 8E 00 0
1 00 8E 00 00 00
B0 32 6E 7D BB 7A 06 33 00 00 8F 00 01 00 8F 00 00 00 B4 32 C6 70 BB 7A 06 33 0
0 00 90 00 02 00
91 00 00 00 0C 34 16 0D BB 7A 06 33 00 00 92 00 0C 00 9D 00 00 00 0C 34 96 19 B
B 7A 06 33 00 00
9E 00 0D 00 AA 00 00 00 0C 34 56 45 BB 7A 06 33 00 00 AB 00 0C 00 B6 00 00 00 0
0 00 00 00 00 00
23 48
info: putpacket()
02 0A
40 00 00 00 00 00 00 02 00 00
42 0C
info: read time=1125ms
info: flag=0x02 last=0x02
info: getpacket()
02 0A
02 00 00 00 00 00 00 02 45 00
49 0C
info: opcode=0x02 length=0x0A
info: read unit=0 sw=0x00 mod=0x00 blk=0x0045 cnt=0x0200
info: putpacket()
01 80
46 00 01 00 2E 00 00 00 F8 03 6A 04 34 04 5E 04 00 04 FA 02 2C 04 4A 00 F6 04 0
0 00 40 FD 00 00
00 00 00 00 00 00 00 00 01 00 00 00 32 00 00 00 EA 01 00 FD 01 32 00 03 00 04 0
0 07 00 01 00 01
00 02 00 FF 01 28 00 01 00 00 00 08 00 00 00 26 10 66 10 35 8A FF FF 37 0A 82 0
2 40 13 77 1D 02
00 74 02 F7 0C 70 02 77 1D 06 00 6C 02 77 1D FE FF 60 02 57 1D 04 00 00 00 E6 1
7 04 00 C1 15 16
B7 FC
info: putpacket()
01 80
00 C1 61 02 01 CD 55 20 00 5F 10 04 00 40 13 C8 0B A0 00 9F 15 04 00 07 01 96 2
5 CD 35 20 00 F2
03 9F 15 04 00 1C 01 E6 15 08 00 03 0A B0 0A 04 00 F7 09 F6 01 F0 0A 04 00 C3 1
5 04 04 F0 0B 02
00 F7 09 EA 01 03 0A F7 09 F8 01 C3 00 C3 A5 10 00 0F 03 CE 0A EA 02 CD 35 20 0
0 D4 03 D6 0B C0
11 C0 E5 DC 00 C0 65 E7 02 24 88 F5 8A FF FF 47 01 D6 0B F5 0B 08 00 23 03 B7 0
A E0 01 F7 95 0A
30 16
info: putpacket()
01 80
00 CD 01 F7 95 02 00 C6 01 F7 15 03 00 C2 01 F7 09 CE 00 C4 1D 60 FF 03 0A F7 0
9 A6 01 C3 00 C3
A5 10 00 09 02 F7 95 80 00 A5 01 F7 95 01 00 9E 01 F7 09 50 00 F0 01 C3 00 F7 0
9 86 01 1E 01 37
0A 9A 01 F7 95 0A 00 87 01 F7 95 02 00 80 01 F7 15 02 00 7C 01 F7 09 88 00 C4 1
D 1A FF F7 09 5E
01 F7 10 6A 01 C3 A5 01 00 08 02 F7 10 6C 01 F7 09 38 00 F5 8B FF FF 03 02 F1 0
1 F7 09 BA 00 81
D9 11
info: putpacket()
01 80
15 80 15 87 00 F7 09 86 00 F7 09 9E 00 C2 0A C3 1D 3C 01 F7 09 18 01 03 15 F7 0
9 12 01 C2 8A FB
02 C3 1D 36 01 F7 09 06 01 87 00 C2 9D 21 01 C2 45 00 FF 82 0C F7 09 06 01 C2 0
A 06 81 D4 10 F7
60 18 01 77 0B 14 01 F6 01 F7 20 0E 01 08 03 C0 11 C0 E5 CC 01 C0 65 E7 02 24 8
8 F5 8A FF FF 87
00 F7 09 46 00 03 0A C4 11 C4 65 E6 00 03 65 43 0B C2 0A FC 02 F7 10 E2 00 F7 0
9 2E 00 C4 11 C4
2A DF
info: putpacket()
02 0A
40 00 00 00 00 00 00 02 00 00
42 0C
info: read time=1125ms
info: flag=0x02 last=0x02
info: getpacket()
02 0A
02 00 00 00 00 00 00 02 46 00
4A 0C
info: opcode=0x02 length=0x0A
info: read unit=0 sw=0x00 mod=0x00 blk=0x0046 cnt=0x0200
info: putpacket()
01 80
47 00 65 D0 00 03 15 F7 09 A6 00 C2 0A FB 80 87 00 F7 09 18 00 26 11 C3 1D B6 0
0 C2 0A 03 65 43
0B C2 0A FC 02 F7 10 B4 00 84 15 87 00 C2 9D A1 2D 01 00 D6 00 29 02 00 C2 45 0
0 FF 82 0C 82 0A
87 00 C3 A5 02 00 1C 02 C4 10 F7 10 8A 00 C2 15 05 00 C1 11 C1 65 86 00 F7 09 6
C 00 C2 0A 04 81
D1 10 C4 60 44 0B F8 01 C4 20 1B 02 C1 1D 6A 00 C1 45 00 FF C1 A5 40 00 03 02 F
7 0B 64 00 19 03
97 CA
info: putpacket()
01 80
F7 0B 62 00 07 02 C0 11 C0 E5 7A 02 C0 65 E7 02 24 88 0D 01 C0 11 C0 E5 88 02 C
0 65 F0 02 24 88
06 01 C0 11 C0 E5 96 02 C0 65 DA 02 24 88 F5 8A FF FF 87 00 CF 09 CF 09 CF 09 F
0 90 06 00 C3 00
F0 8B 04 00 FD 80 87 00 03 0A CF 09 C8 8B FE 80 03 DC 02 00 C3 00 87 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 3F 20 58 46 52 20 43 4B 20 45 52 52 00 3F 20 52 44 20 4
5 52 52 00 3F 20
CF 24
info: putpacket()
01 80
57 54 20 45 52 52 00 8F 01 00 FD 01 FA 02 37 0A 1E 00 F7 09 1E 00 F5 8B FF FF 0
9 02 42 11 C2 65
DA FF C3 15 12 00 44 10 12 95 C3 0A FD 02 87 00 00 00 00 00 35 8A FF FF F7 0B F
4 FF 03 02 F5 0B
D0 FF 05 02 35 0A D2 FF 35 0A D6 FF 0C 01 C0 11 C0 65 E2 FF 26 12 0F 89 D6 2D D
6 FF 0C 03 75 1D
D8 FF 06 00 03 02 75 1F 10 00 06 00 06 89 C0 11 C0 65 C2 FF 0F 89 44 1D CC FF D
4 0B 03 0A F5 20
F9 FC
info: putpacket()
01 80
D2 FF 04 03 83 0A C4 65 12 00 F9 01 F5 25 1C 00 D2 FF 0A 02 75 1F CC FF 06 00 0
3 02 B5 8A FF FF
23 01 35 0A D2 FF E2 01 B5 0A D6 FF B5 0A D2 FF F7 0B 7C FF 03 03 CC 0B 13 03 E
1 01 CC 0B 06 02
F4 0B 0A 00 DC 02 B5 8A FF FF 0E 01 C2 11 C2 65 6E FC 01 11 15 88 40 11 C0 65 1
4 00 14 88 CF 01
75 1D 06 00 D8 FF 01 11 87 00 44 1D 10 00 F4 0B 16 00 0B 02 35 1D 08 00 06 00 0
6 89 43 1D CC FF
82 DE
info: putpacket()
02 0A
40 00 00 00 00 00 00 02 00 00
42 0C
info: read time=1125ms
info: flag=0x02 last=0x02
info: getpacket()
02 0A
02 00 00 00 00 00 00 02 47 00
4B 0C
info: opcode=0x02 length=0x0A
info: read unit=0 sw=0x00 mod=0x00 blk=0x0047 cnt=0x0200
info: putpacket()
01 80
00 00 F4 1C 04 00 04 00 B4 0A 16 00 87 00 35 8A FF FF 13 89 87 00 40 11 C0 65 D
A FF 41 11 C1 65
14 00 0C 89 B7 0A 0A FF F7 09 0A FF F5 8B FF FF 07 02 35 0A E4 FF 35 0A E8 FF 3
5 0A E6 FF 05 89
87 00 35 8A FF FF 16 89 87 00 35 8A FF FF 09 0A 31 0A 02 00 31 0A 04 00 75 1D D
8 FF 06 00 09 89
F5 8B FF FF 06 02 F1 0B 06 00 02 80 1F 89 01 01 1E 89 87 00 35 8A FF FF 1C 89 3
5 0A CE FF 87 00
2E 2A
info: putpacket()
01 80
35 8A FF FF 41 1D 10 00 40 1D CC FF 0B 89 05 89 04 10 54 1C 0A 00 75 1C 08 00 0
6 00 54 1C 10 00
43 1C 04 00 42 1C 06 00 D4 10 D4 10 83 0A C2 0A FC 02 0A 89 F5 8B FF FF 28 02 0
4 10 35 13 06 00
14 0A D4 15 01 01 54 1C 00 00 D4 15 09 00 0A 89 F5 8B FF FF 1A 02 1B 89 F5 8B F
F FF 16 02 20 89
F5 8B FF FF 12 02 75 1C 0E 00 0E 00 35 0A E8 FF 16 89 75 1C 0A 00 E8 FF 15 89 7
5 1C 04 00 E8 FF
F8 72
info: putpacket()
01 80
75 1C 06 00 0E 00 16 2E 01 00 15 00 F1 04 89 18 89 87 00 35 8A FF FF F7 09 D8 F
E 87 00 2A 01 00
06 00 01 00 F8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
4E 27
info: putpacket()
01 80
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
01 80
info: putpacket()
02 0A
40 00 00 00 00 00 00 02 00 00
42 0C
info: read time=1141ms
info: flag=0x00 last=0x02
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x04 last=0x00
info: <INIT> seen
info: flag=0x04 last=0x04
info: <INIT> seen
info: <INIT><INIT> seen, sending <CONT>
info: flag=0x00 last=0xFF
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x00 last=0x00
info: <NULL> seen
info: flag=0x04 last=0x00
info: <INIT> seen
info: flag=0x04 last=0x04
info: <INIT> seen
info: <INIT><INIT> seen, sending <CONT>
info: flag=0x02 last=0xFF
info: getpacket()
02 0A
02 00 00 00 00 00 00 02 01 00
05 0C
info: opcode=0x02 length=0x0A
info: read unit=0 sw=0x00 mod=0x00 blk=0x0001 cnt=0x0200
info: putpacket()
01 80
02 00 01 00 07 00 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
12 80
info: putpacket()
01 80
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
01 80
info: putpacket()
01 80
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
01 80
info: putpacket()
01 80
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0
0 00 00 00 00 00
01 80
info: putpacket()
02 0A
40 00 00 00 00 00 00 02 00 00
42 0C
info: read time=1140ms
info: flag=0x00 last=0x02
info: <NULL> seen
info: TU58 emulation end

C:\PDP\tu58>

OK, Thats it !!!!!!
THANK YOU Marty
 
RSX11M+ said:
Ok, that's excellent. You indeed have booted XXDP.
Click to expand...

Caution - I do not think that Marty actually BOOTED XXDP from the TU-58 Emulator. In earlier posts, he indicated that he got the file to read in, then he said something about everything halting, then he said he found the code in memory and did a restart.

My only point here is that something went wrong in the boot process. XXDP may be "mostly" there, but having some problem as the result.

Marty, please speak up and correct me if I'm wrong about this.

smp
 
Hi All;
SMP, I Don't know If you are Right or Wrong.. I just don't know enough about everything..
In the posting of Saturaday, I used a different Program.. The Program that I have Loaded today, I got From RSX11M late Saturday and This is the first Time I have tried to load it in the PDP 11/45.. And I thought it might do something different, since when I tried to load a 400K program it didn't stop at '000225.. So I figured 'Why not try it and see what happens, worst case I am back where I was before..'
When I re-started XXDP on the PDP side I did go to 152010, which is part of where the program resides in PDP Memory..
But the BOOt process so far is this -- I put into Core Diane's Bootloader for the TU58, I start up the TU58em with the following script --
TU58em -v -d -T -p 1 -s 9600 -r XXDPP.DSK
I then press the "Start" Button..
After it Loads that program , (I Think) it tries to Run it and it Does, since (I can't say How much of XXDP is Loaded), it does come up with the correct "sign-on" for XXDP..
But before that Sign-on.. The PDP 11/45 stops and shows on the Front Panel lights Address of '000225 and Data of '000226..
I then do a Front Panel Reset and then press the "start" Button and the Loading continues, until I get the XXDP sign-on..
THANK YOU Marty
 
Last edited:
Hi All;
Here is a copy of Diane's Boot Loader --

1000 / 005000 <--- r0 = 0 (bootloader standard)
1002 / 012701 <--- r1 = reciever csr (bootloader standard)
1004 / 176500
1006 / 012702 <--- r2 = transmitter csr (bootloader standard)
1010 / 176504
1012 / 012761 <--- send "init"
1014 / 000004
1016 / 000006
1020 / 005761 <--- wait until sent completely
1022 / 000004
1024 / 001775
1026 / 012761 <--- send "init"
1030 / 000004
1032 / 000006
1034 / 005761 <--- wait until sent completely
1036 / 000004
1040 / 001775
1042 / 012761 <--- send "boot"
1044 / 000010
1046 / 000006
1050 / 005761 <--- wait until sent completely
1052 / 000004
1054 / 001775
1056 / 012761 <--- send 0 (drive no.)
1060 / 000000
1062 / 000006
1064 / 005761 <--- wait until sent completely
1066 / 000004
1070 / 001775
1072 / 105711 <--- wait until reply recieved completely
1074 / 001776
1076 / 116105 <--- ...and flush it (was the "cont" reply)
1100 / 000002
1102 / 005003 <--- r3 = 0 (byte counter)
1104 / 105711 <--- wait until byte recieved completely
1106 / 001776
1110 / 116123 <--- move to memory, increment r3
1112 / 000002
1114 / 022703 <--- r3 = 512?
1116 / 001000
1120 / 001371 <--- if not, continue ...
1122 / 005007 <--- ... else jump to boot block


THANK YOU Marty
 
Just to satisfy myself, I checked the tape image I sent. Here's a screen capture of the CONSOLE terminal TT0: and some commentary.
Code: 
000000 000000 000000 000000
@DD0

CHMDDC0 XXDP+ DD MONITOR
BOOTED VIA UNIT 0
28K UNIBUS SYSTEM

ENTER DATE (DD-MMM-YY):

RESTART ADDR: 152010
THIS IS XXDP+.  TYPE "H" OR "H/L" FOR HELP.

.H
? NOT FOUND: HELP  .TXT
.D

ENTRY# FILNAM.EXT        DATE          LENGTH  START

    1  HSAAD0.SYS       3-MAR-83         24    000050
    2  HUDIB0.SYS       3-MAR-83          5    000100
    3  HDDDC0.SYS       3-MAR-83          3    000105
    4  UPD2  .BIN       3-MAR-83         25    000110
It begins with me starting the system from a Console Emulator ROM. In my system this code is at 165000 and a start address of 165020 is used.

The terminal outputs the customary stuff:
Code: 
000000 000000 000000 000000
@
To this I type the desired boot device: DD0 and hit ENTER. (Yes Marty... at this point DD0 is the correct response) This boot expects to see a TU58 drive connected to the SLU at 176500. In Marty's case, an emulated TU58 on a PC.

Next we see the customary output from an XXDP+ startup.

Code: 
CHMDDC0 XXDP+ DD MONITOR
BOOTED VIA UNIT 0
28K UNIBUS SYSTEM

ENTER DATE (DD-MMM-YY):
No date is entered, but the RETURN key is hit and we get a Restart address and a prompt.

H is the first command entered to XXDP+ - this is intended to see the HELP.TXT file. Apparently I didn't include it in the tape. The last command is D - which begins a Directory listing of the start device (DD0). The capture ends there but the full directory was listed.

Marty's output differs.
 
Ok Marty - I see your post. Did I understand correctly that your have an M9312 in your system with Console Emulator ROMs?

Using the hand input boot code is ok, if that's all we can make work. But I need to understand what's in your system.
 
Hi All;
RSX11M, No, I have Tried the M9312 and I cannot get it to work.. But I have an M9301 YF that is and Does Work.. The M9312 may be Bad or I don't have it set up correctly, I do have the Manual for it and for the M9301..
But, I do have the Console Emulator and it does come up, though it Does Not have DD, it has TT..
I am going to bring up E11 and try and do as you show and see the Output for myself, especially what it is supposed to be..
And of Course Don could still be Right.. I might have a Bad PC IC.. Which Is Why I would like to get this going.. So I don't have to enter it by hand..
THANK YOU Marty
 
Last edited:
I'm torn which way to turn at this moment. Having M9312 and M9301 available makes me think we could go in that direction. Maybe we could try to identify which ROMs are in each. I take it the M9301 is the one with the Console Emulator?... how do you run that, and what does it output please.

The other direction I am tempted to go in - is to supply you with an alternate TU58em that I've found to be more robust before you go disturbing the system any more.

Let's do this... please don't alter the system hardware or configuration. Let's concentrate on things external to it please. Post good pics of the M9312 and 01 and any info you can read printed on the ROMs. We can look at them to see the settings and such - maybe we'll spot something.

I'll get another TU58em for you to try - look for a PM from me. Don't change any system hardware until we see it it makes any difference.

How's that sound?
 
Hi All;
RSX11M, OK by me, I'LL get the things You have asked me for..
At least one of the M9312's have a Console Emulator.. But, NONE of them show up on the system, all the Boards give me an Address Error Led lighting when accessed..
The M9301, is loaded at '173000..
and comes up with the following..

177777 177777 177777 177777
$
I have used the M9301 to Load the Absolute Loader when it gets OverWritten or Currupted.. And it works fine.. Using the TT Bootstrap Command..
THANK YOU Marty
 
Last edited:
Hi All;
Here are the picture of the three boards that I have.. I have three other pictures that will be in the next post, since it won't let me download all six pictures..

02172014007.jpg 02172014008.jpg 02172014009.jpg

THANK YOU Marty
 
If you get the DEC ID numbers off the PROMs in the sockets you can look at this page:

http://www.ak6dn.dyndns.org/PDP-11/M9312/

and cross reference them to which CPU boot PROM the board has, as well as what device boots are supported in the PROMs.

Don

Also the TU58 boot device (765A9) was not commonly used in the M9312, but often seen on the integrated 11/44 card that supported the same boot PROM devices (as 11/44 systems could ship with TU-58 drives integrated in the loboy cabinet).

On my 11/34, I added a second DL11-W at 776500/300 hacked to run up to 19.2Kb (standard max is 9600baud) and added the 765A9 boot prom to the M9312 I have in that system. Works fine with TU58EM either with a direct serial port connection (COM1) or thru a USBserial adapter. Typically I use either an old Dell Latitude Win2K laptop or a desktop WinXPsp3 as the TU58em host.
 
Last edited:
Here's his list Don. I had him working on identifying them offline.

Code: 
M9301:
     480A9
     481A9
     482A9
     483A9

M9312's
     752A9
     758A9
     248F1
     751A9
     233F1
     755A9
     757A9
There are others he can't read the print on.

Soon he will be needing some experience I can't supply... how to run the diags on the tape. Could you work with him on this once we get the TU58 connection solid?
 
RSX11M+ said:
Here's his list Don. I had him working on identifying them offline.

Code: 
M9301:
     480A9
     481A9
     482A9
     483A9

M9312's
     752A9 -- DM RK06/07
     758A9 -- MT TU10
     248F1 -- CPU 11/04-34
     751A9 -- DL RL01
     233F1 -- CPU (?)
     755A9 -- DP RP02/03
     757A9 -- MM TU16
There are others he can't read the print on.

Soon he will be needing some experience I can't supply... how to run the diags on the tape. Could you work with him on this once we get the TU58 connection solid?
Click to expand...

I added the devices supported to the above list.

This is the XXDP user manual (bitsavers): http://bitsavers.trailing-edge.com/pdf/dec/pdp11/xxdp/Turnbull_XXDP_Feb93.pdf

This is the diagnostic user guide (bitsavers): http://bitsavers.trailing-edge.com/pdf/dec/pdp11/xxdp/PDP11_DiagnosticHandbook_1988.pdf

And here are the 11/40-45 diagnostic listings (bitsavers): http://bitsavers.trailing-edge.com/pdf/dec/pdp11/xxdp/diag_listings/1140_45/

The diagnostic listings have a user section at the beginning that indicates any special setup required. Most diagnostics are run with the switch register set to zero, and start at 200(8).

Most of the earlier systems (11/40-45) tended to have a large number of very small diagnostics, since they were typically loaded via paper tape (most systems had a high speed tape reader). XXDP was not even used, diagnostics were run standalone.

Later on (11/04-34-44, etc) there were a smaller number of larger diagnostics, as those were typically loaded via XXDP from disks.

Don
 
Hi All;
Don, Thank You for the Links, I already have them all.. But, Just the same Thank You for Posting them for others..
I have Run the PDP 11/40/45 Diagnostics that I can find in Paper Tape format.. Including about six or so Memory Diagnostics..
The Others that I know of are Only in the PDF links that You show.. And would need to be Re-Entered and re-assembled..
RSX11M, Had me slow down the Baud Rate, which I did and I decided to run things at 1200 Baud.. And so Now it doesn't stop at address '000225, but at address '000010.. So I am going to Bump up the Baud rate and see what that does, to 4800 Baud..
I have set the Baud rate back to 9600.. and try things again..
Also, Don, the proms for the M9312's are from three different Boards.. And the M9312's cause the Address Error Led's to come on, when addressed.. On all three Boards.. But the M9301 Board does work, I would gladly trade One of its proms for a DD program in it instead.. But, I need to read them, and see what they already contain..
THANK YOU Marty
 
Last edited:
You must log in or register to reply here.
Back
Top