Fixed writing unaligned sections that may overlap page boundaries of SPI-flash (GF180)

[shaos]

One example that was written incorrectly by old version of utility:

...
@000009B0
00 00 00 00 01 00 00 00 00 00 00 00 02 00 00 00 
03 00 00 00 02 00 00 00 00 00 00 00 01 00 00 00 
00 00 00 00 02 00 00 00 03 00 00 00 02 00 00 00 
00 00 00 00 04 00 00 00 00 00 00 00 02 00 00 00 
06 00 00 00 02 00 00 00 00 00 00 00 04 00 00 00 
00 00 00 00 02 00 00 00 06 00 00 00 02 00 00 00 
12 00 00 00 02 00 00 00 00 00 00 00 08 00 00 00 
00 00 00 00 60 00 00 00 20 00 00 00 60 00 00 00 
40 00 00 00 60 00 00 00 62 00 00 00 E2 00 00 00 
62 00 00 00 60 00 00 00 62 00 00 00 E2 00 00 00 
E0 00 00 00 60 00 00 00 61 00 00 00 60 00 00 00 
61 00 00 00 60 00 00 00 FF FF FF FF 00 00 00 00 

Previously utility tried to write 256 bytes overlapping to next page 0xA00 and that extensive part was not written properly, corrupting beginning of the current page.

Now fixed utility do

• erase the flash (entirely as before);
• read file to buffer (filling holes with FFs and at the end up to the next page boundary);
• write buffer to flash page by page (so no going through page boundaries while writing);
• verify by reading flash page by page (comparing with buffer, not file).

CC @jeffdi

[shaos]

Problem is still happening if page end is located in the middle of the line so I'm going to re-write most of the logic in the script - reading all sections to array, then write this array page by page to SPI-flash and then do verification against this array (so reading from the file will be done only once). It should also fix this issue: #83

[shaos]

Now it's fully fixed and ready to go ( it also fixes #83 )

[shaos]

need to re-create this pull-request because repo is too different now...