#11210 NORM 1.75-ha: eMMC dead in XO 1.75 B1

[Zarro Boogs per Child]

#11210: eMMC dead in XO 1.75 B1
------------------------------------+---------------------------------------
           Reporter:  jnettlet      |       Owner:                        
               Type:  defect        |      Status:  new                   
           Priority:  normal        |   Milestone:  1.75-hardware         
          Component:  not assigned  |     Version:  1.75-B1               
         Resolution:                |    Keywords:  eMMC, hardware failure
        Next_action:  never set     |    Verified:  0                     
Deployment_affected:                |   Blockedby:                        
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by Quozl):

 Tested ''erase-blocks'' in XO-1.75 B1 with board revision 1B2.  This
 system does not exhibit the failure of "test int:0" normally.

 The error generated by ''erase-blocks'' is '''not''' the same as in the
 ticket description, in that the failing command is ERASE_WR_BLK_START (CMD
 32), which is the first of three commands in the erase sequence, and is
 the command that specifies the starting block.

 After this failure, no further commands seem to be possible, the timeout
 condition is persistent, until power cycle.

 ----

 @jnettlet, if the "test int:0" still fails after a power cycle, with a
 "Recent commands (decimal): 17", then I agree that the device is faulty.
 CMD17 is READ_SINGLE_BLOCK, and the argument of zero means it is the first
 block of the device.

 Just wondering; what method have you been using to force a shutdown during
 graphics driver development?

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