I just checked the specs on my Enermax PS, it supplies 24A of current on the 3.3V rail. I highly doubt the (at most) .5A supplied by the programmer is going to change anything. I think you misunderstand how current works. If a device draws 200mA you could power it with a 200mA power supply, 2A power supply, or 200A power supply. Nothing is going to change the fact that it draws 200mA. Your laptop doesn't blow up when you swap the 40W (2A @ 20V) power adapter for a 65W (3.25A @ 20V) power adapter. But it will if you swap the 2A @ 20V power adapter for a 2A @ 48V.

Voltage is the concern. If it operates at 20V and you tap 48V across the terminals it is going to pop.

Again my concern was more with 'what are the BIOS datalines doing on a running system while I attempt read/write them from an external device'. Is it going to corrupt the BIOS? Is the system going to hold a line in a high or low voltage state preventing the programmer from doing what it needs to do? etc.

What are the active data pins (for read/write) on a 8-pin SPI chip? I don't know what SO/IO/SCK/CS/etc mean.

Also, this has kinda drifted from the purpose of this thread. In this thread I asked how I would go about modding the Intel bios dump (i.e. what tools do I use and are there any guides) assuming I can ever get my bios dumped to a .BIN. My question about how I can dump the BIOS without desoldering was asked in a different thread. In case Fernando wants to move these last few posts.

The reason I asked about how to mod the Intel bios dump before even getting a dump file is in case someone says "it cannot be done, it is NOT possible to add the TRIM-modified IRST OROM to an Intel bios dump". In that case the question about how to dump the bios becomes moot. I don't want to be holding the desoldered bios chip in my hand when I find out it isn't possible to do what I want.

@gyrator

That's up to you and your need.
As I already previously told, I have no clue about the CH341A, so, you'll better find it's documentation and also ask someone with one.
About the desoldering/soldering it's up to your skill-project. The @IntelModder solution ( adding the SPI socket ) is tied to this.
For the voltage, well, it's a bare chip yet it is connected on it's IC.. so..
The active data pins for stable operation are the whole 8 pin, see the chip maker documentation WINBOND.
And finally, the BIOS: dunno. In support of the old intel bioses you could try to ask the developer of either Andytool and/or UEFITool to add the necessary changes, or lookup by yourself for how LZMA work.
ATM drag and drop workflow with users tool may not work.

You mentioned you've been able to update the microcode. Which tool did you use for that? I don't have a DX58SO dump yet but I've looked at the UBU batch file and it looks like it is capable of detecting an Intel bios and exiting the script...

uefifind body count 49006E00740065006C00........4400650073006B0074006F007000200042006F00610072006400 bios.bin>nul) && echo File Intel Desktop Board BIOS is not supported! && goto exit1

@gyrator

By hands you can already customize almost anything not compressed.
I used an hex editor to replace the microcode for both XEON and i7, there should be a more recent revision somewhere.
For the compressed stuff (main firmware) it require time and understanding how the compression work eg: starting from the inner header/body size/map/checksum, going backwards till the outer LMZA header/body size/map/checksum, all the value must be recalculated while compressing back and adjusted accordingly in each compression level present ( this is just a wild example ).

@gyrator

It's up to you how you dump your firmware. I encourage the method I wrote about before because you can always experiment and recover from a failure. It is also open to you to modify again in future.

I second @noInk 's method to replace microcode. I also used a hex editor to update mine.

I got rid of the ridiculous LZMA compressed section in the firmware for my DX79SR by extracting the uncompressed section from the .bio. I'd need to see a .bin dump of the DX58SO to see if it's also possible in that firmware.

Is it possible to start from a .BIO file to build a modified BIOS and replace the IRST OROM? Or must that begin with a .BIN dump of bios? I know it isn't possible to flash the modified bios file back using Intel's flash software but maybe that modified bios .BIN can be written using a USB flash programmer?

