#8955 NORM Not Tri: bad crc file on firmware q2e22

[Zarro Boogs per Child]

#8955: bad crc file on firmware q2e22
------------------------------------+---------------------------------------
           Reporter:  hiro          |       Owner:  frances      
               Type:  defect        |      Status:  closed       
           Priority:  normal        |   Milestone:  Not Triaged  
          Component:  not assigned  |     Version:  not specified
         Resolution:  duplicate     |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------
Changes (by wmb at firmworks.com):

  * status:  new => closed
  * resolution:  => duplicate


Comment:

 There has never been a problem with the actual CRC in the firmware image.

 The problem is a bug in the NAND file reading code in the firmware.  If
 you start with Q2E18 then try to reflash to Q2E22, you will get the CRC
 error message.  That doesn't mean that the Q2E22 image file has bad CRC.
 Q2E18 misreads the file, so Q2E18 *thinks* that the Q2E22 firmware (or in
 fact any firmware image) is bad.

 After you succeed in updating to Q2E22, the next attempt to reflash
 firmware from NAND will work correctly.  To perform the update from Q2E18
 to Q2E22, you can use the workaround in http://dev.laptop.org/ticket/8932
 or you can put the firmware image on a USB stick or SD card and reflash
 from there, without needing a workaround patch.

 Closed as duplicate of #8932

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