December 4, 2016 - 3:23pm, 2914 views
As You can see, Iam able to create som files.But if I restart the module, the files are gone,and the file-tree is emptyWhat is the problemBrrrr
Could you please write more details: what modulre are you using (ATI1 reply), how do you access the file system and create the files (Java MIDlet, MES command line, AT commands etc.). Are you sure that the files are really created on the module?
I am using the FileConnection API 75
CinterionEHS8REVISION 03.001A-REVISION 00.000.14
As You can see from the log, first I just check for existence in the roota: and, then I create.
This is because when I run the second root A: the first check is true.
I assume the two roots share the same pointer a: and A:
Can you share some code for the log you have sent?
Have you verified with MES for example that the files exist after the MIDlet has finished, before the reboot and then after the reboot but before starting the MIDlet again? Is it possible to copy some files to FFS with MES? Does such files also vanish?
Using Mes copy, files persist.
But using java fileconnection, they are not recognised in the first run, only second.
But they are not persistence as You can see from the whole log.
I've gone through your logs and code - please verify if my conclusions are correct.
I can see two passes in your log: one for root a: and another one for root A:. Both letters refers in fact to the same root.
In each pass you call the fcopen method for each file. And inside this method you check if the file exists and if it exist you delete it. If it not exists you create it. So in the first pass the file does not exist, so it is created. In the second pass the file already exists, so it is deleted. As a result after two passes all the files created in the first pass are deleted.
© 2013-2023 Thales DIS AIS Deutschland GmbH - a Telit Cinterion Company