Thank You

@robert-hh Many thanks for this detailed analysis and testing. The results are promising, based on your tests and also information from others I think it is clear that enabling wear-leveling does not have any significant negative effect.

@jcaron Thanks for the clarification. Okay, Then how about the second part of my question? If I import a library, does the whole library (including unused functions) get loaded into / waste memory? Thanks, Troy

@edward-dimmack said in Storing variables in between deepsleep: @elizar Do you mean to a file on an SD card? Because we are not using an SD card in this application. You can use the filesystem of the internal flashl. Your program files are stored there as well. But mind the wear. Depending on your task, the NVRAM shall be the better solution.

From the pycom module documentation : "pycom.nvs_erase_all() Erase the entire NVRAM memory area." AFAIK, there is no way to see all of the contents of nvram on ESP32/Pycom boards.

@kjm I just double checked this. Beware boys & girls. pycom.wifi_on_boot(0) not only permanently disables the power up ad hoc wifi it breaks the gpy FTP server so that it won't work on any wifi network you subsequently join.

@oved-yavine you can connect by ftp using tools like filezilla for plain ftp you can use "import uos;uos.listdir()" to get a list of files there is a useful python script called upysh.py which offers a small set of shell like commands at the REPL prompt. Import it with "from upysh import *", and then you have commands like ls, cat, .. (https://github.com/micropython/micropython-lib/tree/master/upysh)

@robert-hh Whew, OK, LoPy4 on 1.19.0.b4 has 4MB flash!

Hi, I tried via ftp and it works perfectly. Regards

Hi @nicoloboatto, Indeed it is not supported currently, but it's on our list.

@seb Is it possible to use this method with encrypted flash? I mean, is application capable of writing/modifying the json file if the flash is encrypted? And if so, does these changes count for those 3 FW flashs overs USB?

@charly86 For OTA you just need appimg.bin, if the other two files are already loaded. The esptool.py command line for that would look like: esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x10000 appimg.bin

@wstallwood There is wear levelling mechanism on nvs_set, it uses the Non-volatile library from ESP-IDF: http://esp-idf.readthedocs.io/en/latest/api-reference/storage/nvs_flash.html

@dbrgn The library may also have a local cache, which would be used for reading, and could compare values against the cache before actually writing to flash. There could also be some way to write only a few bytes rather than full sectors like a filesystem would do, not sure if that's actually possible with the flash interface used.

@Colateral Before föashing your own image, you have to erase flash completely. So with the Pycom IDF, issue: make erase make flash You have to reset the device again between the two commands. I noted that already as an issue, but is is not fixed yet.

@robert-hh - Yes, thanks, I am using that on the esp8266 ( see my first code snippet df() ) and it works just fine, what I am asking is how can I get the freespace on the pycom port as statvfs() is not available ?

I was seeing this developing a BT app for no apparent reason using 1.6 Updating to 1.7.3 solved it. Haven't seen it since.