#9436 NORM Not Tri: Flash failed to program correctly

Zarro Boogs per Child bugtracker at laptop.org
Thu Aug 13 16:41:03 EDT 2009


#9436: Flash failed to program correctly
------------------------------------+---------------------------------------
           Reporter:  wad           |       Owner:             
               Type:  defect        |      Status:  new        
           Priority:  normal        |   Milestone:  Not Triaged
          Component:  not assigned  |     Version:  1.5-A2     
         Resolution:                |    Keywords:             
        Next_action:  never set     |    Verified:  0          
Deployment_affected:                |   Blockedby:             
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by wmb at firmworks.com):

 bad.rom exactly matches Q3A07.ROM except for differences in the
 manufacturing data area.  Q3A07.ROM contains all FFs in the mfg data
 block, bad.rom contains non-FF data from 0xefd00 .. 0xeffff.  The data
 there doesn't look like valid mfg data, so I'm guessing that it is
 leftover from a conventional BIOS image that was in that SPI FLASH at some
 point.

 From the data provided, I can't explain all the symptoms, but it's pretty
 clear that this is not a problem with Q3A08, as the data in the ROM was
 pristine Q3A07 modulo the mfg data thing.

-- 
Ticket URL: <http://dev.laptop.org/ticket/9436#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list