AnoopPuthanveetil / yaffs2utils

Automatically exported from code.google.com/p/yaffs2utils
GNU General Public License v2.0
0 stars 1 forks source link

Ignore OOB area #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I have downloaded the image directly from device, just to examine the contents.
The problem is that the image does not contain extra +64 bytes at the end of 
every chunk.

Is it possible to extract contents while skipping OOB area? Or maybe generate 
OOB from the downloaded image?

Original issue reported on code.google.com by megapr...@gmail.com on 7 Apr 2012 at 6:18

GoogleCodeExporter commented 9 years ago
This is a feature request, not a defect, sorry.

Original comment by megapr...@gmail.com on 7 Apr 2012 at 10:48

GoogleCodeExporter commented 9 years ago
At this moment, the unyaffs2 still cannot extract the image dumped directly 
from the evice (it is still in progress). 

When processing the contents of a file, unyaffs2 need the information in the 
spare(oob) area to extract the correct size of the data chunk. The tool, such 
as nanddump, should has the capacity to dump a image contains oob info, hasn't 
it!?

Original comment by penguin.lin on 9 Apr 2012 at 8:39

GoogleCodeExporter commented 9 years ago
When extracting the contents of a file, the information in the spare area are 
required to get the correct size of the data chunk. The tool, such as nanddump, 
should has the capacity to dump a image contains oob info.

If there are no other concern, I will close this issue and set as "won't fix"

Original comment by penguin.lin on 27 Jun 2012 at 8:59

GoogleCodeExporter commented 9 years ago

Original comment by penguin.lin on 27 Jun 2012 at 9:08