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.