New version, more bug fixes. Thanks for Carl-Daniel for testing! - Restore the original ROM before beginning the second set of tests. - The last iteration of the second test (un-aligned partial writes) was causing problems on a 128KB part (emulated). I've removed it for now since I'm in a hurry to get out tonight. - Fixed a copy + paste error in the 4k aligned test layout. - Added $FLASHROM_PARAM to the list of parameters passed into Flashrom.
On Tue, Oct 26, 2010 at 5:33 PM, David Hendricks dhendrix@google.comwrote:
On Tue, Oct 26, 2010 at 4:42 PM, David Hendricks dhendrix@google.comwrote:
After a few tries at manually verifying partial writes and realizing that it's awfully tedious to do any exhaustive testing, I hastily threw together a shell script to help automate the process. Since there are others on this list doing similar things, I figured it might be helpful to throw it up here.
Note: It's unfinished and probably has bugs, but I figure it's at least a start, even if only to kickstart a conversation about how to test partial writes in a standard and useful manner.
idwer already noticed at least one issue, so I attempted to correct it along with a couple others.
- Default path for flashrom binary should be "../flashrom" since that is
where a user will typically have built a fresh binary. This can be overridden easily.
- Suppressed some annoying output from "dd" command.
- Implemented better checks for uuencode and pre-installed (assumed to be
stable) flashrom binary.
Signed-off-by: David Hendricks dhendrix@google.com
-- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.