• Please review our updated Terms and Rules here

PDP 11/45, Part 2

Hi All;
I read the Printout of the Document that Don posted a link for on TU58 Message Packets..
I think I will investigate the Vector part of the System and see if it is working, and as a part of this try to find where the NULLS are coming from..
I know Nothing about either.. I don't know what purpose the Vectors serve, nor what Board they come or go to, to or from.. I will need to find some Documents about what they are for..
THANK YOU Marty
 
Marty said:
Don has mentioned numerous times about my Unit Sending "NULLS" and no one knows where they are coming from, (not that I expect anyone to know) or why or how they got created..

Once I find where the NULLS are coming from, them I can find out how to get rid of them..
Click to expand...

Marty,

You have an oscilloscope, and you have a logic analyzer. If you attach one or both to the output of your serial I/O you can see if it is continuously putting out nulls.

Like I said, please pay attention to what Don is asking about. Perhaps you have a problem with your vector, but that is another different thing. Don't try to be addressing everything all at the same time. Let's just concentrate on getting your connection between the PDP-11 and the TU-58 emulator stable first, and then move to the next possible issue.

smp
 
Hi All;
SMP, """You have an oscilloscope, and you have a logic analyzer. If you attach one or both to the output of your serial I/O you can see if it is continuously putting out nulls."""
I already knew this, and that is exactly what I planned on doing..

"""" Like I said, please pay attention to what Don is asking about. Perhaps you have a problem with your vector, but that is another different thing. Don't try to be addressing everything all at the same time. Let's just concentrate on getting your connection between the PDP-11 and the TU-58 emulator stable first, and then move to the next possible issue. """"
You mention to pay attention to what Don is saying, I agree, and You say that my vectors are a different thing, I don't know this.. My thinking is that they might be related, that my vector problem may be why its putting out the Nulls.. And / or the PDP 11/45 has to somehow know that the information is being sent to it and if the Vectors are messed up, then it might be that when a vector is active like if the signal is between two states and so that it messes up the timing between the serial TU58 and the PDP 11/45..
I can send and receive signals to and from the Serial ports without the Vectors, but both boards have and I assume use those Vectors for something.. Which might have ALL to do with the Vectors, that is what I need to find out and that is exactly what I need to find out, where the Nulls are coming from or what is creating them.. They are not just showing up out of thin air all by themselves, something is creating or causing them to be created..
Like I said earlier, I can look with my scope first at the Output from the RX and TX on the TU58 Serial port.. I can also look to see if for instance that an "A", is actually sending what is needed to send an "A", and not any extra bits..
Then I can look at the Vectors and see if they are being used at all.. If they are Not being used, then for now I can put that to rest..
But if during the different transfers I see vector Activity, then that needs to be looked into..

THANK YOU Marty
 
Hi All;
I have cleaned the Dec Block contacts and the one that was the worst was Slot 8 the D, E and F sections, Most of them were pretty clean over all..
Now that I know where the Vector(s) connect it will be an easy thing, to see IF the two that are used by the TU58 Serial Card M7856, are working correctly.. Then that issue can be Put to Rest..

THANK YOU Marty
 
Last edited:
Hi All;
I asked Tradde what His Switch settings were on the M7856 Switch 4.. Since I had them all OFF..
He sent me the Switch settings He had, which were different than what I had implemented..
The only one that I needed to change from His settings was He had two Stop bits and I tried that and it didn't Work.. But, when I changed it Back to 1 Stop Bit.. And them tried it..


IT WORKED I HAVE SUCCESSFULLY BOOTED FROM THE TU58 EMULATOR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

No One Told me, Nor said anything about having switch 4 position 1 and 7 ON !!!!
And that is what made the Difference..

177777 177777 057774 177777
@DD)
@DD0
177777 177777 177777 177777
@DD0

MEMORY MANAGEMENT UNIT NOT FOUND



BOOTING UP XXDP-SM SMALL MONITOR


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

RESTART ADDRESS: 072010
TYPE "H" FOR HELP

.

!!!!!!!!!!!!!!!!!! (And Here is the Rest of the Story) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.H

HELP for XXDP V2 HELP.TXT Rev: 6.0
________________________________________________________________________________

LIST>

-- The commands outlined here are for XXDP V2 only!


LP: = line printer
TT: = Console terminal
SM: = Small monitor
XM: = Extended monitor

HELP is available on the following topics:

BOOT BOOTSM CHAIN CLEAR COPY DATE DEFSM
DEFXM DELETE DIRECTORY ENABLE HELP INFONBOOT INITIALIZE
LOAD NOTES PRINT RENAME RUN SET START
SMALLMON SWITCHES TYPE UPDAT V2.4 VERSION



________________________________________________________________________________

INFONBOOT>

