View Single Post
Old 01-25-2013   #74
baileyscream
Senior Member
 
baileyscream's Avatar
 
Join Date: Feb 2011
Posts: 1,485
Likes: 531
Liked 1,004 Times in 503 Posts
Mentioned: 485 Post(s)
Tagged: 0 Thread(s)
Originally Posted by defyboy View Post
Thank you for this most useful tool, I'm glad my painstaking reverse engineering and documentation came in handy for someone.

I would like to upload this to the wiki's download section if you don't mind.

Also, just a comment on checking the 0x00 and 0xFF areas, I have a few samples where areas that usually are 0xFF are indeed 0x00. I am not sure what conditions cause this but I assume it's from different boundaries from previous firmwares.

Basically, areas that are 0xFF will be so because NOR flash memory in it's "erased" state contains all 1's, a write operation is able to change a 1 to a 0 however a block erase operation is required to revert 0's to 1's. Areas that are 0x00 are simply where blank data has been written over an erased block, usually to fill up a boundary.

As for a final report, it would be nice to give a pass or warnings on what specific parts of flash are incorrect.
is the download section getting re-opened then?
otherwise its a bit pointless moving it there if it cannot be accessed.

^^^dont take that as a piss take or anything. its just a question
baileyscream is offline   Reply With Quote
Likes: (1)