MicroPython Forum

I had the same error when I tried to flash a esp-07 which had 1Mbyte flash while I expected that is was a 4Mbyte device like most esp12-F's.

This is the Micropython forum. Your code is C.

But your problem is that you should use the GPIOxx names as pin and not the physical pins of the board.

For android there is an apk to use WebRepl

https://microcontrollerelectronics.com/ ... n-android/

I tried it and it works.

jimmo wrote: ↑

Thu Oct 03, 2019 12:51 pm

Unfortunately this is an ESP32-only feature and not currently documented. https://github.com/micropython/micropyt ... rtc.c#L128

That is not true. It is implemented (and undocumented) for esp8266 too.

So you should prevent this by cutting off the pins that connect to tx/rx, fill your device (especially also the flash memory) with epoxy etc. What exactly do you mean with "epoxy" etc. ? I never heard about this term in this kind of area. I mean like 2 component epoxide glue. I have to say! This is...

I'm mainly using ESP-8266/32 boards. Now to access the network with the device you have to put the clear WIFI credentials into your scripts For esp32 that is true for esp8266 there is no need to store credentials in your script. But as you said, if you have access to the device you can read out all...

My mistake was a typo in my post. I meant ticks_ms, not ticks_us. I've correct the post. Thanks. But even then then you can not have a mismatch of 10 seconds in 10 minutes because ticks_ms uses ticks_us. And yes, if you keep track of the overflows you can use that as your time. I have made a digita...

and time.ticks_us() is only slightly better (fell 10 seconds behind in a 10 minute test). Then you made a mistake or your device is broken. time.ticks_us() is very accurate. (about 2 seconds per 24 hours or less). Are you aware that ticks_us() uses a 30-bits counter that overflows after about 17 mi...

I had that error too (error on client side) when I was trying to develop an Android App (based on html, js and css that worked on my laptop and Google Chrome browser). I finally found out that it was caused by using the emulator of Android Studio. As soon as I used my "real" telephone as test device...

uwebsocket should work. Can you try another client? For example on this site: https://www.websocket.org/echo.html look at "Creating your own test" I used this to do a simular project as you and that worked (websocket on esp8266). The advantage is that if you use "index.html, js , css" in a folder on...