#1905 BLOC Trial-3: Field Return: flash corruption - OpenFirmware complaining of 'unknown node type 2006'.

[Zarro Boogs per Child]

#1905: Field Return: flash corruption - OpenFirmware complaining of 'unknown node
type 2006'.
-----------------------+----------------------------------------------------
  Reporter:  dwmw2     |       Owner:  wad     
      Type:  defect    |      Status:  assigned
  Priority:  blocker   |   Milestone:  Trial-3 
 Component:  hardware  |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by Luna):

 * cc: luna (removed)
 * cc: Luna.Huang at quantatw.com, Elvis.Wu at quantacn.com (added)

Comment:

 Dear David,
  After talking over with Elvis, I would like to tell you the results as
 follows.
  Problem 1 is known by you and Problem 2 is the test I did.

 According to the test results, I assume there may be some problem with
 nand flash erasing when the action is executed under OFW.

 Please feel free to tell me if there is any problem.

 Thank you.
 Luna
 ============================================================

  Problem 1: ( Tested on the same CL1 )

  If I execute command " nandwrite -p /dev/mtd" in OS, the CL1 will hang up
 in the process of   nand write.
  Moreover, if I execute "copy-nand" under OFW, the nandwrite action keeps
 going even  there is an error message (Refer to the attached:problem1-1,
 problem1-2.) and the machine can go into sugar successfully.
  But it will show a message: "Unsupported node type 2006" after reboot
 several times.

  I think the bad blocks are not marked well so it gets chance to write
 into the blocks which
  have problem


  Problem 2: ( Use two new Nand flash chips on the same machine to test)

 I used two methods for the first chip:

   (1) Put the chip into the ST nand flash test machine which comes from ST
 Cor. to get the initial bad block table which has 16 initial bad blocks.

   (2) Solder the chip on the board first. Boot OLPC to OFW and execute
 command "select /nand " "scrub" "test /nandflash" in order.
         It comes out 5 bad blocks only to skip and the BBTables is set on
 the latest two blocks (0x1ffe 0x1fff)

   (3) Then I move the chip into the ST nand flash test machine and scanned
 it again.
       There are 7 bad blocks in the chip. You can see the attachment
 (problem2chip1-1,problem2chip1-2) to get the bad address.

 The second chip: (attachment: problem2chip2-1 ~ problem2chip2-3)

   (1) Put another new chip into the ST nand flash test machine to get the
 initial bad block table which has one bad block (0x069e).

   (2) Solder the chip on the board first. Boot OLPC to OFW and execute
 command "test /nandflash". It comes out 1 bad block (0x069e) and BBTable
 is also set on the latest two blocks

   (3) Then I boot from USB. Execute command "flash_eraseall -j /dev/mtd0"
 to get the result with four more bad blocks (0x3ff80000 0x3ffa0000
 0x3ffc000 0x3ffe000).

   (4) Reboot OLPC to OFW to execute command "test /nandflash". Get one bad
 block (0x069e).

   (5) Execute command "select /nand " "scrub" "test /nandflash" in order.
 It comes out no bad block and BBTable is set on the latest two blocks.

 According to the test results, I assume there may be some problem with
 nand flash erasing when the action is executed under OFW.

 Please feel free to tell me if there is any problem.

 Thank you.
 Luna

-- 
Ticket URL: <https://dev.laptop.org/ticket/1905#comment:33>
One Laptop Per Child <http://laptop.org/>