MicroPython Forum

In the forum we often refer to using uasyncio for programming, I think it is a core module that should be available everywhere. Even more than modules like btree, who are (as far as I can tell) are not widely used. Yep, I agree. Might be a good idea to revisit the esp8266 1M board definition to see...

esp8266 builds for 1M modules do not have uasyncio included in them (maybe we can add it to them, not sure if there's enough space left on the 1M builds). The reason you can import uasyncio on your board is because it's been installed via upip and resides in the filesystem. I've now updated upip so ...

Hi! The general answer to your questions is that, if you develop an IoT device and security is important to the application, then you should have your own procedures in place to make sure your device and all the code meets the security requirements (or otherwise) of the application. For example, Mic...

AKAIK there are a lot of users who have been and are using MicroPython on a NUCLEO_H743ZI board, without any issue. MicroPython doesn't do anything funny that would break ST-LINK. You can try and getting the board into ST bootloader mode and see if that helps. Use BOOT0 or execute machine.bootloader...

It shouldn't really be possible to kill ST-LINK like that, but I have seen ST-LINK run into issues quite often. I'd suggest simply power cycling everything, even your PC. Also, the H7 MCU can be a bit of a beast to tame. If you have access to a more "friendly" MCU, like an F7 or F4 then I'd suggest ...

After a long delay and a crazy year, the team is happy to announce the next release of MicroPython, v1.13! Source code and firmware can be downloaded from https://micropython.org/download/ The full change log can be found at https://micropython.org/resources/micropython-ChangeLog.txt A summary of th...

This issue should be fixed by https://github.com/micropython/micropyt ... 3daccfc7d5

Dear community, It's been a while since the last newsletter and, although we are in unprecedented times, MicroPython continues to move forward, albeit a bit more slowly. Today is MicroPython's 7th Birthday: the 29th of April marks the date on which the first line of code was written, and it's now be...

why does pinging make this go away? Maybe because with wifi power saving now enabled (which is perhaps why it wasn't seen before), when the power saving feature runs it runs in a certain location in flash which aliases to the same cache location that pin_intr_handler was in, and evicts the pin_intr...

The fact that it crashes with an IllegalInstructionCause right at pin_intr_handler is very good evidence that the crash is because pin_intr_handler is in flash and it cannot read flash because the hard GPIO IRQ has interrupted an ongoing flash operation. Note that pin_intr_handler is called by pin_i...