I have made another BIOS.This one failed too even though looks good.Q-Flash says it s an invalid Image.

I have tested it by extracting HOLE-s after and comparing them with the ones extracted before re/adding HOLE4(DONOR) ,HOLE5 (DONOR-manually collected same size as CBROM reported) and HOLE3(FGf) into FGf.
HOLE 3 was extracted released reinserted the last in the hope of checksums corrections.

I had also took the Hex and compared them by copy/paste them to see if they overlap,they didn t
Keep in mind that even though HOLE5 can be inserted with CBROM with no problems ,it can t be extracted with CBROM.So it must be checked manually in HexEditor.
CBROM had all modules listed and with correct size.

All seemed good in theory but ... after flashing it with atBIOS i still was in a black screen with monitor in stand by.This time it took longer though for the Recovery to kick in.
So something is still wrong.

Keep in mind i am using the Phenom 2 and that NCPUCODE is as it is in this beta(FGf) by default.So even if we make the assumption it s from NCPUCODE it worked without it as well.
I did not touched the NCPUCODE ,it was left as it is in this beta BIOS-es.

By the way the code in the previous picture seems to be from ECCODE.bin code.

Until someone that knows coding comes in i am unable to do more.
I would have tried directly some other BIOS if this not cheap board wouldn t have had such a small NVRAM chip.

I am opened to ideas.Maybe some checksums don t go right in there.

I will do one more try.

I will take the BIOS FGc as mod base.Maybe FGf has something in it that brakes the mod.It s 1K smaller in code.

I will also harvest the AGESA from a 990FXA board via HEX Editor.
Maybe indeed the AGESA code i ve took from the AMD 780 board is not compatible with the 890 chipset or something ,even though they are quite similar.

I will report what happens.

Edit:

I have made a BIOS based on the FGc.
It didn t work either .
Same Invalid BIOS image in Q-Flash and flashed with atBIOS did the same black screen at restart ,monitor led flashing as in stand by and then the routine of Auto Recovery kicked in putting back FF BIOS.

Preparation was the following:

1.Released the RAID850 component.

2.Released the HOLE4 and HOLE5 as well.

3.Edited the *HOLEf* field in the resulted file so it allows the full HOLE5 file to be inserted via CBROM ,as i have discovered and presented in previous posts.Value was changed for 95 module to 50 from 45.I did the same for HOLE4 (module 94 in there) which i ve changed from 10 to 11 from the fear of not having it incomplete as discovered earlier.

4.Added via CBROM HOLE5 (Agesa 1500)
HOLE5 here -> http://www.sendspace.com/file/rcz1sz

5.Added via CBROM HOLE4 (Agesa 1500)
HOLE4 file here -> http://www.sendspace.com/file/lfypip

It s interesting to notice that FGc opposed to FGf has no HOLE3 (ECCODE.bin) module.
Both of the original BIOS-es are linked in the first post.

The BIOS file resulted is here ,has no RAID module ,was left out -> http://www.sendspace.com/file/oeydfe

The checksums look ok ,but the Q-Flash Invalid Image message is what puzzles me.
At any normal BIOS file Q-Flash ,before flashing ,it shows a Checksum number.
Where is it getting it is the question.
Then i wonder if my BIOS-es don t work because the Checksum procedure kicks in first and before it even loads the BIOS file it goes for the Recovery ,which states Checksum error as well.

Hello again.

I think i am finally close to something here.
As the CBROM does strange stuff decided to use ONLY the copy/paste approach.

So what i did was to take FGc BIOS this time and see if by copying the new modules content over the old content it works.

So took the file opened it and the pasted HOLE4 and then HOLE5 content over.
As they are bigger by adding each one ,other lines were moving down ,so i have moved each ones start back to the offsets they had before pasteing.Practically by this i have removed some of the FFFFFFFFF dummy stuff.

This CAN NOT be done on the FGf on the other hand as after pasteing the HOLE5 content ,the big one ,the end of this module would overlap HOLE3 content ,which is ,with luck, a module non existent in the FGc. :)

So this is what i have now ,after correcting the *HOLE* 94 and 95 maximum sizes as it was did in that sticky.The modules are in there ,but CBROM reports the old dimensions of the previous ones.


I have the hunch that this ones in this picture are the lines that determine also the position and space of this HOLE-s


This module or whatever it is ,somehow splits the BIOS file in 2 ,whats upper than it in Hex Editor is the HOLE-s content it seems ,under it in HexEditor there seems to be compressed modules.
It s some kind of boundry ID-ing the HOLE-s.
Maybe this module is the one that checksums HOLE-s.

So what do i correct in there.I ll take a look in the donor BIOS and see some hints or something ,but it would be nice to know each of those numbers purpose.
And almost forgot.
If this lines have nothing to do with the wrong file dimensions how do i correct them so the HOLE4 and HOLE5 show the correct sizes.Around 63Kb for HOLE4 and around 297Kb for the HOLE5.


Edit:
And here is a picture where we have on the right the FGc BIOS made with CBROM and on the left the initial values from the copy/pasted one (the strings are identical to the one in the original FGc of course)


Another question would be if i should change the HOLE names according to the DONOR BIOS.Copy/paste this strings from donor.
AGESA 1500 HOLE4 and HOLE 5 modules have different names in the other AGESA 1500 Gigabyte BIOS-es.
Could this names be hard coded in the modules copy-ed !?
Maybe that s why they are not initialized ?!

Zitat von Fernando im Beitrag #36

---

@ Jumbix:

What you are doing is really applaudable. I like people like you, who never give up. This is the way you learn the most.
All I wish is, that you will succeed at least. I have already my fingers crossed.

---

Zitat von Fernando im Beitrag #38

---

Zitat von Jumbix im Beitrag #37

---

Can the sound module be replaced with no head scratch?!
Where is it usually as i am not able to identify it.

---

I have extracted several modules of your BIOS and opened them with a hex editor, but I didn't find the sound module either.

---

Fernando ,this is the checksum used by Gigabyte ,the one that Q-Flash checks for at BIOS update.This checksum poped up at install.
It s 16 bit.



This is my modified file and same was on the FGc when i ve installed it to test it.
As the file has been modified the probability for the checksum to be AA00 as the original FGc is impossible. :)

And another question.
When you change modules does ITEM.bin needs modifications.What modules modifie when you change modules ?!
Any other modules should be changed ?!

EDIT:

Could be the fact that i ve worked with the hex editor in bytes instead of Dwords a problem ?!
Maybe harvested the modules incomplete or something ?!

Reading some BIOS guide i have downloaded IDA Pro Free(some old version) and loaded some BIOS-es and see how they are executed.
Loaded the FGc original and the last modded FGc that i ve made
Look here
The original FGc beta ,nice and tidy


My BIOS :) ,clearely there is something wrong in the routine ,no need to be a coder to see it :)



Most probable the chipset is not initialized as it seems it should be the first in the line as its module is somewhere to the end in there.:)

Hey Guys, was the modding of the AM3 Board for FX Cpu successfull? At this time, i have a similar Project in a ZOTAC AM3 ITX Board.