Re: [flashrom] report for Intel QM67 | Winbond W25Q64 ([PATCH] (not for merge) ichspi: print BFPR (BIOS Flash Primary Region Register))

[Stefan Tauner]

On Tue, 23 Aug 2011 08:41:35 +0200
"Frei, Thomas (GE Germany)"  wrote:
> please send me this patch - I first want to read out the flash - and if this works, I will try to write...
>
> I need this for production test.

i have already posted my patches in the (sub)thread named "[PATCH 0/7]
every layout handling feature you ever wanted to see but never cared to implement".
if you are not subscribed to the list you could also fetch them from
http://patchwork.coreboot.org/project/flashrom/list/ (all those with date 2011-08-19).
i will mail them to you separately this time. you need at least 1-5 to
be able to read.
> Will this patch work without a layout file? I fnot, can you tell me how to generate it?

no, it will not work without one. there is apparently no way to flash
beyond the regions defined by the flash descriptor. the layout file can
limit the address range accessed (to make it work). depending on how
fine-grained you wanna use it you can define in the layout file ranges
for each region as defined by the flash descriptor on your board (from
this output of flashrom:)
0x54: 0x00000000 (FREG0: Flash Descriptor)
0x00000000-0x00000fff is read-write
0x58: 0x03ff0200 (FREG1: BIOS)
0x00200000-0x003fffff is read-write
0x5C: 0x01ff0001 (FREG2: Management Engine)
0x00001000-0x001fffff is read-write
or just define one range for the whole accessible area (that would be
something like 0x0 - 0x003fffff i would say)

i think you will probably need to set the read_all_first variable in
flashrom.c to 0 (and maybe also use the -w parameter) to be able to
write without errors printed, else flashrom will try to read the whole
flash before and after writing to verify its contents.

i have told you already at least twice to look into our documentation.
you know that this is my spare time and i am not here to do your
work... if you have concrete questions about layout files or their
usage we are happy to answer that, but "how do we do that?" makes me
kinda angry, if it is already documented.