Files
OpenCellular/include
Randall Spangler b70183a9bd Implement persistent flash write protect settings
This uses the last bank of flash to hold persistent settings, and
looks at the write protect GPIO to decide whether to protect the chip
at boot (chrome-os-partner:7453).

For ease of debugging, I've temporarily hacked this so flash uses the
RECOVERYn signal (dut-control goog_rec_mode:on) to enable WP instead
of the write protect signal; this works around chrome-os-partner:8580.

Also note that if you write protect any blocks even temporarily,
you'll need to do a power-on reset to clear them before you can
reprogram the flash.  See chrome-os-partner:8632.  At the EC console,
"hibernate 1" will do that, or you can just yank the power.

This also fixes a bug in the flash write and erase commands, where
they weren't properly detecting failure if you attempted to modify a
protected block (missed an interrupt reason...)

New "flashwp" console commands work.  LPC commands need reworking.

Signed-off-by: Randall Spangler <rspangler@chromium.org>

BUG=chrome-os-partner:8448
TEST=manual

Change-Id: I49c38cc25c793094ae3331a4586fda0761b4bac6
2012-04-02 10:57:03 -07:00
..
2012-03-16 14:02:59 -07:00
2012-02-10 16:12:56 -08:00
2011-12-07 19:10:02 +00:00
2011-12-07 19:10:02 +00:00
2012-01-13 10:34:09 -08:00
2012-03-06 12:07:22 +08:00
2012-02-02 20:51:45 +08:00
2012-01-11 11:37:55 -08:00
2012-03-15 12:42:11 -07:00
2011-12-07 19:10:02 +00:00
2011-12-07 19:10:02 +00:00
2011-12-07 19:10:02 +00:00
2011-12-07 19:10:02 +00:00
2012-01-25 18:23:48 +00:00
2012-03-16 10:40:52 +08:00
2012-03-16 10:40:52 +08:00
2011-12-07 19:10:02 +00:00
2012-01-19 10:54:37 +08:00
2012-01-31 22:29:13 +00:00
2011-12-07 19:10:02 +00:00