Working on a project with an ESP32-S3 N16R8.

If I compile and upload my sketch using the default partition scheme of 'Default 4MB with spiffs' all is well.

When I add a partitions.csv file to my project folder (where the *.ino lives) with the following content (which is a slightly changed version of the default.csv):

# Name,     Type, SubType,  Offset,  Size, Flags
nvs,        data, nvs,      0x9000,  0x5000,
otadata,    data, ota,      0xE000,  0x2000,
app0,       app,  ota_0,    0x10000, 0x80000,
app1,       app,  ota_1,    0x90000, 0x80000,
spiffs,     data, spiffs,   0x110000,0x80000,
sensordata, data, undefined,0x190000,0x270000, 

Then the build shows the correct new size for app0 ('Used X% of a 524288 byte maximum', which is the 0x8000) so the build process has noticed the partitions.csv file but when I try to upload the sketch esptool fails with

No such file or directory Quote:


That FlashTry.ino.partitions.bin is preceeded by a path but whatever I try I can't get that path to be displayed here in this post.

What am I missing? From the documentation I understood that just having the partitions.csv file (in the correct place) should be enough. Right?

Yes, I confirm that exactly as I said in my opening post the file is called partitions.csv and it's in the very same directory as my .ino file.

I also got an email telling me to enable the options at the top of the page and attach that as output but I had already done that by emailing it.

That's odd because the very page you link to - and which I had read before of course - mentions that

"When type is data, the subtytpe can be specified as..." and 1 of the listed predefined data subtypes is

"undefined" (0x06)

But if that for whatever reason doesn't work, what else would be a good subtype to store sensordata to? All the other listed ones have a specific meaning that is not applicable to my sensordata which will be a lot of binary data.

I can confirm that leaving subtype blank, or using nvs does work and solves my problem. Thanks for your help.