MicroPython Forum

This is in support of PR6007 . I experienced problems with Kingston SD cards where the SPI bus is shared with other peripherals. The fault is fixed by a simple change to sdcard.py. The question is whether I have some specially dodgy SD cards or whether others are affected. In my testing Sandisk card...

HermannSW wrote: ↑

Thu Apr 22, 2021 7:15 am

...
The point is to give Pico MicroPython networking, so that any usocket code will work on it as is.
...
When I will have usocket running with lwIP over USB, I will revisit the connected ESP01 and get hopefully "real" Wifi networking for the Pico.

Light dawns

Yes. In general microcontrollers boot up with pins floating: any other option would be potentially unsafe to connected peripherals. If you want a pin to start at a defined level, an external resistor is the solution.

I may be wrong but my understanding of this project is that the Pico/ESP8266-01 combination hosts an HTTPS website on one core while running arbitrary Python code on the other. The Python side supports a REPL over UART for debugging. This could have plenty of applications. As you say, I imagine you ...

The rgb() function you copied converts 24-bit rgb color values to an 8-bit result, for use with a bytearray buffer. This is a RAM saving device: I use GS8 mode for the underlying framebuf, with values being expanded to 12-bit at runtime. I'm surprised the result looks remotely correct! Given that yo...

... Is that -3155673600 indicative of the problem? Actually after trying this a few more times it seems if I don't wait more than one (?) second between tries then I get the error... If you look at ntptime.py you'll find this line . A return value of -3155673600 means that the time() function has f...

No. FreeRTOS runs on one core and MicroPython on the other. MicroPython supports pre-emptive multitasking via _thread and cooperative multitasking via uasyncio, but in both cases (on ESP32) execution is on a single core.

Try this format string

Interesting link. It's noteworthy that your two addresses both fall in the 74.125.0.0/16 range reported in September 2017. The article talks of the address ranges changing with time - it doesn't mention whether individual addresses within a range might become unavailable. A possible approach to mini...

... That didn't take long ... took about 10 minutes for it to change from ('74.125.200.108', 465) to ('74.125.68.109', 465)... That's interesting. I wonder if the old address still worked? I'm no expert on this stuff but it's possible that Google maintain a pool of IP addresses and DNS servers serv...