Hi,
It seems to us that erasing the bad file from a PC with Ubuntu was the simpliest solution
It is not clear where the problem is.
My point of vue is the cache or the file system of the mbed could sometimes returns bad information to the Windows OS,
It could be also a problem with the size of the cluster on the mbed which is different with the windows one,
and as most of my program are very small, the WFP go crazy with this small file. Anyway, it is only fiction speaking
However, some of our students have succeeded to remove the issue using the format options on windows USB drive!
Clearly, as the vital part of the mbed is protect against writing, formating can only access to the user part, so do not worry about formating
But, I have try it and as my mbed wasn't able to clearly connect to Windows,
the size of the mbed didn't correspond to the options of the format options. (the proposed size was more like having an old 2Mo USB drive)
So, better go on Ubuntu or another kind linux to solve the problem.
Best regards,
Warning if you are using windows, the Windows File Protection (WFP) system (http://support.microsoft.com/kb/222193/en-us)can bug and refuse to finish the file transfer (a small windows opens during the transfer and doesn't close).So, if you unplugged the mbed during such problem, you can destroy the file system of the mbed...
It happened to my mbed: two new files appear : USBC 3 997 696KB and USBC-ZL. 753 664KB)and the .bin file can no more be remove or updateSo the mbed works with this only program, and I have found no solutions for the moment to solve this issue...