#5870 NORM Never A: Cleanup error handling in OFW NAND driver
Zarro Boogs per Child
bugtracker at laptop.org
Mon Jan 7 18:54:26 EST 2008
#5870: Cleanup error handling in OFW NAND driver
----------------------------------+-----------------------------------------
Reporter: wmb at firmworks.com | Owner: wmb at firmworks.com
Type: defect | Status: closed
Priority: normal | Milestone: Never Assigned
Component: ofw - open firmware | Version:
Resolution: fixed | Keywords:
Verified: 0 | Blocking:
Blockedby: |
----------------------------------+-----------------------------------------
Comment(by wmb at firmworks.com):
To test the fix for subproblem 1:
a) Install Q2D08.
b) Boot to the ok prompt, e.g. with a developer key or an unsecured laptop
c) Type
{{{
ok dev /nandflash
ok patch 0<> 0= get-existing-bbt
ok dend
ok dir n:\
}}}
You should see a normal NAND directory listing.
Simulating the problem on a system with old firmware is tricky, so a
recipe is not given here.
To test subproblem 2, using an unsecured or developer key laptop:
a) Obtain an OS image and corresponding .crc file, e.g os653.img and
os653.crc.
b) Download the attached "empty.zip" and prepare an extended .crc file by
concatenating the existing .crc file with "empty.crc", as follows:
{{{
$ unzip empty.crc
$ cat os653.crc empty.crc >os653x.crc
}}}
c) Put all three files - os653.img, os653.crc, and os653x.crc - in the
root directory of a USB key.
d) Reboot to the ok prompt and install the NAND image:
{{{
ok copy-nand u:\os653.img
}}}
e) Verify that the copy succeeded:
{{{
ok crc-nand u:\os653.crc
}}}
f) Verify the fix with:
{{{
ok crc-nand u:\os653x.crc
}}}
The verification should run for awhile, then eventually stop with the
message:
{{{
No more good NAND blocks
}}}
--
Ticket URL: <http://dev.laptop.org/ticket/5870#comment:2>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list