@MarkL, @analogRF thanks for letting me know that the warning I get is not the expected behavior.
My guess is that the contents of your TDS3ENG module is not quite right. You might want to go back and double-check against the TDS3UAM-TDS3HEX.pdf document that was posted to this thread.
My module was indeed not quite right. The problem was that the PDF (as well as the tds3eng.hex file posted to this thread) only specifies the values of the first 256 Bytes, and I filled the remaining bytes above them with
FF instead of
00.
I was lead to do that by extrapolating from the following sentence in the PDF:"...the second writes the entire 256 byte filling in FF in all unused locations, just in case you made an Oops and forgot the erase".
It is interesting that this makes no difference for the TDS3UAM, but causes the warning message with the TDS3ENG.
Thus, to prevent anybody else from making the same mistake, I suggest to further clarify the instructions in the TDS3UAM-TDS3HEX.pdf as follows:
1. Wherever it says erase it means fill with
00.
2. The sentence "Only difference is that the first block relies on you having erased the EEPROM, the second writes the entire
256 byte filling in FF in all unused locations, just in case you made an Oops and forgot the erase." should be ignored.
Indeed, even when using the second block, one has to also fill all bytes above the first 256 with
00. For example, by first erasing to all
00.
My thanks to the author of TDS3UAM-TDS3HEX.pdf for this amazing document!