VOGONS


First post, by TehGuy

User metadata
Rank Member
Rank
Member

So I've got 2 GA-6BXCs, a Rev 1.7 and 2.0. The 1.7 came with the 29EE020 for its BIOS IC and the 2.0 came with nothing. Both are 2mbit (256K x 8 ) ICs and as far as I can tell from their datasheets the pin layout is the same and both run at 5v. Would there be anything beyond that I would need to look for to make sure I can just slot the new one in the board (after programming) and it work just fine?

29EE020 datasheet
39SF020A datasheet

Win98+DOS: C3 Ezra-T 1.0AGHz / P3-S 1.26GHz, 128MB RAM, AWE64 + Orpheus + Audigy 2 ZS, Ti 4200, 128GB SD card
Win XP SP3: C2Q 9650, 4GB RAM, X-Fi Titanium, GTX 750
PowerMac G4 QS 800MHz + GeForce4 Ti4200, OS 9
PowerMac G5 DP 1.8Ghz + ATi x800 XT, Leopard

Reply 2 of 5, by TehGuy

User metadata
Rank Member
Rank
Member

The only thing I can find that seems to really differ is how the IC performs the writes (byte-program v page-write), product ID, and some timings with how long it takes the IC to perform an operation; otherwise the OP mode selection sequences, software command sequences, etc. seem to be 1:1

But maybe it's the fact the IC writes in a completely different manner (and that I cant find any blocks in the data sheet for Software Data Protect despite the new chip saying it supports that stuff per JEDEC spec) that would throw things off... Well, it'd be ~$1.8 USD and it's going to get bundled in with some caps I need so I don't think it'd cost me too much to find out if it'll work or not.

Failing that, there's apparently a bit of work I can do via

I used UNIFLASH to save the BIOS from a working system (using the SST PH29EE010-150-3CF flash chip) into a file. Then I flashed this saved BIOS (and not the original UUD2014.BIN file) onto the 39SF010A flash chip and it worked like a charm. No "Updating ESCD ... " message anymore and therefore also no hang. Apparently, when UNIFLASH saves a BIOS to file, it also saves the ESCD data alongside the actual BIOS.

with the caveat that I can't be swapping cards around lest I make the BIOS want to reconfigure itself, but that shouldn't be too much a problem.

Win98+DOS: C3 Ezra-T 1.0AGHz / P3-S 1.26GHz, 128MB RAM, AWE64 + Orpheus + Audigy 2 ZS, Ti 4200, 128GB SD card
Win XP SP3: C2Q 9650, 4GB RAM, X-Fi Titanium, GTX 750
PowerMac G4 QS 800MHz + GeForce4 Ti4200, OS 9
PowerMac G5 DP 1.8Ghz + ATi x800 XT, Leopard

Reply 3 of 5, by jakethompson1

User metadata
Rank l33t
Rank
l33t

For what it's worth, not long ago I got an MB-8433UUD-A v3.1 that had an EPROM BIOS instead of EEPROM. It would print "Updating ESCD..." message with the EPROM, not hang, and continue booting without printing "Success". With the SST39SF020A, it would hang. Not sure what all the ramifications of having nowhere to store the ESCD would be. Guessing it might cause issues with PnP cards in Windows 95.

Reply 4 of 5, by mihai

User metadata
Rank Member
Rank
Member

if the new eeproms are cheap, it is worth trying. Looking on ebay, 29EE020 eeproms are plentiful and very cheap, less than 2 USD per piece.

I replaced 3 defective bios chips with other 3 random bios chips (different brands) bought from ebay and new chips all worked.

Reply 5 of 5, by zapbuzz

User metadata
Rank Oldbie
Rank
Oldbie
jakethompson1 wrote on 2021-09-15, 00:29:

For what it's worth, not long ago I got an MB-8433UUD-A v3.1 that had an EPROM BIOS instead of EEPROM. It would print "Updating ESCD..." message with the EPROM, not hang, and continue booting without printing "Success". With the SST39SF020A, it would hang. Not sure what all the ramifications of having nowhere to store the ESCD would be. Guessing it might cause issues with PnP cards in Windows 95.

I have an ASUS mobo wwith a beta bios that doesn't say ESCD success being beta 🤣