PC Hoarder Patrol wrote on 2024-11-18, 09:22:

Certainly not their clearest bit of technical documentation!...

...JP6 = Keyboard Wakeup = JPWAKE

The attachment 840slot1_1.1i.pdf is no longer available

Yea
It is not working anyway.
I need a way to circumvent the id check of the Supermicro customised flash program.
No idea how.

Mamba wrote on 2024-11-18, 09:37:

Yea It is not working anyway. I need a way to circumvent the id check of the Supermicro customised flash program. No idea how. […]
Show full quote

PC Hoarder Patrol wrote on 2024-11-18, 09:22:

Certainly not their clearest bit of technical documentation!...

...JP6 = Keyboard Wakeup = JPWAKE

The attachment 840slot1_1.1i.pdf is no longer available

Yea
It is not working anyway.
I need a way to circumvent the id check of the Supermicro customised flash program.
No idea how.

Have read that when using the BIOS recovery option the source file to rename (in your case dme3171.rom) should be uppercase, so SUPER.ROM

PC Hoarder Patrol wrote on 2024-11-18, 09:48:

Mamba wrote on 2024-11-18, 09:37:

Yea It is not working anyway. I need a way to circumvent the id check of the Supermicro customised flash program. No idea how. […]
Show full quote

PC Hoarder Patrol wrote on 2024-11-18, 09:22:

Certainly not their clearest bit of technical documentation!...

...JP6 = Keyboard Wakeup = JPWAKE

The attachment 840slot1_1.1i.pdf is no longer available

Yea
It is not working anyway.
I need a way to circumvent the id check of the Supermicro customised flash program.
No idea how.

Have read that when using the BIOS recovery option the source file to rename (in your case dme3171.rom) should be uppercase, so SUPER.ROM

Yes I did it.
I receive the error messages.

Tried the amiflash utility.
It says bios is write protected.
I am running out of options, maybe I have to give up and wait forever for an Intel chip to reach me from China….

What sequence of POST codes do you get before it reaches AMIFLASH?

kmeaw wrote on 2024-11-18, 13:30:

What sequence of POST codes do you get before it reaches AMIFLASH?

What you mean?
Before it posts?
The motherboard posts correctly and even loads WinXP.

I am loading Amiflash after correct post. So not sure about the request.

Sorry, I probably have misinterpreted your description. For some reason I thought that the BIOS is forcing you into an embedded flash recovery utility on each boot and you had to abort it to boot into OS.

I have checked the bootblock code - it seems to support only Intel 82802AB:

10007939C  E807A5            call 0x38a6 ; send program command
20007939F  E8E2FF            call 0x9384 ; send reset command
3000793A2  1E                push ds
4000793A3  6657              push edi
5000793A5  6A00              push byte +0x0
6000793A7  1F                pop ds
7000793A8  66BF0000FFFF      mov edi,0xffff0000
8000793AE  67C60790          mov byte [edi],0x90 ; read ID command
9000793B2  678A07            mov al,[edi] ; manufacturer code
10000793B5  678A6701          mov ah,[edi+0x1] ; device code
11000793B9  678A7F02          mov bh,[edi+0x2]
12000793BD  8AD8              mov bl,al
13000793BF  665F              pop edi
14000793C1  1F                pop ds
15000793C2  E8E2A4            call 0x38a7 ; empty func
16000793C5  C3                ret
17
180007929D  E8FC00            call 0x939c ; see above
19000792A0  3D89AD            cmp ax,0xad89 ; Intel 82802AB, 4Mbit
20000792A3  58                pop ax
21000792A4  5B                pop bx
22000792A5  C3                ret

