jwagnervaz / DUAL-CPU-ZX-DU99D4-V1.31-BIOSMOD

BIOSMOD for DUAL CPU ZX-DU99D4 V1.31
MIT License
19 stars 2 forks source link

B7 after flashing #15

Open thiagoretes opened 1 week ago

thiagoretes commented 1 week ago

Hello ;) After I flashed your latest version I got a b1 code. After holding power down button as you said and restarting I always get B7. But it's not the usual B7 I used to get during memory check, it's B7 after 4F code. Already tried flashing the stock version with ch341 and no success at all. Tried removing one CPU and all ram modules, no success. Tried booting without battery, tried reseting cmos, nothing seems to solve it ;( Before flashing the first time I made sure my GPU supported UEFI, the GPU has a switch when toggled/untoggled it switch uefi mode or not, my GPU is a Sapphire RX 580 2GB. Both CPUs are 2680v4 Any tips to solve this?

jwagnervaz commented 1 week ago

Hi,

To flash via ch341 you need be sure the board is receiving Power So, plug the ch341 clip to the BIOS chip.

Power on the PC when try to read/flash the BIOS chip.

Be sure to pin 1 from BIOS match to pin 1 to clip.

Flash your stock BIOS, or my stock BIOS

After try to boot.

If you dont have backup you can use this original BIOS .

https://github.com/jwagnervaz/DUAL-CPU-ZX-DU99D4-V1.31-BIOSMOD/blob/main/BIOS%20DUMP%20FOR%20FLASH%20WITH%20CH341A/ZX-DU99D4%20V1.31.rom

thiagoretes commented 1 week ago

It's reading, writing and verifying the ROM 'correctly' at least the checksums match. Did you mean I have to flash with PSU connected and powered? I might just give another try right now but I tried it earlier.

thiagoretes commented 1 week ago

Did it again with PSU connected and motherboard energized, no post. Still B7 after 4F.

jwagnervaz commented 1 week ago

Did it again with PSU connected and motherboard energized, no post. Still B7 after 4F.

You need to erase chip 1st Maybe its Just that. You rev of the board is 1.31?

The BIOS file need to be 16mb

thiagoretes commented 1 week ago

Yeah, rev 1.31. Already tried erasing chip first, same problem. My bios chip is XM25QH128C in case that is useful.

thiagoretes commented 1 week ago

Good news! After rewriting lots of bios and being frustated I found a russian forum discussion about support on XM25QH128C chip, it was some guy trying to flash older bioses versions on this rev 1.31 and his problem was this chip specifically. After downloading a full dump from another website I just checked it had this chip listed in the descriptors of the bios using UEFITool.

I checked the stock ROM you provided and it's probably this problem, it doesn't support this chip. This is the descriptor region of the new bios I found and finally was able to boot my system: Fixed: Yes Base: 0h Address: FF000000h Offset: 0h ReservedVector: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Full size: 1000h (4096) ME region offset: 1000h BIOS region offset: 800000h Region access settings: BIOS: FFh FFh ME: FFh FFh GbE: FFh FFh BIOS access table: Read Write Desc Yes Yes BIOS Yes Yes ME Yes Yes GbE Yes Yes PDR Yes Yes Flash chips in VSCC table: 1F4700 (Atmel AT25DF321) EF3016 (Winbond W25X32) BF2541 (Microchip SST25VF016B) 1F4700 (Atmel AT25DF321) 1F4501 (Atmel AT26DF081A) 1F4600 (Atmel AT26DF161) C22014 (Macronix MX25L80) C22015 (Macronix MX25L16) C22016 (Macronix MX25U16) C22017 (Macronix MX25L64) C22018 (Macronix MX25L128) 9D7F7A (Unknown 009D7F7Ah) BF258E (Microchip SST25VF080B) BF2541 (Microchip SST25VF016B) 208015 (Micron M25PE16) EF3014 (Winbond W25X80) EF3016 (Winbond W25X32) EF3017 (Winbond W25X64) EF4017 (Winbond W25Q64) EF4018 (Winbond W25Q128) EF6017 (Winbond W25Q64) EF6018 (Winbond W25Q128) C22018 (Macronix MX25L128) A12818 (Unknown 00A12818h) **204018 (Micron XM25QH128C)**

This was yours stock rom: Fixed: Yes Base: 0h Address: FF000000h Offset: 0h ReservedVector: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Full size: 1000h (4096) ME region offset: 1000h BIOS region offset: 800000h Region access settings: BIOS: FFh FFh ME: FFh FFh GbE: FFh FFh BIOS access table: Read Write Desc Yes Yes BIOS Yes Yes ME Yes Yes GbE Yes Yes PDR Yes Yes Flash chips in VSCC table: 1F4700 (Atmel AT25DF321) EF3016 (Winbond W25X32) BF2541 (Microchip SST25VF016B) 1F4700 (Atmel AT25DF321) 1F4501 (Atmel AT26DF081A) 1F4600 (Atmel AT26DF161) C22014 (Macronix MX25L80) C22015 (Macronix MX25L16) C22016 (Macronix MX25U16) C22017 (Macronix MX25L64) C22018 (Macronix MX25L128) 9D7F7A (Unknown 009D7F7Ah) BF258E (Microchip SST25VF080B) BF2541 (Microchip SST25VF016B) 208015 (Micron M25PE16) EF3014 (Winbond W25X80) EF3016 (Winbond W25X32) EF3017 (Winbond W25X64) EF4017 (Winbond W25Q64) EF4018 (Winbond W25Q128) EF6017 (Winbond W25Q64) EF6018 (Winbond W25Q128) C22018 (Macronix MX25L128) 1C4018 (Unknown 001C4018h)

Perhaps it'd be nice to make some disclaimer so ppl could check if their bios chip is compatible before getting into a lot of trouble. This is the BIOS that finally worked, just in case you want to make your mods for it: fullbackup_301123_171936.zip

Another troubleshooting tip, B7 might happen before 4F and after 4F and has two different meanings. If it happens in initial phase of the boot it's probably memory problem or cpu related. If it happens after initial phase(4F is the start of hardware initialization) it's related to BIOS being unable to initialize stuff.

And lastly, it would be nice if you could give some guide on README about how to use AFUWIN. There are lots of options there that might get you into trouble. In this russian forum they didn't recommend AFUWIN because of issues with ME rom part.

Hope that helps anyone that bricks a motherboard haha.

jwagnervaz commented 5 days ago

I conducted some investigation and found that the BIOS you sent is (10/30/2023) ZX-DU99D4 V1.3 DU994305, whereas mine is older (05/06/2023) ZX-DU99D4 DU994304. thanks to https://github.com/jwagnervaz/DUAL-CPU-ZX-DU99D4-V1.31-BIOSMOD/issues/2 My board came with (03/21/2023)ZX-DU99D4 V1.3 DU994301

As you can see, the factory keeps changing BIOS chips to generic ones and updates the VSCC table whenever they make changes in their factory. This unpredictability makes it difficult for me to anticipate their next steps.

I've advised people to back up their BIOS using a disclaimer. This way, they can return to the stock version if necessary. My goal is to fix some bugs and improve its performance.

I'll include this information in the readme soon and suggest that people post their own BIOS here before flashing, so we can verify the BIOS information.

Regarding AFUWIN, I'll try to create a tutorial. I suggested AFUWIN because FTP doesn't support these generic BIOS chips that the factory uses.

As you can see, the factory continues to "update" this BIOS, and there's a newer BIOS (2024 build) available. I saw it in a video and asked the person to share it, but unfortunately, he gave me an empty response.

https://www.youtube.com/watch?v=0PX0qbvGUHM I can confirm exists Bios version at 13:36 at video

(03/06/2024)ZX-DU99D4 V1.3 DU994306

I don't personally know anyone in the manufacturing process. This board is sold by various Chinese brands, and support for it is uncertain.

@thiagoretes can you point where you find this bios dump ? and what about yours bios dump, you did?

With all info i can check, i can update an universal bios, that supports olders versions of these board and they new bios chips.

jwagnervaz commented 5 days ago

@thiagoretes Did test your bios that was posted here https://xeon-e5450.ru/socket-2011-3/kllisre-x99-dual-zx-du99d4-v1-11/ and it gave me error b7. so it confirms that is about VSCC table. will try to make this version universal for older boards.