On Fri, Nov 14, 2014 at 10:08 PM, Justin Hibbits <[email protected]> wrote: > On Sat, 15 Nov 2014 05:11:19 +0100 > Stefan Tauner <[email protected]> wrote: > >> On Fri, 14 Nov 2014 19:34:45 -0800 >> Justin Hibbits <[email protected]> wrote: >> >> > On Sat, 15 Nov 2014 02:41:22 +0100 >> > Stefan Tauner <[email protected]> wrote: >> > >> > > On Fri, 14 Nov 2014 17:30:34 -0800 >> > > Justin Hibbits <[email protected]> wrote: >> > > >> > > > On Sat, 15 Nov 2014 02:06:50 +0100 >> > > > Stefan Tauner <[email protected]> wrote: >> > > > >> > > > > On Fri, 14 Nov 2014 16:45:39 -0800 >> > > > > Justin Hibbits <[email protected]> wrote: >> > > > > >> > > > > > Hi, >> > > > > > >> > > > > > I just checked out the trunk from svn, since it supports the >> > > > > > Kabini SPI bus, but I'm unable to flash the BIOS. I see the >> > > > > > following message when I run it as: >> > > > > > >> > > > > > 'flashrom -p internal:laptop=force_I_want_a_brick -w >> > > > > > myimage.bin' >> > > > > > >> > > > > > "Warning: Chip content is identical to the requested image." >> > > > > >> > > > > Well... above is pretty much everything to say unless you know >> > > > > your image differs from the chip contents. Why do you think >> > > > > there is anything wrong? >> > > > > >> > > > >> > > > Reading the contents back, I get a different binary than what I >> > > > flash in, about 192k into the image. >> > > >> > > Hm... the code that produces the warning above does almost the >> > > same as a manual read and compare... does the read work reliably >> > > (e.g. do files read always have the same md5sum)? >> > > >> > >> > Yeah, I tried twice, before and after flashing the new image, and >> > both reads are identical. I could chock it up to a potentially bad >> > read if the files differed from the flashed rom on a block >> > boundary, but they differ at 192k+89 bytes, so I'm pretty sure it's >> > just not writing the image. >> >> Yes, it is definitely not even trying to write because it reads the >> flash contents, compares it to the file you give it and thinks they >> are equal. Can you please create a log with maximum verbosity (-VVV) >> while you try to write and send it to the list, thanks. >> It might also be interesting to look at the binaries at some point. >> You can upload them to http://paste.flashrom.org/ (posting them here >> wont work). >> > > Thanks for your quick replies. The next log will have to wait for > Monday, since the machine's at work. Unfortunately I can't provide the > BIOS binaries as they contain proprietary code for internal use. > > - Justin
After trying a local setup, apparently with an older version of this board, it appears to be a write protection change in newer spins of this board, so I'll need to find more information from the hardware group about what has changed. The older board revision that I just tried does flash and verify. - Justin _______________________________________________ flashrom mailing list [email protected] http://www.flashrom.org/mailman/listinfo/flashrom