So without doing any modifications this is the only chip that can be used for write and erase operations.
However replacing the ID check at 0x792A0 is easy, so it can be modded to support another FWH flash if the set of supported commands matches Intel's: FF - reset, 90 - read id, 70 - read status, 50 - clear status, 20 - block erase, 10 - program.
PM49FL004T-33JCE only has a JEDEC-style command set, so it won't work.
Atmel AT49LH004, SST 49LF004C, ST M50FLW040 support Intel command set, so they should (if package and electrically compatible, I haven't checked that) work on a modded BIOS.

kmeaw wrote on 2024-11-18, 15:33:

I have checked the bootblock code - it seems to support only Intel 82802AB: […]
Show full quote

I have checked the bootblock code - it seems to support only Intel 82802AB:

Copy code to clipboard

10007939C  E807A5            call 0x38a6 ; send program command
20007939F  E8E2FF            call 0x9384 ; send reset command
3000793A2  1E                push ds
4000793A3  6657              push edi
5000793A5  6A00              push byte +0x0
6000793A7  1F                pop ds
7000793A8  66BF0000FFFF      mov edi,0xffff0000
8000793AE  67C60790          mov byte [edi],0x90 ; read ID command
9000793B2  678A07            mov al,[edi] ; manufacturer code
10000793B5  678A6701          mov ah,[edi+0x1] ; device code
11000793B9  678A7F02          mov bh,[edi+0x2]
12000793BD  8AD8              mov bl,al
13000793BF  665F              pop edi
14000793C1  1F                pop ds
15000793C2  E8E2A4            call 0x38a7 ; empty func
16000793C5  C3                ret
17
180007929D  E8FC00            call 0x939c ; see above
19000792A0  3D89AD            cmp ax,0xad89 ; Intel 82802AB, 4Mbit
20000792A3  58                pop ax
21000792A4  5B                pop bx
22000792A5  C3                ret

So without doing any modifications this is the only chip that can be used for write and erase operations.
However replacing the ID check at 0x792A0 is easy, so it can be modded to support another FWH flash if the set of supported commands matches Intel's: FF - reset, 90 - read id, 70 - read status, 50 - clear status, 20 - block erase, 10 - program.
PM49FL004T-33JCE only has a JEDEC-style command set, so it won't work.
Atmel AT49LH004, SST 49LF004C, ST M50FLW040 support Intel command set, so they should (if package and electrically compatible, I haven't checked that) work on a modded BIOS.

Thank you for your findings.
It is far beyond my expertise.
Are you able to mod the bios?

The ATMEL seems promising:

https://datasheet.octopart.com/AT49LH00433JC- … heet-117415.pdf

“ Auto-detection of FWH and LPC Memory Cycles
– Can Be Used as FWH for Intel 8xx, E7xxx, and E8xxx Series Chipsets”

Unfortunatelly no, I don't know much about AMI BIOSes.
You would need to replace bytes "89AD" with "1FEE" at 0x7929E in the uncompressed code and at 0x5EA in the runtime (compressed) module. But I don't know how to recompress the module and update the checksum.
Maybe Jan Steunebrink aka Chkcpu could help you with AMI?

I always bother Jan now and then from decades, better not…
Will wait for the Intel chip.

Here is my first attempt to do a patch for AMI95. I have reused rom.by's patch engine for that and repacked it with AMIBCP 7.01.01.
It should work on ATMEL AT49LH004 4Mbit PLCC32 chip.

kmeaw wrote on 2024-11-19, 04:35:

Here is my first attempt to do a patch for AMI95. I have reused rom.by's patch engine for that and repacked it with AMIBCP 7.01.01.
It should work on ATMEL AT49LH004 4Mbit PLCC32 chip.

Thank you,
Will use it in case I will stumble across the ATMEL chip

Ok now it gets weird….

Three chips arrived from China.
All 3 seems to be ok, I read them correctly with my Xgecu programmer.
So I loaded on all 3 the PIIIDME bios.

Guess what?

None of them works, or better, the board does not post at all with them.
Post card does not show anything ( - -).

It does not make any sense, the chips are ok, no errors. And I used exactly the same programmer,bios and method!

Any clues??

When you order something and get it "different"...

Could it be possible that some lines of code are written elsewhere and not being part of the BIOS?
Like some confirmation code in order to avoid tinkering.

Nexxen wrote on 2024-12-15, 18:19:

When you order something and get it "different"...

Could it be possible that some lines of code are written elsewhere and not being part of the BIOS?
Like some confirmation code in order to avoid tinkering.

There is exactly the same bios file of the PM49FL004T, loaded with the same Xgecu programmer.
There are no differences at all.
Plus, the Xgecu T48 is able to spot problems on the chip, and all of three are fully recognised, correctly erased and with all pins ok.
What I am experiencing is pure non sense.
Or this motherboard for unknown reasons does not want its own Intel bios chip type anymore…

Mamba wrote on 2024-12-15, 18:29:

There is exactly the same bios file of the PM49FL004T, loaded with the same Xgecu programmer. There are no differences at all. […]
Show full quote

Nexxen wrote on 2024-12-15, 18:19:

When you order something and get it "different"...

Could it be possible that some lines of code are written elsewhere and not being part of the BIOS?
Like some confirmation code in order to avoid tinkering.

There is exactly the same bios file of the PM49FL004T, loaded with the same Xgecu programmer.
There are no differences at all.
Plus, the Xgecu T48 is able to spot problems on the chip, and all of three are fully recognised, correctly erased and with all pins ok.
What I am experiencing is pure non sense.
Or this motherboard for unknown reasons does not want its own Intel bios chip type anymore…

Could it be checking the BIOS's chip ID?

Nexxen wrote on 2024-12-15, 18:51:

Mamba wrote on 2024-12-15, 18:29:

There is exactly the same bios file of the PM49FL004T, loaded with the same Xgecu programmer. There are no differences at all. […]
Show full quote

Nexxen wrote on 2024-12-15, 18:19:

When you order something and get it "different"...

Could it be possible that some lines of code are written elsewhere and not being part of the BIOS?
Like some confirmation code in order to avoid tinkering.

There is exactly the same bios file of the PM49FL004T, loaded with the same Xgecu programmer.
There are no differences at all.
Plus, the Xgecu T48 is able to spot problems on the chip, and all of three are fully recognised, correctly erased and with all pins ok.
What I am experiencing is pure non sense.
Or this motherboard for unknown reasons does not want its own Intel bios chip type anymore…

Could it be checking the BIOS's chip ID?

What you mean?
It is the same file.
loaded in one chip works and i another one (the one that is supposed to work properly), not.

Weird things often happen when someone's using Ali Baba's cave 😀 You order exact chip model, but you get some sanded and relabeled "compatible" chip.

Did you tried kmeaw's modified BIOS for the Atmel AT49LH004 chip?

analog_programmer wrote on 2024-12-15, 19:03:

Weird things often happen when someone's using Ali Baba's cave 😀 You order exact chip model, but you get some sanded and relabeled "compatible" chip.

Did you tried kmeaw's modified BIOS for the Atmel AT49LH004 chip?

I do not think so.
The chips seems original, it is not easy to replace the writings on it.
Plus, the programmer would spot differences or errors. It is not a basic ch341a thing.
There is not use in trying a different bios.