#11316 NORM 1.75-fi: "Reflash returned, unexpectedly" seen upgrading to Q4B11

[Zarro Boogs per Child]

#11316: "Reflash returned, unexpectedly" seen upgrading to Q4B11
-------------------------------------------+--------------------------------
           Reporter:  greenfeld            |       Owner:  wmb at firmworks.com                
               Type:  defect               |      Status:  new                              
           Priority:  normal               |   Milestone:  1.75-firmware                    
          Component:  ofw - open firmware  |     Version:  Development build as of this date
         Resolution:                       |    Keywords:                                   
        Next_action:  diagnose             |    Verified:  0                                
Deployment_affected:                       |   Blockedby:                                   
           Blocking:                       |  
-------------------------------------------+--------------------------------
Description changed by greenfeld:

Old description:

> 0. Attach your XO-1.75 with Q4B10 to a serial terminal if you want to log
> this.
>  1. Install 11.3.0 os880 on an XO-1.5 said XO-1.75 with the four-button
> secure approach.
>  2. Hold down the "X" and "Checkmark" keys while the system restarts to
> force checking the bootfw.zip file in secure mode.
>  3. The system will reflash to Q4B11, verify the results, and quickly
> print "Reflash returned, unexpectedly" immediately before rebooting.
>
> Secure mode may not be necessary, but it was used the one time I have
> seen this so far.

New description:

 0. Attach your XO-1.75 with Q4B10 to a serial terminal if you want to log
 this.
  1. Install 11.3.0 os880 on an XO-1.75 with the four-button secure
 approach.
  2. Hold down the "X" and "Checkmark" keys while the system restarts to
 force checking the bootfw.zip file in secure mode.
  3. The system will reflash to Q4B11, verify the results, and quickly
 print "Reflash returned, unexpectedly" immediately before rebooting.

 Secure mode may not be necessary, but it was used the one time I have seen
 this so far.

--

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