MicroPython Forum (Archive)

As you've discovered in deep sleep USB is turned off to save power. The way I deal with this on the Pyboard is, when my application starts, to detect whether USB is connected. If it is, I don't go into deep sleep. This facilitates debugging while enabling it to run normally when you start it without...

This depends on the graphics hardware. I would consider SSD1306 OLED displays which are officially supported. See the driver code . Libraries like Qt are far too large to port to microcontrollers, especially the ESP8266. There are full touch GUI solutions for the Pyboard but I don't think there are ...

Unless you have access to the MicroPython sourcecode for your platform and have the tools to rebuild and deploy it I'm afraid your options are extremely limited.

If you can successfully build and deploy the code, then I'm sure we can advise on how to include the official framebuf module.

Fair point, although a pair of resistors should be used to limit the digital signal to the 0-1V that the ADC can accept.

@Roberthh I think you may have misunderstood the original post. @digicosmos wants to re-purpose the pin as a digital output. I believe @deshipu is correct in his comment and that it's a limitation of the hardware rather than of MicroPython.

You successfully coded the first example, so I'm sure you could adapt it to do what you want. Read the x value and multiply it by a factor for the sensitivity you need. Then limit the result to constrain it to 0 <= result <= 255 and set the intensity accordingly.

A full duplex software UART is quite hard to do, especially if all the features of a hardware UART are to be emulated. Further the Pyboard has five user-accessible hardware UARTs so use-cases on that platform will be few. The main use-cases are on Espressif devices, especially the ESP8266 which has ...

The builds on the download page marked (latest) are daily builds so should work fine.

This has caused confusion before. It's not obvious how an emit=native option could possibly work without a means of specifying the target architecture/instruction set. In practice, as far as I'm aware, it doesn't work and @Roberthh's post is correct.

It looks like the developers who ported MicroPython to that platform have chosen to omit the framebuf module, perhaps to save RAM. It is available by default on the Pyboard and ESP8266.