I support about 100 students using ATMega128 with bootloaders and we use BLIPS as the iploader. This has worked pretty well. However recently I had two failures where it goes through the motions, but fails to verify. If the Verify after program box is unticked for all intentional purposes one would think that the new program has been uploaded. However the old program remains (without any damage) and runs quite happily.
The bootloader is firmly in control and can be used for executing the application program etc.
The number of erasures for each was about 100 times, so it is not a exceeded maximum erasure issue.
I will be trying to read the code out of these controllers, to see what has happened to the bootloader to fail in this weird manner, before I try & reflash them.
Has anyone else experienced failures of this type.
Lee de Vries