I'm trying to get some assembly code to run on my 11/23 by entering it in
at the ODT, and it seems like I'm having trouble with device I/O
addresses.
All I've got in the machine right now is the CPU card, an M8044 with 32kW
at address 0, and the DLV-11J, set up so that port 3 works with ODT as a
console port.
I've got a DLV11-J set up so that port 3 is the console, and I can
interact with ODT just fine. However, when I try entering something that
should read or write to the console, nothing happens.
Below is a listing of the assembled code I'm trying - I got the I/O
address out of a PDP-11 assembly programming book I got from the library.
Most likely the book was written with a UNIBUS -11 in mind, not a QBUS
one... is that a problem?
1 000000 LC=.
2 001000 .=LC+1000
3
4 177564 XSR=177564
5 177566 XBUF=177566
6
7 001000 012767 000110 177566' MOV #110,XBUF
8 001006 105767 177564' L1: TSTB XSR
9 001012 100375 BPL L1
10 001014 012767 000064 177566' MOV #64,XBUF
11 001022 105767 177564' L2: TSTB XSR
12 001026 100375 BPL L2
13 001030 012767 000130 177566' MOV #130,XBUF
14 001036 105767 177564' L3: TSTB XSR
15 001042 100375 BPL L3
16 001044 012767 000060 177566' MOV #60,XBUF
17 001052 105767 177564' L4: TSTB XSR
18 001056 100375 BPL L4
19 001060 012767 000122 177566' MOV #122,XBUF
20 001066 105767 177564' L5: TSTB XSR
21 001072 100375 BPL L5
22 001074 000005 RESET
23 001076 000000 HALT
-- Pat
http://www.floodgap.com/cbm-enet.jpg
'Nuff said. The device is a Lantronix UDS-10 in modem mode, allowing the
SX to open TCP connections using Hayes-like commands over the local Ethernet
network. Here, it's browsing the apartment network using HyperLink 2.5:
http://www.armory.com/%7Espectre/cwi/hl/
The picture the SX-64 is viewing has been slightly blurred to protect the
innocent/unwitting. :-)
By the way, I see no reason why Apples, Ataris, TIs, etc., can't all be
using these things too. The only problem is they're not terribly cheap (mine
was a little over $100).
--
----------------------------- personal page: http://www.armory.com/~spectre/ --
Cameron Kaiser, Point Loma Nazarene University * ckaiser(a)stockholm.ptloma.edu
-- Why did the chicken cross the Moebius strip? To get to the other ... uh ...
Some time ago I saw someone on the list interested in the above . . . .
well I found these at my gold mine in Topeka and had to bring them home
. . . !!!
I've yet to try them out, but if they are working, I'm willing to part
with them for a few bucks, for all those Amigaphile wannabes out there.
I have nine Amigas already and it is getting hard to navigate around the
house.
Reply off-list and we'll go from there.
Gary Hildebrand
St. Joseph, MO
On Sep 15, 0:46, Patrick Finnegan wrote:
> I've got a PDP-11/23 cpu, M8044 32kW memory card, DLV11-J serial card,
and
> an RQDX1 set up, and starting up into ODT. I've got an ST225 'MFM'
> interface drive and an RX50 I'd like to hook up, but no cab kit for the
> RQDX1.
>
> Four questions:
>
> 1a) Does anyone have a pinout for a cable that'll let me hook up the RX50
> and MFM drive to the RQDX1
I have two documents that might help. Years ago, I made two (different)
"distribution boards" so I could use my RQDX1 and RQDX3 on machines that
didn't have the proper DEC board. One was no more than a small (2" x 4")
perfboard with a 50-way connector for the cable to the RQDX1, a 34-way
header for the RX50, and another 34-way, with adjacent 20-way headers, for
one or two RDxx drives (actually I used either a Rodime or a Seagate). It
also had a terminator pack (7-resistor SIL pack) and a set of jumper pins
to take the place of the panel pushbuttons. The interconnections were just
hand-soldered, using wire-wrap wire.
However, I also made a PCB which does the job more neatly, and which I
mounted inside an old TK50Z box (is that a "leprechaun box"?), along with
the original PSU, an RX50 (where the TK50 used to be) and a Rodime 10MB
drive. It's still in use today (literally today, as I'm using it to copy
some RT-11 stuff for someone).
I've put the document I wrote (in PostScript format) listing the RQDX
distribution board connections and signals, along with some notes about
using random floppy drives, on my web site. It's not just a list of
signals and pin numbers; it also describes what they actually do. I've
also put the layout for the distribution board PCB up there.
http://www.dunnington.u-net.com/public/RQDX/
I once traced out the connections and drew the circuit diagram of a real
M9058 distribution board (which is what my PCB emulates) but I can't find
the document. Sorry! However, I do remember that it's very simple.
> 1b) What DIP switch settings should I use on the RQDX1?
Well, that's easy, because it has no switches :-)
If you mean the jumpers, they're set as follows:
There's a group of jumpers to set the starting LUN (Logical Unit Number) of
the RQDX1, at the back edge on the right (top left if you're looking at a
board from above, with the contact fingers downwards and the LEDs and
connector at the top). The jumper positions are labelled 0 to 7, and
represent powers of two, so no jumpers at all sets "0", a jumper on the
first position ('0') sets "1", a jumper on the second and third positions
sets "6", etc. If this is the first or only MSCP disk controller in the
system, set LUN 0 (which means it controls drive units 0-3, ie four LUNs
starting at 0) ie remove all the jumpers.
Another set of jumpers, near the "Row B" contact fingers, sets the
addresses of the IP and SA registers, by setting A2...A12. The A2 jumper
position is nearest the "Row A" fingers and the A12 position is near the
"Row C" fingers. Jumper IN is a '1', no jumper is a '0'. A0 and A1 are
always zero, and the higher bits are controlled by BBS7 so there are no
jumpers for those bits.
The standard address is 17772150, set by jumpering A3, A5, A6, A10, A12.
The interrupt vector is set by software as part of the bootstrap; it's
usually 154 for the first MSCP device.
Finally, there are four wire links, W1/W2 near the "Row C" fingers and
W3/W4 near the centre of the board. Actually, they're usually zero-ohm
resistors. W1 and W2 are for grant continuity, they are IN for use in Q/Q
or Q22/Q22 (serpentine) backplanes and OUT (removed) for use in Q/CD or
Q22/C (straight) backplanes. I don't know what W3 and W4 do, but they're
IN on mine.
> 1c) Does someone have a bootstrap I can enter using ODT to boot RT-11 off
> of an RX50 or the hard drive on the RQDX1?
That's harder. The way MSCP works, by setting up message blocks and
passing them to the controller, makes it a bit complicated, and I've never
seen a stand-alone bootstrap. The easiest way might be to get the boot
code off an Emulex controller to disassemble, as at least that wouldn't
have all the overhead of dialogs and options for other devices which the
DEC boot ROMs have.
--
Pete Peter Turnbull
Network Manager
University of York
If I am not for myself, then who will be for me?
And if not now, when?
-- Pirkei Avot
----------
> From: Patrick Finnegan <pat(a)purdueriots.com>
> To: cctalk(a)classiccmp.org
> Subject: osborne executive disks
> Date: Saturday, August 10, 2002 10:07 PM
>
> Does anyone have some (preferally images of) Osborne Executive CP/M
disks?
> Also, what format does it use, and is it possible to use an Osborne 1
boot
> disk to boot an Exec?
>
> Thanks for the help
>
> -- Pat
>
>From: "Dwight K. Elvey" <dwightk.elvey(a)amd.com>
>
>Hi Chris
> I spent quite a bit of time looking at the stuff from
>the web site on the CPM-8000. It looks like the CPM.SYS
>in the cpm8k11 stuff is built specifically for the
>M20. It was made with the symbol table so I was able
>to find the various tables.
---snip---
Hi
Sorry about that, this was intended for Chris only
but if there is anyone else interested in getting the
CP/M-8000 up and running, let me know. It may be easy
but one can never tell. I'm not much of a C expert.
I wish they'd just done it in assembly. Proper
used of macros would have made the job easy enough.
My main complaint is that it requires either a
PDP-11 with their compiler or a working CP/M-8000.
Of course, that is what I'm trying to create. Writing
an assembler is relatively trivial while writing
a C compiler is a bit more. There are several M***
assemblers that one could easily adapt to the 8000
out there as well ( I do tend to write my own though ).
The stuff from the web site looks like one may
be able to build a booting disk. I'll be working on
that, over the next few days.
Dwight
Hi Chris
I spent quite a bit of time looking at the stuff from
the web site on the CPM-8000. It looks like the CPM.SYS
in the cpm8k11 stuff is built specifically for the
M20. It was made with the symbol table so I was able
to find the various tables.
I don't think the fellow that did this implementation
really had a solid grasp of a boot process but what they
have done should work. There is no reason why what they
call CPMLDR.SYS couldn't have been a slightly modified
CPM.SYS with a simple loader added ( like more traditional
CPM's ).
If you look, you'll see that in one place ( I forget where ),
they have a compiler flag called TRANSFER. It would seem that
they had, in fact, connected a 8 inch drive to a system as the
next drive after the hard drive. They used this as a transfer
system.
The disk, that the .img files were from, was built as
though it were for this setup. It was not a bootable
disk. There is quite a bit of information on building
a boot disk in the various files that contain the tables
T0S0, T1S0 and T1S1. These are the main information
involved in creating a boot disk. My understanding of
T0S0 leads me to think that the one they have is not
correct but may have still worked. I believe we can
continue to just use the unaltered T0S0 that is on the
disk, formatted by the M20. We can just build the bootable
image on one of these disk. We don't need to get too carried
away. Once we've built a disk that boots, we can add
one file at a time to a different disk and transfer them
using the second drive. This way, we only have to deal
with the directory on the CPM for one file at a time.
This simplifies transfers but may take a little extra time.
Still, we wouldn't have to deal all that much with disk
space allocation.
I'm going to fiddle with trying to build up an image
but I'll only be able to do this in the evenings this week.
Next weekend I'll be off visiting relatives.
I converted another RAM board to 128K. It now boots to
384K :) It was one of the two B/W memory boards that
I have. It wasn't as simple as I thought. Changing pin 8
>from +12V to +5V was just a simple jumper change but
Pin 9 had connections inside to an internal power plane.
This time, rather than lifting a pin on the chips, I
lifted one of the socket pins. I used a little quick setting
epoxy to insulate the board pin 9 from the socket pin
that I bent out to the side. On these boards, there was
at least, a nice jumper hole to connect this additional
wire to ( it even looks like they had intended it to
be jumper configured but the internal plane connections
kept one from doing that ). It took me about 4 hours
to do one board. I could have done it faster if I didn't
want to save the IC's. Just clipping the IC out and
pulling the pins is a lot faster than removing the entire
IC, intact. It is a lot safer for the board but I
just can destroy working chips.
Anyway, do you know of any issues that I should look out
for in creating a boot disk from these files? I haven't
seen anything that looks like a show stopper.
Dwight
>Thanks to some help from Bob I got past the HP 2117F power supply issue so
>now the box is not totally dead. Some day after I figure out a lot more
>about how this system works I'll have to try building an HPIB cable to
>connect to the 12821A disc interface in the system and see if I can get it
>to talk to one of my CS/80 drives. Apparently this box has a CS/80 boot
>prom which I have been told is not too common.
I have a machine with the CS80 boot ROMs but have been unable to dup them.
One of the problems that we've had is finding a burner to dup the ROMs. Bob
Shannon had tried a number of times but still can't get his copies to work.
So... This weekend I wnet to the Melbourne Hamfest and stumbled across an
old programmer that is supposed to burn Harris 7611's. Now If I can just get
Bob to send some of those chips back to me, maybe I can make dups.
See ya,
SteveRob
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
Would anyone have an extra power plug they could sell me for my generic S-100
computer? Somehow mine must have gotten given away with other misc. cords.
It's the kind with two sort of oval female prong inputs on the computer end.
Anyway, I'd be happy to furnish a picture to anyone who needs to verify. I
haven't had it up and running for a couple of years now, and I would like to.
I'm really hoping to make it for the first time to the VCF West this year!
Thanks very much, David
David Greelish
Classic Computing
www.classiccomputing.com
"classiccomputing" on eBay
Thanks for the offer, but I didn't mean a standard HPIB-HPIB cable. The
12821A disc interface has a 50 conductor edge connector instead of a
standard HPIB champ connector. I think the HP part number for the edge
connector to HPIB champ connector cable is 59310-60008. If that was really
the cable you were talking about then maybe I will take you up on your
offer.
-Glen
>From: Joe <rigdonj(a)cfl.rr.com>
>Reply-To: cctalk(a)classiccmp.org
>To: cctalk(a)classiccmp.org
>Subject: Re: HP CS/80 Instruction Set Programmers Manual (5955-3442)
>Date: Fri, 13 Sep 2002 23:10:10
>
>Glen,
>
> Don't bother to build a HP-IB cable. They're common. If you can't find
>one locally I'll drop one in the mail to you.
>
> Joe
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com