MicroPython Forum (Archive)

in flashbdev, the flash size appears to be hard-coded to 512MB: (2048 * 1024) / 4096 = 512MB But given that devices have different size flash, can this be calculated automagically ? As the esp32 wroom and esp32-thing both 4MB of flash space, how much can I safely define ? If I correctly understand, ...

Hi Robert; I am using both ESP32-Thing and ESP-WROOM Boards. The pre-compiled binary load just fine, there's no error when loading that during boot, it is only with the firmware I compiled. I use the exact same settings for flashing the pre-compiled and my builds, it is very strange as the file size...

Have spent all of Saturday and Sunday morning and I am unable to solve this problem. on OSX, after compiling the ESP32 code, first stage is to erase the flash, second is to flash the firmware, both stages complete without errors. I have tried several different branches, and also re-cloned xtensa, es...

I am trying to create a bullet proof web server that won't just die when there is a socket error, here's the main code loop that handles the socket listen and connect: def close(self,conn): try: conn.close() except Exception as err: print('Close error:',err) while True: print('HTTP serve on IP:', wl...

You need to connect RESET PIN -> GPIO 16, otherwise it will only partially wake up (approx 6ma current) But I have discovered a problem with the Wee Mos Mini Pro, whereby the minimum supply voltage appears to be a whopping 4 volts. This is a serious limitation if you plan (as I did) to run the devic...

Fails for me on version 1.9 - 8266 ??

I am only stating the obvious here, but doesn't this break every bit of code not included in the official 1.9 release files that does any form of digital I/O ?

Maintaining 2 sets of code, one for devices already deployed (< 1.9) and another for new ones is going to be a major headache.

It is the Mini-Lite that I am referring to, that has an 8285 and a CH340G, this is the one that does a hard reset whenever you connect via serial. The Mini-Pro which I just received has an 8266 and a CP2104 and thgs device does not do a hard reset when connecting via serial and behaves same as ESP12.

I have just received and tested the Mini-Pro and it does not have this problem, so it looks like this is limited to the Mini LITE.

It may be caused by the CH340G USB > Serial device, but can't say for sure.

OK, so it seems that the watchdog is not fully implemented on the esp8266 as it is used internally. It appears that all you can do is trigger it by disabling interrupts, not sure how useful that would be. I would like to implement a watchdog in some devices, especially where they are battery powered...