I happened to notice that after I built a debug version of tidfu.dll, I was getting a failure in the Verify after downloading a hex file to my F28069 based board.
I have verified that it is writing and reading the correct number of blocks. I have compared with the .hex file. All is as it should be. I am not reading beyond where I have written.
However, last record of the .hex file that was written, there are 4 bytes that are incorrect. Its always at the same location and same values. All blocks write and read and do not report any errors.
I was wondering if there is something special about those locations and/or these values. Here is a snippet from some output spew.
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37fe9 - read 0xff, expected 0xff
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37fea - read 0xff, expected 0xff
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37feb - read 0xff, expected 0xff
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37fec - read 0x00, expected 0xff <- wrong
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37fed - read 0x7d, expected 0xff <- wrong
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37fee - read 0x90, expected 0xff <- wrong
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37fef - read 0x3b, expected 0xff <- wrong
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37ff0 - read 0xff, expected 0xff
tidfu.cpp(1575) : atlTraceGeneral - Verification at offset 0x37ff1 - read 0xff, expected 0xff
