Sharpflash Bugs: Difference between revisions
Jump to navigation
Jump to search
(New page: = Bugs = Please leave details of bugs and bug-fixes on this page ... == Partition Overrun == Suspected Bug: If there are bad blocks, writing will overrun, and possibly corrupt next part...) |
(→Bugs) |
||
| Line 1: | Line 1: | ||
= Bugs = | = Bugs = | ||
Please leave details of bugs and bug-fixes on this page ... | Please leave details of bugs and bug-fixes on this page, or chat about them on the discussion tab ... | ||
== Partition Overrun == | == Partition Overrun == | ||
Revision as of 00:29, 20 October 2007
Bugs
Please leave details of bugs and bug-fixes on this page, or chat about them on the discussion tab ...
Partition Overrun
Suspected Bug: If there are bad blocks, writing will overrun, and possibly corrupt next partition.
Temporary fix: run sharpflash -b and reduce length in sharpflash -w command by 0x4000 * number of known bad blocks in partition.
Permanent Fix: Truncate (lose) any blocks which overrun the specified length in the -w command.
Issues: There may be issues with this - I don't understand how the device driver uses the flash - i.e. could it have an unused gap, then use the last block on the partition?