[flashrom] join IRC

[Владимир Амельянович]

Hello,

1) save image - flashrom -p
internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -r boxpc899_0.rom
2) write image - flashrom -p
internal:laptop=force_I_want_a_brick,ich_spi_mode=auto -w boxpc899_0.rom -V
-o /lib/live/mount/medium/

I have tried to write saved image finally. And got the following message:

FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... Reading 8388608 bytes starting at
0x000000.
done.
Apparently at least some data has changed.
Your flash chip is in an unknown state.
Get help on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom at flashrom.org with the subject "FAILED: <your board name>"!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
Restoring MMIO space at 0x7fb5896f08a0
Restoring PCI config space for 00:1f:0 reg 0xdc

-V output attached.

What should i do next?  PC is power on.


2018-08-09 23:16 GMT+03:00 Владимир Амельянович <
amelyanovich.vladimir at gmail.com>:

> Hello Nico,
>
> Thank you very much for your information.
>
> Does the image of SPI chip  which i get with -r key contain BIOS firmware
> or BIOS settings or both?
> My goal is to create  BIOS master image which i can write to 10,20,100
> devices with same hardware.
>
> Regards,
> Vladimir
>
>
> 2018-08-09 22:11 GMT+03:00 Nico Huber <nico.h at gmx.de>:
>
>> Hi Владимир,
>>
>> On 08.08.2018 10:07, Владимир Амельянович wrote:
>>
>>> flashrom -p internal:laptop=this_is_not_a_laptop  didn't change anything
>>>
>>
>> yes, because your BIOS claims that it's a laptop: `DMI string
>> chassis-type: "Notebook"`.
>>
>> flashrom -p internal:laptop=force_I_want_a_brick show more info. Logs
>>> with
>>> different V number are attached.
>>> Please could you please tell me if i can use flashrom in my case?
>>>
>>
>> You already did. If you let it probe with the above force option,
>> it can already harm some laptops. But in your case (SPI chip directly
>> attached) it's safe. You can go ahead (if you have a valid image to
>> flash). In either case of success of failure, please always keep
>> logs (best use the -o option) and report back.
>>
>> Please note that your message got filtered from the mailing list (there
>> is a 256KiB limit for the mail size). So I'll attach your least verbose
>> log for reference.
>>
>> Regards,
>> Nico
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.coreboot.org/pipermail/flashrom/attachments/20180814/5665883b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: flashrom899write.log
Type: text/x-log
Size: 56921 bytes
Desc: not available
URL: <http://mail.coreboot.org/pipermail/flashrom/attachments/20180814/5665883b/attachment-0001.log>