You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This contents of this file are not getting uploaded to the image upon LittleFS filesystem build and flashing.
I've got 3 other files, that are not 0 bytes on the disk and they are getting uploaded perfectly fine.
I'm using PlatformIO Home 3.3.3 and core 5.1.0 with Espressif v2.6.3.
EDIT: that's not it. I created a copy of the file (config2.json), which is 0 bytes on the disk and that's getting uploaded properly. config.json is just not getting through for some reason.
I looked at the binary file, the config.json file itself is present in the image (with the contents) but the file table lists this file as 0 bytes. Removing all the other files still gives a 0 byte file size
Building with a block size of 4096 creates the proper binary that is readable with mklittlefs -l littelfs.bin. The default command creates an unreadable file.
The text was updated successfully, but these errors were encountered:
I've got a config.json file that is 0 bytes on the disk. (A nice video explaining 0-byte files here: https://www.youtube.com/watch?v=q6eCv0plATg)
This contents of this file are not getting uploaded to the image upon LittleFS filesystem build and flashing.
I've got 3 other files, that are not 0 bytes on the disk and they are getting uploaded perfectly fine.
I'm using PlatformIO Home 3.3.3 and core 5.1.0 with Espressif v2.6.3.
EDIT: that's not it. I created a copy of the file (config2.json), which is 0 bytes on the disk and that's getting uploaded properly. config.json is just not getting through for some reason.
I looked at the binary file, the config.json file itself is present in the image (with the contents) but the file table lists this file as 0 bytes. Removing all the other files still gives a 0 byte file size
Building with a block size of 4096 creates the proper binary that is readable with mklittlefs -l littelfs.bin. The default command creates an unreadable file.
The text was updated successfully, but these errors were encountered: