MicroPython Forum (Archive)

Thanks, I agree this could do with a better explanation -- sent https://github.com/micropython/micropython/pull/5421

MicroPython only runs main.py at startup.

When you click the run button in uPyCraft, it runs blink.py for you, but on startup you have to tell it.

The easiest thing to do is add "import blink" to the top of main.py.

I highly recommend your third option -- write out your config as Python (using `repr` helps here) and load it directly by importing.

So where did the 150us come from? Could it be that Damien made a mistake and nobody thought to question it or double check it? OK, so the web site is wrong. Perhaps someone should update it. I suspect that the quote on the website is measuring MicroPython itself. i.e. the time taken from when the f...

I think v1 support is there mostly for people who wanted to migrate existing / devices that were using v1 for whatever purpose or had some specific reason for using it. But that's why support for it isn't compiled in by default.

I went looking through my notes from a summer school I used to teach at -- https://github.com/jimmo/ncss-embedded/blob/master/chapters/7-bitbot-neopixels.md This is specifically about using the bit:bot with the micro:bit and MicroPython. There's a code snippet at the end: from microbit import * impo...

MicroPython doesn't currently support the "signed" parameter to from_bytes. In the code for from_bytes it says: // TODO: Support signed param (assumes signed=False at the moment) (void)n_args; So it matches the CPython behavior if you set signed=False (which probably isn't what you want). However, t...

Worth mentioning though -- to answer your specific question, yes the ESP32 can do this right now if you write C code against the IDF using Bluedroid. So given that all you want to do is pretend to be a non-functional HFP profile device, it might be quite straightforward to adapt one of the IDF examp...

I'm fairly sure this requires Bluetooth Classic, not BLE. That UUID is the Hands Free Profile (which is part of BT Classic). Not to be confused with a BLE Service UUID. It would be great to support BT Classic on ESP32 and STM32 -- I replied to a query about this on GitHub recently https://github.com...

This is really cool - excited to see hardware APIs getting the asyncio treatment. Thanks!

Don't have a DHT22 but I might have a DHT11 somewhere to test with.