-- XXDP V2 can boot two monitors (XXDPSM or XXDPXM). The "SM" or Small
monitor is for systems that are 28k or smaller in size, the "XM" or
Extended monitor is for systems larger than 28k. The "SM" monitor
works like the monitor of XXDP+ V1 and will run all programs written
for V1. The "XM" monitor offers the new features advertised in XXDP V2.
By default you will boot up the "XM" monitor provided the system has
enough memory and memory management capability.

Start-up file BOOT.CCC
-----------------------
At boot time, a start-up file BOOT.CCC will be executed as a chain file.
If this file does not exist, there will be no warning message, boot will
continue and by default the "XM" monitor will be booted up. If the file
exists, it must contain one of the two commands listed below. Only one
of the two commands may be used at a time and it should be on the first
line of the file with no leading spaces. If the file does not contain one
of the two commands it will boot up the "XM" monitor. Note, if the system
does not have more than 28K worth of memory or memory management capability
the "SM" monitor will be booted up.

SM - Boots the "SM" monitor.

QUIET - Boots "XM" monitor in UFD mode. (SYSTEM.CCC must exist)

________________________________________________________________________________

SMALLMON>

SMALL MONITOR (XXDPSM)
-----------------------

The following are legal commands : (format of each command is shown)

-------------------------------------------------------------
C - run a batch job (chain)

C filename.CCC[/switches]
------------------------------------------------------------
D - list directory of load medium

D[/L][/F] "/L" switch = on a LP:
"/F" switch = in a short form.
-------------------------------------------------------------
DAte - inspect or set the current system date.

(For more information see "HELP DATE")
------------------------------------------------------------
E - enable alternative drive for system device

E n where n is the new drive number
------------------------------------------------------------
H - type help information about XXDP V2

H[/L] "/L" = print on a LP:
------------------------------------------------------------
L - load a program

L filename[.ext]

Example:
.L DIAG (load DIAG.BI?)
.L ZDJCA2.NEW (load ZDJCA2.NEW)
------------------------------------------------------------
R - run a program

R filename[.ext] [addr]
------------------------------------------------------------
S - start a program

S [addr]
------------------------------------------------------------
VT - toggles the console terminal type between video and hard copy
(The default terminal type is hard copy)

________________________________________________________________________________

EXTENDED_MON>

EXTENDED MONITOR (XXDPXM)
-------------------------

The following are legal commands : (format for each command is shown)

(Letters shown in upper case are required to make a command unique)

________________________________________________________________________________

BOOT>

Boot - directs monitor to boot another XXDP device

Boot dev:

________________________________________________________________________________

BOOTSM>

BOOTSm - directs monitor to boot up the small monitor.

BOOTSM

________________________________________________________________________________

COPY>

COpy - transfer files and maintenance operations

COpy[/BOOT ] input-filespec output-filespec
[/FILES ]
[/DEVICE ]
[/DELETE ]

Examples:
.COPY A.BIN DY0: (Copy A.BIN from system device to DY0:)
.COPY/BOOT DM0: DM1: (Copy monitor from DM0: to DM1:)
.COPY/FILES DL0: DL1: (Copy all files from DL0: to DL1:)
.COPY/DEVICE DY0: DY1: (Copy device image from DY0: to DY1:)

________________________________________________________________________________

CHAIN>

Chain - execute a batch, or chain file. The file must be a .CCC

CHAIN filespec[/switches]

________________________________________________________________________________

CLEAR>

CLear - Clears the SM and XM flags. When these flags are cleared
they allow the monitor to check bit 12 of location 52
before running any program. If bit 12 is set the program
will be run under the extended monitor. If bit 12 is not
set then the program will be run under the small monitor.

Note :- On boot up (by default) these flags are cleared
and can be set by issuing the DEFSM or DEFXM command only.

________________________________________________________________________________

DATE>

DATE - inspect or to set the current system date

DATE dd-mmm-yy (Default dates are 01-JAN-84 for SM)
( 01-JAN-87 for XM)
where
dd = day (a decimal number from 1 to 31)
mmm = month, first three characters
yy = year (a decimal number from 83 to 99)

Example (setting date):
.DATE 18-MAY-83

Example (obtaining date):
.DATE
18-MAY-83

________________________________________________________________________________

DELETE>

DElete - deletes the file(s) that are specified.

DElete[/NOREWIND] filespec
[/NONAMES ]
Example:
.DELETE DU0:ABC.BIN
.DELETE/NONAMES DU0:ABC?.BIN (No file names will print)
.DELETE/NOREWIND MU0:*.TXT (No tape rewind between files)

________________________________________________________________________________

DIRECTORY>

Directory - list all files on a XXDP device.

DIRECTORY[/PRINTER]
[/FAST]

