VOGONS


First post, by ux-3

User metadata
Rank Oldbie
Rank
Oldbie

I have dumpstered an old GA-586ATE/P.
The ODIN chip was empty, so I drilled for the contacts and soldered a 2032 battery to it. I accidentally broke off the lonely pin 1. I also replaced it with a staple, and detected +3V between pin 1 and battery minus. Seems the pin does connect.
PC seems to work, but gives "Unknown Flash Type".
I wonder if this is related to the ODIN chip?

Last edited by ux-3 on 2024-09-07, 06:59. Edited 1 time in total.

Retro PC warning: The things you own end up owning you.

Reply 1 of 12, by dominusprog

User metadata
Rank Oldbie
Rank
Oldbie

Well, was it working correctly before modeling the chip?

Duke_2600.png
A-Trend ATC-1020 V1.1 ❇ Cyrix 6x86 150+ @ 120MHz ❇ 32MiB EDO RAM (8MiBx4) ❇ A-Trend S3 Trio64V2 2MiB
Aztech Pro16 II-3D PnP ❇ 8.4GiB Quantum Fireball ❇ Win95 OSR2 Plus!

Reply 2 of 12, by ux-3

User metadata
Rank Oldbie
Rank
Oldbie
dominusprog wrote on 2024-09-06, 17:51:

Well, was it working before modeling the chip?

I don't know. Is the Odin actually able to cause this?

The time/date and CMOS settings are now kept.

Retro PC warning: The things you own end up owning you.

Reply 3 of 12, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie

No, that chip is not causing the message. That's just the RTC chip. You can ignore the message since the BIOS is obviously working, but the message is just the subroutine complaining that the ID of the IC used for the BIOS EEPROM is unknown to it.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 4 of 12, by rasz_pl

User metadata
Rank l33t
Rank
l33t

related to https://en.wikipedia.org/wiki/Extended_System … figuration_Data
without the error you would see "Updating ESCD" message while BIOS is flashing new data ack to EEPROM.

https://github.com/raszpl/FIC-486-GAC-2-Cache-Module for AT&T Globalyst
https://github.com/raszpl/386RC-16 memory board
https://github.com/raszpl/440BX Reference Design adapted to Kicad
https://github.com/raszpl/Zenith_ZBIOS MFM-300 Monitor

Reply 6 of 12, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie
ux-3 wrote on 2024-09-06, 20:02:
rasz_pl wrote on 2024-09-06, 19:29:

without the error you would see "Updating ESCD" message while BIOS is flashing new data ack to EEPROM.

That would suggest it may well be the ODIN?

No, but he makes a good point... Updating ESCD is important.

What I suggest is to update to the latest BIOS from here (2.31) and see if that solves the issue.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 7 of 12, by rasz_pl

User metadata
Rank l33t
Rank
l33t
ux-3 wrote on 2024-09-06, 20:02:

That would suggest it may well be the ODIN?

its BIOS EEPROM chip itself, as mockingbird said:
"ID of the IC used for the BIOS EEPROM is unknown to it."
did you find this board without a bios and programmed new one to a random chip? or a chance someone did this before you? then you can either try different part number EEprom chip or just ignore it. Afaik this error just means board runs full P&P hardware scan on every boot instead of relying on saved config to speed boot up.

https://github.com/raszpl/FIC-486-GAC-2-Cache-Module for AT&T Globalyst
https://github.com/raszpl/386RC-16 memory board
https://github.com/raszpl/440BX Reference Design adapted to Kicad
https://github.com/raszpl/Zenith_ZBIOS MFM-300 Monitor

Reply 8 of 12, by Repo Man11

User metadata
Rank l33t
Rank
l33t

I found it.

"For the record:
This message means Award PnP core can't update the ESCD data in EEPROM, necessary for ISAPnP operations. Award, some AMI and Phoenix BIOSes store the ESCD data in EEPROM, instead NVRAM. Depending in the board and the BIOS program, this can mean bad news when using ISAPnP cards along PCI ones. Some boards regenerate the data in RAM when they can't retrieve it from EEPROM, so the only issue is slower boot times, and Windows/ICU utilities unable to save resource relocation for ISAPnP cards across cold power cycles (It needs to be reconfigured in each reboot)."

Re: PC Chips BIOS upgrade

"We do these things not because they are easy, but because we thought they would be easy."

Reply 9 of 12, by ux-3

User metadata
Rank Oldbie
Rank
Oldbie

I reflashed the BIOS, which was on 2.31 already. The reflash worked, there were no complains about the flash type from the flash software.
Yet the "unknown flash type " post message remains.

My board revision is 3B. I wonder if the bios is too new for my revision. Pictures show a later revision 4. Should I try an earlier version?

From the above error description, this board would be basically unusable with multiple expansion cards.

I wonder what could be the cause?

Retro PC warning: The things you own end up owning you.

Reply 10 of 12, by ux-3

User metadata
Rank Oldbie
Rank
Oldbie

OK, I tried an earlier bios version.
2.30 gives me "ESCD updated".
So that problem is solved.
On the down side, I lose the ability to boot from CD etc.

Seems like they changed the allowed bios chip ID in 2.31.

Retro PC warning: The things you own end up owning you.

Reply 11 of 12, by rasz_pl

User metadata
Rank l33t
Rank
l33t
ux-3 wrote on 2024-09-07, 07:04:

Seems like they changed the allowed bios chip ID in 2.31.

Its not about allowing something, its checking if its able to flash the chip(right algorithm). New Bios version might shipped on different EEPROMs and vendor didnt bother keeping backwards compatibility. Updating BIOS wasnt really something people did at the time.
You can still try never version using different eeprom chips, maybe you will find one matching.

https://github.com/raszpl/FIC-486-GAC-2-Cache-Module for AT&T Globalyst
https://github.com/raszpl/386RC-16 memory board
https://github.com/raszpl/440BX Reference Design adapted to Kicad
https://github.com/raszpl/Zenith_ZBIOS MFM-300 Monitor

Reply 12 of 12, by targeted

User metadata
Rank Newbie
Rank
Newbie

To add 2c to the discussion, this motherboard has 2 (!) jumpers related to BIOS/CMOS - one for the size and one for the voltage, and until I guessed the right combination, it was giving this exact message of "Unknown Flash Type" before DOS boot.