#11464 NORM 1.75-fi: XO-1.75 B1 EC write protected while SPI FLASH writable
Zarro Boogs per Child
bugtracker at laptop.org
Tue Nov 15 21:05:03 EST 2011
#11464: XO-1.75 B1 EC write protected while SPI FLASH writable
-------------------------------------------+--------------------------------
Reporter: Quozl | Owner: Quozl
Type: defect | Status: new
Priority: normal | Milestone: 1.75-firmware
Component: ofw - open firmware | Version: 1.75/1.5/1.0 Software Build os883 aka 11.3.0
Resolution: | Keywords:
Next_action: reproduce | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-------------------------------------------+--------------------------------
Description changed by Quozl:
Old description:
> Occasionally a unit has a write protected EC even though the SPI FLASH is
> not write protected. The condition persists until battery and external
> power are removed.
>
> The symptom up to Q4C04, but not Q4B10, is failure to ''flash'', with
> output:
>
> {{{
> Checking integrity...
> EDI byte in timeout
> ok
> }}}
>
> From Q4C05 the symptom will be successful ''flash'' but additional
> warnings:
> {{{
> Checking integrity
> Write Protected EC
> SPI FLASH is type 34 - Macronyx
> ...
> }}}
>
> An early step in ''flash'' is try to hold the EC in reset. This feature
> (#11215) was introduced in Q4B10, but broke in Q4B11, and will be
> reintroduced in Q4C05. This depends on the security flip-flop not being
> triggered by ''protect-fw'', which in turn depends on the ''wp'' tag not
> being present.
>
> Seen on two B1s in the past few days.
New description:
Occasionally a unit has a write protected EC even though the SPI FLASH is
not write protected. The condition persists until battery and external
power are removed.
The symptom up to Q4C04, but not Q4B10, is invisible.
From Q4C05 the symptom will be successful ''flash'' but additional
warnings:
{{{
Checking integrity
Write Protected EC
SPI FLASH is type 34 - Macronyx
...
}}}
An early step in ''flash'' is try to hold the EC in reset. This feature
(#11215) was introduced in Q4B10, but broke in Q4B11, and will be
reintroduced in Q4C05. This depends on the security flip-flop not being
triggered by ''protect-fw'', which in turn depends on the ''wp'' tag not
being present.
Seen on two B1s in the past few days.
--
--
Ticket URL: <http://dev.laptop.org/ticket/11464#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list