where
/PRINTER = print on LP:
/FAST = show in short form

________________________________________________________________________________

ENABLE>

Enable - enable alternative drive for system device

E n where n is the new drive number

________________________________________________________________________________

HELP>

Help - types HELP.TXT which contains help on XXDP V2

H[/PRINTER]

Help = Displays topic list
Help ? = Displays topic list
Help * = Displays help on all Topics
Help Topic = Displays help on that Topic
Help To* = Displays help on all topics
starting with the letters "To"


Note : To exit help, simply type in EXit or a carriage return.

________________________________________________________________________________

INITIALIZE>

INItialize - initialize device directory into XXDP format.

INITIALIZE device: CAUTION: All data on device
is lost!

________________________________________________________________________________

LOAD>

Load - load a file into memory

LOAD filespec

Example:
.LOAD ZKXCA0.BIC (load DIAG.BI?)


NOTE: This command is used to load programs whose extensions
are (.BIC, .BIN or .SYS) only.
________________________________________________________________________________

PRINT>

Print - Print contents of files on the specified device on LP:

PRINT[/NOREWIND] filespec

Example:
.PRINT DY0:SYSTEM.CCC
.PRINT/NOREWIND MS1:*.TXT

________________________________________________________________________________

RENAME>

REname - change the file specification of an existing file

RENAME input-filespec output-filespec

Example:
.RENAME DX1:DIAG.OLD=DX1:DIAG.BIN

________________________________________________________________________________

RUN>

Run - load and start a program that is stored on system device.

RUN filespec [addr]

Examples:
.RUN UPD2 (load/start UPD2.BIN)
.RUN SAMPLE.XXX (load/start SAMPLE.XXX)
.RUN FXDIAG 204 (load/start FXDIAG.BI? at location 204)

________________________________________________________________________________

SET>

Set - changes device characteristics and system parameters.

SET [ device ]:condition
[ item ]

where "device" = device whose characteristics are modified.
"item" = system parameter that needs to be modified.

Examples:
.SET TT:SCOPE (RUBOUT will delete characters - XM Default
is SCOPE)
.SET TT:NOSCOPE (RUBOUT will echo deleted characters -
SM Default is NOSCOPE)
.SET TT:QUIET (Prevent system from echoing lines from a
chain file or from diagnostics that are
running from a chain file)
(Default = NOQUIET)

________________________________________________________________________________

DEFSM>

DEFSm - Sets the SM flag. After issuing this command all programs
will be run under the small monitor until the CLEAR
command is issued. Bit 12 of location 52 will not be
checked at all and by default any program(s) run after
this command is issued will be run under SM.

Note of caution :- If you plan to run only one program
under SM and issue this command make sure you issue the
"CLEAR" command after your program has completed running.
Else by default every program will run under SM regardless
of whether bit 12 was set or not.

________________________________________________________________________________

DEFXM>

DEFXm - Sets the XM flag. After issuing this command all programs
will be run under the extended monitor until the CLEAR
command is issued. Bit 12 of location 52 will not be
checked at all and by default any program(s) run after
this command is issued will be run under XM.

Note of caution :- If you plan to run only one program
under XM and issue this command make sure you issue the
"CLEAR" command after your program has completed running.
Else by default every program will run under XM regardless
of whether bit 12 was set or not.

________________________________________________________________________________

START>

Start - start a file that has been loaded into memory via LOAD

START [addr] A starting address may be entered

________________________________________________________________________________

TYPE>

Type - prints the contents of a file on the terminal

TYPE[/NOREWIND] filespec

Example:
.TYPE/NOREWIND *.TXT

________________________________________________________________________________

VERSION>

Version - Prints information about the Extended monitor.

Version

________________________________________________________________________________

V2.4>

There are some major differences in V2.4 and all of the previously
released versions of XXDP V2. The main difference is the way programs
will be run from now on.

In previous versions, programs were run under the same monitor that
was displayed on boot up. i.e. if you booted the small monitor you
ran all your programs under the small monitor. If you booted the
extended monitor you ran all programs under the extended monitor.
The problem with this was that you would have to reboot the other
monitor if you had a program that ran on one and did not run on
the other.

In V2.4 (and following versions), this problem is solved, programs
will be run after a check is made on bit 12 location 52 (after the
program has been loaded) and if this bit is set the program will be
run under the extended monitor. If this bit is not set, the program
will run under the small monitor. Unlike the previous versions there
will be no need to reboot.

Bit 12 of location 52 should be set by using the "UPDAT" or "PATCH"
utility. If UPDAT is used you might have to change the LOCORE of your
program. Please sure the "CLR" command is issued before loading the
program and changing the locore.

Note : Look at the "DEFSM", "DEFXM" and the "CLEAR" commands in this
help file if you are unable to set bit 12 by using the utilities.

