Hi, I've written a (HTTP 1.0) web server which will have various features, for the esp8266 running in Micropython (1.8.4 actually the latest built) This is all running perfectly most of the time, but there is a case where it isn't. If a web browser opens two sockets at once, perhaps a second one bef...
200ms sounds like quite a long time to write a small file, I think it should be doable. Robustness is a bigger problem. Writing a file to the (DOS) filesystem needs at least to update the directory entry, the fat and the file itself. This is three writes which might not all succeed if the power fail...
Hi, I'm wondering if it's possible to workaround the small amount of RAM, by loading, then unloading several modules at runtime. Then I can write more code than can fit in memory. For example, if I have some pseudo-code which uses import sys # .... exec('import modtest', {} ) # Instead of globals, u...
Thanks a lot, I'll try it at home. Is your miniservet able to handle POST and GET vars? Unpacking form-encoded data is a problem, because there is very little ram and form posts can get big. That's why I don't use multipart/form-data POSTs, and just use PUT instead (client-side JS deals with it). I...
I have written a web server for the ESP8266 which allows upload / download files, serves images, css and Javascript code, it's still in development, but code is here: https://github.com/MarkR42/esp-webui Memory limitations are the real problem, but I can stream upload / download files as big as you ...
If you have 512k flash, then there won't be enough room for a filesystem, so I suppose, we should build a version of Micropython for the ESP8266 without the filesystem and that may save enough space to fit in 512k? Of course you then need to store your app in the scripts/ directory to be built with ...
Ideally we would be able to redirect the repl to /dev/null, and still connect over webrepl (if enabled), but then use rx/tx for something else. I don't think we can prevent the firmware and bootloader spitting out rubbish at 75k baud at boot-time, but that only affects tx (and some rubbish comes out...
Usually what I do is check the reset code, and try to start up more quickly if it was a crash, but put a delay for normal reset or power on, to give the user time to press ctrl-C