-
• #2
I surprised how this seems to have zero views in the forum list. Is it true that no one wants a bigger Storage area? :P
-
• #3
Mon 2021.10.18
'I surprised how this seems to have zero views'
It is more likely that as the ESP32 is an unsupported board, most of the community members support this project with their purchase of an authentic Espruino board.
http://www.espruino.com/Other+Boards
https://www.patreon.com/espruino -
• #4
It is more likely that as the ESP32 is an unsupported board, most of the community members support this project with their purchase of an authentic Espruino board.
There are ESP32 / 8266 community members -- so I'm guessing that people just aren't interested in a Storage module with a larger capacity, which is perfectly OK. I just posted to see the interest and if anyone had discussed it.
I'll have a look at the module at some point myself I guess.
G
-
• #5
I surprised how this seems to have zero views in the forum list.
This is some forum issue, noticed this with another topics too. The number can take some time to update - even one day or more.
As for the topic - I'm not using Espruino with ESP32 but looks like the size and address of storage is set here https://github.com/espruino/Espruino/blob/master/boards/ESP32.py#L60
and it matches js_code partition here https://github.com/espruino/Espruino/blob/master/targets/esp32/Changes_V3.1/partitions_espruino.csv
Interesting that there is another 640KB partition called storage right after it so maybe esp32 has another filesystem in flash there? Anyway this partition table is sized for 4MB of flash. -
• #6
I believe you can use the FS module to access some extra storage.
Format the extra partition using http://www.espruino.com/Reference#l_E_flashFatFS
you can then use the extra space availible on the ESP32 board. -
• #7
Hello everyone, I've also encountered this dilemma. But my solution is to use the additional partitioning method from http://www.espruino.com/Reference#l_E_flashFatFS. By accessing https://www.espruino.com/ESP32#flash-map-and-access and using fs.writeFileSync to resolve the issue, but the problem is that this method makes the storage unusable. I hope to be able to use the additional flash memory together with the storage.
-
• #8
Additionally, I've encountered an issue when using the fs module. Specifically, when I call the fs.appendFileSync(filename, data); method and I repeatedly execute this code block within a setInterval function, I'm experiencing issues with missing or inconsistent file writes. Could you please assist me in resolving this when you have the time?
function downloadData(filename) { require('http').get("http://xxx.com/pic/"+filename, function(res) { var i = 0; res.on('data', function(data) { i+=1; console.log('download:' + filename + " chunk =>" + i + '...'); fs.appendFileSync(filename, data); }); res.on('close', function(data) { console.log("Connection closed"); console.log(fs.readdirSync()); }); }); }
Hi everyone. I've been reading the posts on GitHub and here in the forums about making the storage module space bigger. It seems that the limitation is that it is "memory mapped"? But what does that mean "memory mapped"? I couldn't find exactly what that meant?
My storage area shows about maybe 220K free? I find that small, considering I have 4-16MB of flash space typically.
Is it possible to expand? I saw someone else ask about this somewhere, but no one responded to them.
Thanks! :)