________________________________________________________________________________

SWITCHES>

Switches - are not applicable to all commands
- these switches are not system defaults
/PRINTER = print on LP:
/NONAMES = No file names will be shown
/NOREWIND = prevents tape rewinding between files

________________________________________________________________________________

UPDAT>

UPDAT program
--------------
This program uses the same commands as UPD2. Commands SAVM and SAVE are
no longer supported. The following command has been added to build
bootable media. It will work with tapes or disks.

CREATE DY0: (will create a bootable DY from your system media)

________________________________________________________________________________

NOTES>

CAUTION : Do NOT use XXDP+ V1 to write to XXDP V2 media.
XXDP V2 may read or write to XXDP+ V1.

NOTE : The monitor only sizes to 124k words.

* For a detailed description of these commands see XXDP/DRS User Manual

________________________________________________________________________________

.D

ENTRY# FILNAM.EXT DATE LENGTH START VERSION

1 XXDPSM.SYS 1-MAR-89 29 000047 E.0
2 XXDPXM.SYS 1-MAR-89 39 000104 F.0
3 DRSSM .SYS 1-MAR-89 24 000153 G.2
4 DRSXM .SYS 1-MAR-89 48 000203 C.0
5 DATE .SYS 1-MAR-89 2 000263 B.0
6 DB .SYS 1-MAR-89 2 000265 C.0
7 DD .SYS 1-MAR-89 3 000267 D.0
8 DIR .SYS 1-MAR-89 7 000272 D.0
9 DL .SYS 1-MAR-89 4 000301 D.0
10 DM .SYS 1-MAR-89 4 000305 C.0
11 DR .SYS 1-MAR-89 3 000311 C.0
12 DU .SYS 1-MAR-89 4 000314 E.0
13 DUSZ .SYS 1-MAR-89 2 000320 C.0
14 DY .SYS 1-MAR-89 3 000322 D.0
15 LP .SYS 1-MAR-89 1 000325 B.0
16 MM .SYS 1-MAR-89 3 000326 C.0
17 MS .SYS 1-MAR-89 4 000331 C.0
18 MU .SYS 1-MAR-89 4 000335 E.0
19 HELP .TXT 1-MAR-89 29 000341
20 PATCH .BIC 1-MAR-89 31 000376
21 SETUP .BIC 1-MAR-89 27 000435
22 UPDAT .BIC 1-MAR-89 29 000470
23 XTECO .BIC 1-MAR-89 26 000525

.

THANK YOU, TRADDE and DON and RSX11M and SMP for all of Your Help and Suggestions..
THANK YOU Marty
 
Last edited:
Hi All;
I was beginning to Think it was going to be Part 3, with "No" end in sight..
Its amazing what You don't know that you don't know..
THANK YOU Marty
 
Might be time to revert to that other TU58 tape image (the one I sent you) to run some more diags?
 
Hi All;
RSX11M, Thank You, Now I need to find what I did with it, But compared to all the trouble I have been thru for the last couple of weeks.. This should be Easy to find.. Found it, But First, I am going to work on getting another 16K going..
Thank You for All You have Done and Did for me..
THANK YOU Marty
 
Last edited:
Hi All;
Thank You Jack..

I think we'll all sleep easier tonight!

Me too.. That's after my Roommate Peels Me off of the Ceiling..

Right Now I am Testing my 2nd Core Stack, with Don's ZZ program.. Tomorrow the 3rd Core stack and then the Fourth stack.. Then on to the G114's and then the G235's..

02252014019.jpg 02252014020.jpg

THANK YOU Marty
 
Last edited:
Marty said:
IT WORKED I HAVE SUCCESSFULLY BOOTED FROM THE TU58 EMULATOR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...

Congratulations, Marty! Finally a payoff after all the effort you put in. It must really be a great feeling.

I hope your continuing effort also brings more successes in the (near) future.

smp
 
Hi All;
Could SomeOne who has the access to change my "Title" from PDP-11/45,Part two... To PDP-11/45, Part two, IT WORKS !!
Notice besides that adding "it works !!" I have also added a "space" after the first comma and before "Part two" ...
THANK YOU Marty
 
Hi All;
I have checked out all four of the Core Stacks themselves and they all check out, Not only did I run them with Don's ZZ program, but I also boot from the TU58 emulator as well..

Don, your three programs that I have all Load and Run just fine..

RSX11M, of the two Files that I got from You, not so good.. The file xxdpd2d, Boots and Runs just fine.. The file xxdpddd Loads, but will not Run.. It stops at Address '000010.. Just like before.. I have not yet tried Reloading the program and seeing if it will run..

THANK YOU Marty
 
You must log in or register to reply here.
Back
Top