Hi Taiidan, try following these instructions:
1) download the latest official BIOS update .exe file from your laptop manufacturer's website (Lenovo in this case)
2) open this .exe file with 7zip utility and extract all its' contents to a separate folder
3) most likely is that amoung these extracted files you will see a several megabytes binary file, which contains not just a BIOS image but also EC firmware image and some other images. Then you open this binary file in a hex editor like Okteta and search for some ASCII string symbols like for example _EC_IMG to e.g. locate the beginning of EC firmware block, and knowing what size in bytes the EC firmware should be - you cut the same amount of bytes after _EC_IMG text - and save into a new binary file
Something like that, will probably work for you. Good luck in your research ;)

2017-03-07 5:23 GMT+00:00 Taiidan@gmx.com <Taiidan@gmx.com>:
Uhh thanks but that's kinda missing the point of this - that I don't want binaries from random people on the internet.

I need to know how to extract it from the bios update files, not the bios already on the EEPROM.


On 03/06/2017 11:35 PM, Matt DeVillier wrote:
I have the IFD and ME from an x220 that I recently flashed with coreboot
for a customer, extracted from their stock firmware, and verified working
with the coreboot ROM I subsequently flashed.  Can zip and send via email,
or whatever you prefer

On Mon, Mar 6, 2017 at 10:23 PM, Taiidan@gmx.com <Taiidan@gmx.com> wrote:

On 03/05/2017 05:20 AM, Arthur Heymans wrote:

"Taiidan@gmx.com" <Taiidan@gmx.com> writes:
Well I managed to download the latest BIOS from the lenovo site, which
includes an ME update now the issue is that I can't seem to figure out
how to extract it from the .FL1 and .FL2 files.

Those might have a length too long to fit a flash so you need to trim
those down before using ifdtool on those (If they contain and ifd of
course)
so depending on size of rom
dd if=FL1(or 2)file of=vendor_bios.rom bs=1 count=xM

and then ifdtool -x vendor_bios.rom

It didn't work :( after that still "no flash descriptor found in this
image"

These are the files and the flash chip on the board is 8M
8523776 '$01CB000.FL1'
8523776 '$01CB000.FL2'
8523776 '$01CB100.FL2'
All of them have different hashes, but I do not know what makes them
different (maybe it is for various board revisions?)


I would also like to know as to how I can re-flash the EC firmware if
that could potentially cause problems, I of course do not know if it
has DMA.

Only existing tool to flash EC is using vendor tool.
EC are only accessed trough port mapped IO (or on newer ones also via
memory mapped IO). EC itself does not have DMA afaik.


--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot


      



--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot