26 Mar
2014
26 Mar
'14
8:40 a.m.
On 03/26/2014 08:40 AM, cctalk-request at classiccmp.org wrote:
Message: 15
Date: Tue, 25 Mar 2014 20:19:17 -0400
From: Jonathan Katz<jon at jonworld.com>
To: "General Discussion: On-Topic and Off-Topic Posts"
<cctalk at classiccmp.org>
Subject: uVAX2 Help
Message-ID:
<CAEOZr+0byXEZ5TG=nEvnBMDXTGELb+3GewkZVjEHrizBbdi=3A at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
All,
I've added a VCB02 card to my MicroVax 2. Right now the VAX is setup with
the following layout...
Slot 1 KA630-A CPU M7606AF
Slot 2 8M RAM M7609-AM
Slot 3 8M RAM M7609-AP
Slot 4 CMD SCSI MSCP encapsulating (top half) empty bottom
Slot 5 M7516-YM (ethernet, top) M7546 for TK-50 (bottom)
Slot 6 VCB02
Slot 7 VCB02 Memory
Slot 8 VCB02 Memory
Per the docs on bitsavers, the VCB02 can go in any QBUS slot 5-8, but the
layouts in the manual are different than what I have setup.
With the VCB02 in there POST takes longer, but the console still comes out
on the serial port. The VCB02 shows 3 red LEDs.
I assume I need to set the addressing on the card, but I have 0 clue what
to do.
OK, when you boot, you get no display on the screen?
That means the boot ROMs in your CPU board don't have
VCB-02 support in them. (Same as mine.)
My notes show the device address was set to 777402
(Gee, that looks like an octal address. So much I've
forgotten about VAX stuff...)
I think the 3 LEDs come on at power up, and then go off
in a quick sequence when the device driver configures
it.
Is this a VMS or Unix-derived system? I know VMS
4.7 had the drivers for the QDSS (VCB-02), but if you
are using an older OS, not sure.
As the boot ROMs don't support the frame buffer, you
should not expect any display until the OS is up.
Other than making sure the I/O address was set to
a value so that the driver enumeration could identify
the board, I did nothing special to configure it.
Jon
26 Mar
26 Mar
9:29 a.m.
On Wed, Mar 26, 2014 at 8:40 AM, Jon Elson <elson at pico-systems.com> wrote:
OK, when you boot, you get no display on the screen?
That means the boot ROMs in your CPU board don't have
VCB-02 support in them. (Same as mine.)
What firmware do you have on your M7606 KA630? I have 23-110E6 /
23-111E6 firmware on mine and I think with that I got the console to
appear on the VCB02, but it has been a while since I have tried that.
I currently have an M7625 KA655 in my BA123 with the VCB02 instead of
the M7606 KA630.
I never changed the address switches on my VCB02. I don't think there
was ever any reason to do that unless you had more than one VCB02 in a
system, which was probably a rare configuration. The manual says that
only a VCB02 assigned to the first address (Q-Bus I/O page base +
1F00h) would be configured as the console device. On my M7169 switches
1,2,3 are set to the CLOSED / ON position. Switch 4 is unused.
9:37 a.m.
On Wed, Mar 26, 2014 at 12:29 PM, Glen Slick <glen.slick at gmail.com> wrote:
What firmware do you have on your M7606 KA630? I have
23-110E6 /
23-111E6 firmware on mine and I think with that I got the console to
appear on the VCB02, but it has been a while since I have tried that.
I currently have an M7625 KA655 in my BA123 with the VCB02 instead of
the M7606 KA630.
I'm not sure; it echoes "KA630-A.V1.3" out the console port.
27 Mar
27 Mar
5:46 a.m.
On 03/26/2014 12:37 PM, Jonathan Katz wrote:
On Wed, Mar 26, 2014 at 12:29 PM, Glen Slick
<glen.slick at gmail.com> wrote:
That's good enough to run as uVAXII. unlike the uVAX2000 ther ereally was
only one firmware for the KA630 CPU (others were bugfixed).
Allison
We shall see how much spam todays posting brings.
What firmware do you have on your M7606 KA630? I
have 23-110E6 /
23-111E6 firmware on mine and I think with that I got the console to
appear on the VCB02, but it has been a while since I have tried that.
I currently have an M7625 KA655 in my BA123 with the VCB02 instead of
the M7606 KA630.
I'm not sure; it echoes "KA630-A.V1.3" out the console port.
26 Mar
26 Mar
9:31 a.m.
On Wed, Mar 26, 2014 at 11:40 AM, Jon Elson <elson at pico-systems.com> wrote:
OK, when you boot, you get no display on the screen?
That means the boot ROMs in your CPU board don't have
VCB-02 support in them. (Same as mine.)
My notes show the device address was set to 777402
(Gee, that looks like an octal address. So much I've
forgotten about VAX stuff...)
I think the 3 LEDs come on at power up, and then go off
in a quick sequence when the device driver configures
it.
Is this a VMS or Unix-derived system? I know VMS
4.7 had the drivers for the QDSS (VCB-02), but if you
are using an older OS, not sure.
The goal is to have something Unix-based on there.
I did take out the TK-50 controller (not using it) and consolidated down
the ethernet card to be the bottom, below the SCSI, and shifted the VCB02
setup one to the right (moving everything a slot down.) ... the difference
is that I can type in commands and hear the "chirp" from the keyboard and I
can't type, only display output on the serial console. So I guess I'm
having some progress.
I think I'll take the VCB02 out, get the OS and everything working via
serial console first, and then pop the VCB02 back in.
3880
days inactive
3881
days old
4 comments
4 participants
participants (4)
-
ajp166＠verizon.net -
elson＠pico-systems.com -
glen.slick＠gmail.com -
jon＠jonworld.com