#8932 BLOC 8.2.1: OFW Q2E18 can't reflash from NAND in non-secure mode (was: OFW Q2E18 can't reflash from NAND)
Zarro Boogs per Child
bugtracker at laptop.org
Tue Nov 4 21:38:18 EST 2008
#8932: OFW Q2E18 can't reflash from NAND in non-secure mode
-------------------------------------------+--------------------------------
Reporter: wmb at firmworks.com | Owner: wmb at firmworks.com
Type: defect | Status: assigned
Priority: blocker | Milestone: 8.2.1
Component: ofw - open firmware | Version: not specified
Resolution: | Keywords:
Next_action: test in build | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-------------------------------------------+--------------------------------
Changes (by wmb at firmworks.com):
* cc: rsmith at laptop.org (added)
* status: new => assigned
* next_action: never set => test in build
* milestone: Not Triaged => 8.2.1
Comment:
Fixed by svn 994.
The JFFS2 file reader was using the wrong address for "replaying" the file
data in some cases. It didn't affect booting, which uses the "load-base"
buffer, but it did affect "flash", which uses a different buffer. The
incorrect replay address was 0, and if the file was larger than 0xa0000,
the portion of the file at offsets 0xa0000..0xbffff was 0, because that
range of memory is not really memory in E-series firmware (it is reserved
for "DOS hole" devices).
Workaround:
ok dev /jffs2-file-system
ok patch 0 -1 ?play-log
ok patch 0 -1 ?play-log
ok patch -1 0 ?play-log
ok dend
After that patch, the flash command will work properly.
Another workaround is simply to copy the file onto a USB stick or SD card
and reflash from there. Another workaround is to reflash using the secure
method.
--
Ticket URL: <http://dev.laptop.org/ticket/8932#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list