MicroPython Forum (Archive)

At least it is smaller

Have you got plans to fill the 2x 1,5 mm gap? Or is the part too small to fit into the mounting frame?

The was a change regarding the used FAT library and filesystem mount points. The maintainers should be aware of this but you can also file an issue on github.

To think that kind of security is easily implemented in an open source and hacker friendly environment is a false conclusion. It might be possible, but not well supported, because it is not designed into this platforms as it is on those Roberthh did outline. To be constructive... The intent you fors...

The ESP8266 boots up with 26 MHz oscillator and then has a 74880 for the initial boot messages (maybe internal osci?). Then after switching to 40 MHz this becomes the better supported 115200 baud.

So i'd guess that there is this 2880 multiplier, which might help!?

torwag wrote:connection data is stored in permanent flash memory. A reboot or power cycle will not help.
To proof kfrickes thesis, rename the AP ssid to something new and definitively unknown before and try again.

Of course this is the better way!

I am just trying to lead to some details which might help us to identify resolve this issue... I presume this cache is in memory? I get the same results when attempting to connect after a reset or a power cycle No, the cache is in flash memory of your ESP board/module. I'd suggest you try to manuall...

The ESP vendor API caches the SSID and password up to 5 different WiFi connections without further notice. It seems to do this in the way that when connecting with no (or an empty) password it simply (and quietly) looks up the last credential from the mentioned cache. Maybe you have the SSID in this...

I did have a look at the sources (esp8266/modnetwork.c) and do not see any possible reason for that behavior. In both cases an empty string is passed to the underlying SDK method (wifi_station_set_config). A quick online search did yield some issues with the ESP SDK toolchain wich has had such issue...

What does I2C.scan() show?