Fatfs partition not recognized in ESP32

[danimasa]

Hello

I'm trying to mount a FATFS filesystem in an ESP32, I generate the binary and upload it to the vfs partition but if I try to do a simple mp_vfs_stat I keep receiving NLR jump failed, val=0x3ffe58b0 error.

Isn't the vfs partition mounted in root fs at startup?
Frozen files are kept in a different partition? Because boot.py is running correctly

[jimmo]

I'm trying to mount a FATFS filesystem in an ESP32, I generate the binary and upload it to the vfs partition but if I try to do a simple mp_vfs_stat I keep receiving NLR jump failed, val=0x3ffe58b0 error.

The NLR jump failed shouldn't be possible no matter what you're doing, so it sounds like you're definitely hitting a bug somewhere if you're only using Python.

I'm a little bit unsure what you mean though. What does "generate the binary and upload it to the vfs partition". Are you generating a FAT filesystem and then using esptool to write it to the correct offset in flash?

mp_vfs_stat would suggest that you're writing something in C. So I think we need more info -- where are you calling this from?

Isn't the vfs partition mounted in root fs at startup?

Yes. See https://github.com/micropython/micropython/blob/master/ports/esp32/modules/_boot.py -- the flashbdev.py uses Partition.find(Partition.TYPE_DATA, label="vfs").

Frozen files are kept in a different partition? Because boot.py is running correctly

Frozen files are not in an ESP32 partition. Rather they're part of the application code (the freezing process turns it into a .c file which is compiled and linked).

[danimasa]

Really, after putting the code in a exception handling context a different error appears: OSError: [Errno 2] ENOENT but I yet don't understand the reason of the error.

[robert-hh]

ENOENT is raised, when a file is not found. Did you create the file system on the partition?

[danimasa]

ENOENT is raised, when a file is not found. Did you create the file system on the partition?

I was expecting that the boot.py would create it to me, because of it I'm running it first. Should I have to create it using the esp32 libraries?

Really the file was not there, I used the mp_vfs_listdir to list the files in the root and it only shows the boot.py file.

[karfas]

Please read the (frozen) modules in https://github.com/micropython/micropython/tree/master/ports/esp32/modules.

The default _boot.py searches (in flashbdev.py) for a partition labeled either "vfs" or "ffat" (from esp32/partitions*.csv) and happily creates a LFS2 file system here (even for "ffat" labeled partitions) if no filesystem already exists.
If micropython should create a FAT fs for you, you will need to alter inisetup.py accordingly.
If you generate the FAT fs as an image, you need to flash your filesystem to a correct labeled partition.

[danimasa]

I found the problem, the image I was uploading to esp32 was corrupted, I generated the image again and now the _boot.py was capable to mount it correctly. Thank you.