Hi!
I am developing some projects and today there was a very strange behavior. My current project is using a XBee to transmit new firmware. The binary chunks where written to a file at LocalFileSystem. When finished and checksums are OK, the file is getting remaned to a real *.bin file. So, here comes the trouble. A real "rename" implementation is still pending. But there is an alternative:
Create File with new Filename, copy old file content into new file, remove old file. OK, no problem, works.
But today I uploaded a new firmware, upload successfull, renaming... Error! It could not create the new empty file !?
The code providing file upload and flashing was not touched by me since months. The problem must be the new code, but that is not using any file system functionality !?
So I reduced the project (200KB source code) to this small one:
http://mbed.org/users/BlazeX/code/Strange_Test/
It should to the same as the LocalFileSystem demo:
https://mbed.org/handbook/LocalFileSystem
But is does'nt.
Why?
Hi! I am developing some projects and today there was a very strange behavior. My current project is using a XBee to transmit new firmware. The binary chunks where written to a file at LocalFileSystem. When finished and checksums are OK, the file is getting remaned to a real *.bin file. So, here comes the trouble. A real "rename" implementation is still pending. But there is an alternative: Create File with new Filename, copy old file content into new file, remove old file. OK, no problem, works.
But today I uploaded a new firmware, upload successfull, renaming... Error! It could not create the new empty file !? The code providing file upload and flashing was not touched by me since months. The problem must be the new code, but that is not using any file system functionality !?
So I reduced the project (200KB source code) to this small one: http://mbed.org/users/BlazeX/code/Strange_Test/
It should to the same as the LocalFileSystem demo: https://mbed.org/handbook/LocalFileSystem
But is does'nt.
Why?