File: file not found! unhandled exception

[praveenravichandran]

Team,
I have implemented the file concept in my project. Implementation is working fine in windows simulator but It is not working in the esp32 target. Am getting the below error in modFIle. C
\modFile.c (76) # Break: File: file not found!. I have added the file configuration in manifest as below "esp32/moddable_zero": { "modules": { "*": "$(MODDABLE)/modules/files/file/esp32/*" }, "config": { "file": { "root": "./" } } }

Could you please help on this

[wilberforce]

The root would need to be "/spiffs/". If you have a recent build I think this is now the default.

[praveenravichandran]

So you mean that I should give "/spiffs/" instead of ./ in root.? Please correct me if I'm wrong

[lprader]

So you mean that I should give "/spiffs/" instead of ./ in root.?

That's correct.

The files manifest includes the root for each target platform in the config object (so you don't have to add it yourself). You can access this in your script as done in the files example.

[praveenravichandran]

Thanks much Iprader and Wilberforce. Will try that and update here

[praveenravichandran]

We tried adding the "/spiffs/" in the manifest and also declared the root config. Still the error persists :(

[lprader]

Try running the files example. It works for me on the ESP32. Does it work for you?

[praveenravichandran]

Will check that

[lprader]

If the files example doesn't work for you, let me know. Otherwise, follow the same pattern it uses to get the correct root by taking these steps:

1. In your app's manifest, include the files manifest.

   "include": [
   	/*other includes here*/
   	"$(MODDABLE)/modules/files/file/manifest.json",
   ],
   

2. In your app's script, import the config object.

   import config from "mc/config";
   

3. Use config.file.root as the root. Make sure you include the root in file names.

   const root = config.file.root;
   
   let file = new File(root + "example.txt");
   

[praveenravichandran]

I think file example is working. The word think is put here because it doesn't show any error while burning the application and nothing was showing in the xsbug logs too 😁.

[lprader]

Hmm...you should see messages traced to the xsbug console when you run the example. Make sure you're running a debug build. To do that, add -d to your build command. For example:

mcconfig -d -m -p esp32

[praveenravichandran]

Yeah, I always used to run in debug mode. But I couldn't able to figure it out on why its being not shown in log panel. Even I checked by keeping breakpoints, it doesn't even stopped

[lprader]

Based on your original comment, it sounds like you see messages (or at least errors) traced to the console when running other applications. Is that true?

And do you hit breakpoints in other examples? For example, if you run helloworld, do you hit the breakpoint and then see "Hello, world - sample" traced to the console after you press the run button?

[praveenravichandran]

Exactly!

[lprader]

Can you share a screenshot of xsbug when you run the files example on the ESP32 using these commands?:

cd $MODDABLE/examples/files/files
mcconfig -d -m -p esp32

You should get a machine tab (like the one circled in red in the image below). When you click that tab, you should see the instrumentation panel (and it should be updating the values of each row every second or so).

[praveenravichandran]

Yeah I will post it here.

[praveenravichandran]

[lprader]

Sorry, now I'm a little confused--you originally said:

it doesn't show any error while burning the application and nothing was showing in the xsbug logs too

That screenshot clearly shows messages traced to the console and an error. So that doesn't seem to be a problem. Is that correct?

[praveenravichandran]

Iprader you are right, Initially I didn't found any of the trace logs as mentioned above. But after you asked for the screenshot I just try by changing the environment variable path of xsbug that made the debugger .There were something weird at that time. I suspect that I didn't get any error message because xsbug is not launched at that time. However my main issue in the board file not found exists.

[lprader]

Alright, gotcha. Glad that part is solved.

As for the "file not found" issue, what kind of ESP32 board are you using? In your very first comment you mentioned you added a config object for the esp32/moddable_zero target in your manifest. That target is meant for use with an ESP32 paired with a SPI display. Is that what you're using?

[praveenravichandran]

Exactly

[lprader]

Would you mind sharing your application so I can see if it works for me?

[praveenravichandran]

files.zip

[wilberforce]

@praveenravichandran

When did you get your Moddable sources? - they could be out of date and changes made since you pulled your copy of the repository...

[praveenravichandran]

Might be, I have the code which has been last updated on May 1st.

[praveenravichandran]

Meanwhile, I don't see any commits regarding the file issues @wilberforce

[lprader]

Ah-ha. I understand now.

You are attempting to read from a file that doesn't exist on the device. You have a preferences.json file in your source folder, but you don't specify in your manifest that it should go on the device.

[lprader]

I'm not sure how to include a JSON file in your build (I'll look into that tomorrow), but if you want to store preferences like the ones in preferences.json, I recommend you use the Preference class anyways.

[praveenravichandran]

Okay, So that means If I read and write in a single program it doesn't requires any configuration in manifest and it automatically takes from the root path. Correct me if my understanding wrong

[praveenravichandran]

Thank you Iprader, Will definitely go through that preference class too.

[lprader]

Okay, So that means If I read and write in a single program it doesn't requires any configuration in manifest and it automatically takes from the root path. Correct me if my understanding wrong

No files are ever added to the device automatically. You have to specify which files go onto the device in the manifest. Or you can create them at runtime, as the files example does.

From the File class constructor documentation:
If the file does not exist, an exception is thrown when opening in read mode. When opening in write mode, a new file is created if it does not already exist.

If you look at the source for the files example, you can see there are no files other than main.js and manifest.json. But in main.js, an instance of the File class is created with the write argument set to true. Because this file does not exist, it is created. Then it is written to.

file = new File(root + "preferences.json", true);
file.write(JSON.stringify(preferences));
file.close();

[praveenravichandran]

Got it!

[praveenravichandran]

@lprader You were right. It is working when I tried it by deleting the get data from preference part alone.

[praveenravichandran]

For taking the external JSON file, whether we can try it out just by giving the folder name where the JSON file is put under modules of manifest .

[phoddie]

Closing, as this appears resolved.