Is it even possible to replace the IRST OROM on an Intel BIOS or is the digital signature a problem that has never been solved? I still haven't found the information that answers my question, is the signature check only enforced during flash update by normal methods (e.g. Intel's flash software or from USB stick in recovery mode)? If so, writing directly to the bios chip with a USB programmer would bypass that. Or is the signature checked every time the bios is loaded? Meaning *any* attempts to modify parts of bios that are signed is impossible without first defeating the signature check (if that's even possible)?

@noInk has a .BIN dump of the DX58SO bios. He located one in his attempts to resurrect his DX58SO board. I've asked him for a copy via PM, maybe he could share it so you could take a look. I'm not much of a tinkerer, I really just want a working TRIM for my SSD RAID array. 11.2.0.1527 is supposed to be the best performing OROM for ICH10R. If I could accomplish that, and get it written into my bios chip, I'd call it "done" and never need to touch bios again. :)

Starting from zero, unlikely.
If you write random stuff it will certainly NOT work.
You can somehow force the board to boot with a modified bootblock and then flash it's already made firmware as recovery procedure, but, without knowing the BIOS structure, the hardware, the software etc etc, it's a kind of trivial task.

Anyway from the 5600 BIO file you can extract the GUID "7A9354D9-0468-444A-81CE-0BF617D890DF" with the "C2D80" size and implement it as "tools readable" within the "main firmware" of the BIN file.
For extract the main firmware out of the BIO file you must know the GUID first. You can help yourself with something capable to output the structure.
After you located the GUID you translate in little endian both's the GUID and the SIZE.
In this specific case the GUID "7A9354D9-0468-444A-81CE-0BF617D890DF" became "D954937A-6804-4A44-81CE-0BF617D890DF" and the SIZE "C2D80" become "802D0C".
Knowing the vector "00000000000000000000000000000000" the translated GUID "D954937A68044A4481CE0BF617D890DF" and the size "802D0C" you can compose the search with "00000000000000000000000000000000D954937A68044A4481CE0BF617D890DF802D0C".
This is the entry point of the main firmware within the BIO.
To extract the whole section you add, if any, the header of the know previous section "802D0C + 40000 = 842D0C" ( 40000 is the header size ) then translate the result in big endian and our previous value "842D0C" become "C2D84".
This is the block size to select and ready to be merged within the BIN file on it's DX58SO offset (73000h)

As I already said, at this point of time there no ready tools available for the task you are asking.
You may accomplish it by yourself but not in a single flash.

Zitat von Fernando im Beitrag #203

---

Zitat von gyrator im Beitrag #201

---

Is it possible to start from a .BIO file to build a modified BIOS and replace the IRST OROM?

---

Obviously not.

---

@noInk

That's is helpful information. If it is possible to replace the IRST OROM I don't have a problem doing it by hand with a hex editor. Amazingly what you are describing (flipping the little endian/big endian ordering) does actually make sense. And I'll certainly file this information away but unfortunately the "how" doesn't help me until I know if the digital signature checks are going to be a problem. I mean I could follow all the steps perfectly and replace the OROM only to have the system refuse to boot because of the digital signature.

I would think *someone* has tried to replace an OROM on an Intel bios before, you'd think there'd be a more clear understanding of how to do it or why it cannot be done.

@gyrator

Once you'll see the original BIN from your board and re-read this, you'll perhaps understand what I wrote and why.
Till then, without the functional way to grab the BIOS and also flash it back I don't think there much to do.


Like you said, someone may already tried with the current available tools and didn't succeeded.

--
Point is the 4A538818-5AE0-4EB2-B2EB-488B23657022 GUID has to be decompressed and re-compressed to make any change within the firmware.
If the utility/script whatsoever you are using is not capable to make out the same compression 1:1 method, (EG: you change nothing but the binary is different ), the board will likely not boot.

--
Since I had the time to look into..
here the DX58SO BIOS (5600) modified with one custom 4MB compressed volume for the main firmware and lot's of free space.

ADDITIONAL INFO:

Current active microcode:

CPU 106A5 REV. 1B 27.06.2015
CPU 106A4 REV. 13 30.06.2015
CPU 206C2 REV. 1D 04.08.2015

BOARD ID: 202
-------------------------------------------------------------------------------

On the 202 board and with a XEON CPU the J55EV and J54EV jumper must be set on non default position ( 1 2 J55EV |  2 1 J54EV ).
These jumper are located nearby the ATX main power connector.

+-----------------------------------------------------------------------------+
| Firmware Image Information                                                  |
+-----------------------------------------------------------------------------+
| Image Size : 200000                                                         |
+------+-------------------------------+--------------+-----------+-----------+
|  FV  |            FV TYPE            |   Location   |   Length  |    FFSs   |
+------+-------------------------------+--------------+-----------+-----------+
|  00  |          NVRAM FV             |   00003000   |  010000   |    000    |
|  01  |          FFS FV               |   00013000   |  05C000   |    003    |
|  02  |          FFS FV               |   00073000   |  120000   |    001    |
|  03  |          Boot Block FV        |   001F0000   |  010000   |    014    |
+------+-------------------------------+--------------+-----------+-----------+
| NCB Information                                                             |
+-----------------------------------------------------------------------------+
| NCB No : 0                         Location :  00000000   Length :  003000  |
| NCB No : 1                         Location :  0006F000   Length :  004000  |
| NCB No : 2                         Location :  00193000   Length :  05D000  |
+-----------------------------------------------------------------------------+
| Firmware Volume : 00               Location :  00003000   Length :  010000  |
+-----------------------------------------------------------------------------+
| Firmware Volume : 01               Location :  00013000   Length :  05C000  |
+---+---------------+------------------------------------+--------+------+----+
|NO |    FileName   |               GUID                 |Location| Size |Type|
+---+---------------+------------------------------------+--------+------+----+
|000|               |2A439012-440E-4798-B64A-174C0582C836|00013048|00186A|PEIM|
|001|               |098158E9-8447-4FF8-8090-9FEFD2A6D4D3|000148B8|001796|PEIM|
|002|               |5B60CCFD-1011-4BCF-B7D1-BB99CA96A603|00016050|000FC1|PEIM|
+---+---------------+------------------------------------+--------+------+----+
| Bytes Free       : 002978 ( 10 KB)    Bytes Used       : 059688 (357 KB)    |
+-----------------------------------------------------------------------------+
| Firmware Volume : 02               Location :  00073000   Length :  120000  |
+---+---------------+------------------------------------+--------+------+----+
|NO |    FileName   |               GUID                 |Location| Size |Type|
+---+---------------+------------------------------------+--------+------+----+
|000|               |4A538818-5AE0-4EB2-B2EB-488B23657022|00073048|0BB9CC|FV  |
+---+---------------+------------------------------------+--------+------+----+
| Bytes Free       : 05D5C8 (373 KB)    Bytes Used       : 0C2A38 (778 KB)    |
+-----------------------------------------------------------------------------+
| Firmware Volume : 03               Location :  001F0000   Length :  010000  |
+---+---------------+------------------------------------+--------+------+----+
|NO |    FileName   |               GUID                 |Location| Size |Type|
+---+---------------+------------------------------------+--------+------+----+
|000|               |52C05B14-0B98-496C-BC3B-04B50211D680|001F0048|0016BC|PEIC|
|001|               |4BB346D2-8076-4671-8BC9-7B95CBB9A6DF|001F1708|00055E|PEIM|
|002|               |8A78B107-0FDD-4CC8-B7BA-DC3E13CB8524|001F1C68|00083C|PEIM|
|003|               |27A5159D-5E61-4809-919A-422E887101EF|001F24A8|000454|PEIM|
|004|               |3870EF56-E2D1-43D4-AB71-DF30F7DA6524|001F2900|0004E4|PEIM|
|005|               |34C8C28F-B61C-45A2-8F2E-89E46BECC63B|001F2DE8|00076E|PEIM|
|006|               |C779F6D8-7113-4AA1-9648-EB1633C7D53B|001F3558|00073E|PEIM|
|007|               |8323C96A-CF42-4D49-99D4-465BB7B53901|001F3C98|00081A|PEIM|
|008|               |150A6A50-C248-48BB-87A8-7630FDC6989E|001F44B8|00103C|PEIM|
|009|               |6E9A03EE-CB9C-4E59-9627-C1CAC6597ED4|001F54F8|001BA6|PEIM|
|010|               |43610A0E-2722-4CEC-93B8-A611FC7139B4|001F70A0|000784|PEIM|
|011|               |8B03CFA6-28AA-4F4B-AA18-99A67B5D95EE|001F7828|000206|PEIM|
|012|               |0A5EA2E1-BE0B-44A0-A775-F429C9A018A0|001F7A30|0046A4|PEIM|
|013|               |1BA0062E-C779-4582-8566-336AE8F78F09|001FEA78|001588|SECC|
+---+---------------+------------------------------------+--------+------+----+
| Bytes Free       : 0029A0 ( 10 KB)    Bytes Used       : 00D660 ( 53 KB)    |
+-----------------------------------------------------------------------------+
| Total Bytes Free : 0628E0 ( 394 KB)   Total Bytes Used : 19D720 (1653 KB)   |
+-----------------------------------------------------------------------------+
 
 

Setting are from factory, better to boot on the CONFIG jumper for the first boot.
The NVRAM content is non-existent, if you plan to flash this file with the programmer directly onto your board you will lose all your setting, serial, license, log, etc etc IF ANY. ( BOARD ID IS SET to REVISION 202 ).
The main firmware with the GUID 7A9354D9-0468-444A-81CE-0BF617D890DF and the SIZE of 120000h can be extracted and applied directly into your binary DUMP at the same exact address of your original volume main firmware offset (73000h).
Even if bigger nothing will be overwritten ( see notice ).
There no changes from the official 5600 release, except for the size, the main firmware volume contain the same official 5600 release 1:1 data.
Changes are on the CPU microcode: revision 13 for the i7 and revision 1D for the XEON. Any other additional changes are just for the structure and ffsv2 readability.

Dunno if there are any utility/tool available to make the additional change you are asking by yourself without adjusting manually a single value, it should be anyway pretty straight forward.

NOTICE:
By using these files YOU WILL BE SOLELY RESPONSIBLE FOR ANY TYPE OF DAMAGE !!!
Before using any part of this recovery file be sure to have a working 1:1 backup of your board.
DO NOT FLASH ANY OFFICIAL RELEASE with the tools provided by the manufacturer.

NO SUPPORT IS GIVEN.

--
Either way, I was able to replace the RAID ROM on mine DX58SO, so, somehow you should too on your.
Duo the shitty driver for the X58, windows 10 will still spin endlessly or BUG literally OUT if you install any incompatible driver like the currently provided by intel ( see mine previous post, it's a different board but same issue ).

Long story short: this is not a retail BIOS, be advised.

hi guys i need bin file for dz77-sl50k motherboard have password i try all things we can do with cemos jumber and bios recovery but nothing so please if anyone can help me with bin file to program it to the bios chip

@ghass


The password set within the bios should be recoverable by booting in config mode ( non default bios pin ) look up for the board documentation \ manual etc, etc.. if nothing else you could backup your own bios and from the NVRAM volume either delete the "SystemPassword" reference within the VSS store or recursively zero the 55 byte starting from the end of the GUID.