VOGONS


First post, by majestyk

User metadata
Rank Member
Rank
Member

Since I´m collecting all kinds of mainboards made by FIC (until and including Socket 7) I stumbeled across this obscure LPX board.
It was OEMed for AT&T and their Globalyst 620 / 630 systems and came in different revisions / versions.
There´s a version with VIA chipset and a proprietary cache socket like they used on the 486-GAC-2 that looks like a VLB socket and there are (at least) two revisions of a second version with VLSI chipset and a standard CELP COAST socket.
I`m having "fun" with revision 4.11 at the moment which also has a special "feature connector" that looks like the 80-pin SCSI connectors.

psk2000_1.JPG
Filename
psk2000_1.JPG
File size
1.98 MiB
Views
147 views
File license
Fair use/fair dealing exception

They did a lot of post-production solder work here so I guess this probably was the first revision.

psk2000_2.JPG
Filename
psk2000_2.JPG
File size
256.99 KiB
Views
147 views
File license
Fair use/fair dealing exception
psk2000_3.JPG
Filename
psk2000_3.JPG
File size
278.34 KiB
Views
147 views
File license
Fair use/fair dealing exception
psk2000_4.JPG
Filename
psk2000_4.JPG
File size
257.85 KiB
Views
147 views
File license
Fair use/fair dealing exception
psk2000_5.JPG
Filename
psk2000_5.JPG
File size
202.12 KiB
Views
147 views
File license
Fair use/fair dealing exception

It´s also featuring the infamous "PCI0640B" IDE controller...

to be continued...

Reply 1 of 4, by majestyk

User metadata
Rank Member
Rank
Member

...

psk2000_6.JPG
Filename
psk2000_6.JPG
File size
271.47 KiB
Views
146 views
File license
Fair use/fair dealing exception

There´s also a nice riser card for ISA/PCI cards

psk2000_7.JPG
Filename
psk2000_7.JPG
File size
285.89 KiB
Views
146 views
File license
Fair use/fair dealing exception

When I got this board it wouldn`t start due to some damaged traces near the CPU socket that were easy to repair with thin wires

psk2000_8.JPG
Filename
psk2000_8.JPG
File size
218.03 KiB
Views
146 views
File license
Fair use/fair dealing exception

The latest BIOS - 1.07 - can still be obtained from the NCR website
http://www5.ncr.com/support/support_drivers_p … pc_library_3348

Floppy drives are NOT recognized by this mainboard when they are connected to the second connector of the floppy cable (the one behind the wire-crossing). Floppys need to be connected to the first connector instead.

The board offers 50, 60 and 66 MHz FSB and multiplicators x2 and x1.5.
Jumper JP2 switches between core voltages 3.3V and 3.45V.
An additional VRM socket could also be soldered in to provide 2.8V for Pentium MMX but the BIOS doesn´t know any MMX models and given the multiplicator limitations I don´t thik it would make any sense.

Here´s the "feature connector" that can be enabled in the BIOS menu, it´s not populated in later revisions of this board.

psk2000_10.JPG
Filename
psk2000_10.JPG
File size
257.43 KiB
Views
120 views
File license
Fair use/fair dealing exception

t.b.c.

Attachments

  • psk2000_9.JPG
    Filename
    psk2000_9.JPG
    File size
    69.74 KiB
    Views
    132 views
    File license
    Fair use/fair dealing exception

Reply 2 of 4, by majestyk

User metadata
Rank Member
Rank
Member

There´s some progress here. This board has a Socket 5 CPU socket, but is prepared for the connector for an additional 2.8V VRM. I suspected it´s in fact capable of split voltage AKA Socket 7.
So I fitted the 2x15 pins for the VRM in and cut the traces between pin pair 6 and 7, put one of my VRMs on top and a Pentium MMX 233MHz in the socket:

PSK2000_10.JPG
Filename
PSK2000_10.JPG
File size
249.04 KiB
Views
94 views
File license
Fair use/fair dealing exception
PSK2000_11.JPG
Filename
PSK2000_11.JPG
File size
259.76 KiB
Views
94 views
File license
Fair use/fair dealing exception

Then I set the multiplier dip-switch to x1.5 and started the system. To my disappointment the MMX was running at 133 MHz, it didn´t respond to the 1.5 multi by interpreting it as x3.5.
Checked BF1 -> open,
checked BF2 -> open,
checked BF0 (formerly BF) -> open.
On this mainboard the dip-switch releases BF0 from ground but there´s no pull-up resistor present to lift the BF0 pin up to Vcc. So I added a 4K7 resistor and voila

PSK2000_12.JPG
Filename
PSK2000_12.JPG
File size
140.26 KiB
Views
94 views
File license
Fair use/fair dealing exception

The next - and bigger - problem is the COAST cache module. FIC / AT&T obviously have a non standard pinout here that prevents regular COAST modules from being used.
I tested about 25 different COAST modules, all of them are either not detected or prevent the system from starting.

Last edited by majestyk on 2021-02-21, 17:41. Edited 2 times in total.

Reply 3 of 4, by dionb

User metadata
Rank l33t
Rank
l33t
majestyk wrote on 2021-02-21, 11:15:

[...]

The next - and bigger - problem is the COAST cache module. FIC / AT&T obviously have a non standard pinout here that prevents regular COAST modules from being used.
I tested about 25 different COAST modules, all of them are either not detected or prevent the system from starting.

I don't think that pinout is the problem, rather the cache type. This board contains a VLSI 82C590 PowerCore chipset, which is pre-i430FX, so almost certainly also pre-PLB cache. That means it would need an async SRAM cache module. I've not been able to find a datasheet to confirm this assumption, but given you've thrown probably about every PLB config in existence against it, it seems more than likely.

Reply 4 of 4, by majestyk

User metadata
Rank Member
Rank
Member

This might well be the case, or both.
With PLB modules the machine won´t start at all.

Then I have a lot of "sync cache" modules like this:

sync_cache.JPG
Filename
sync_cache.JPG
File size
587.98 KiB
Views
69 views
File license
Fair use/fair dealing exception

Withe these the system starts bot no cache is being detected.

I couldn´t find any datasheet of the VLSI MCH so far.

I then compared the COAST pinout of this mainboard with this one:
download/file.php?id=82702&mode=view

All Vss connections are identical. Same goes for the "Vcc5" voltage. The connections for "Vcc3" differ. On the FIC socket Vdd3 is at pins 76, 68, 60, 52, 39, 25, and 15. It´s NOT at Pin7 as it should be according to the pinout documentation. Pin 7 leads to a pin of the MCH (VL82C591FC3) instead. Pin 6 at the COAST socket is NOT "NC" but also in use.
On all COAST sticks I own, the Vdd3 - Pins 76, 68,60, 52,39, 25,15 AND 7 are bridged.
So VDD3 (3.3V) is probably connected to some Data line when a standard COAST module is inserted.