Search found 642 matches

by Damien
Thu Apr 29, 2021 7:12 am
Forum: Newsletter archive
Topic: MicroPython Newsletter Issue 11
Replies: 2
Views: 2769

MicroPython Newsletter Issue 11

Dear community, Today is MicroPython's 8th Birthday! The 29th of April marks the date on which the first line of code was written, which is now 8 years ago! It has also been exactly a year since the last newsletter... so here is an update on the main things that have happened since then. In the past...
by Damien
Thu Apr 22, 2021 12:00 am
Forum: General Discussion and Questions
Topic: Build firmware v1.14 with IDF 4.2 problems
Replies: 2
Views: 898

Re: Build firmware v1.14 with IDF 4.2 problems

I think you need to install cmake version 3.12 or greater. Which version of cmake do you currently have?
by Damien
Tue Feb 09, 2021 7:45 am
Forum: General Discussion and Questions
Topic: Asyncio in uPython 1.14 has not "run"???
Replies: 18
Views: 1506

Re: Asyncio in uPython 1.14 has not "run"???

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...
by Damien
Tue Feb 09, 2021 1:02 am
Forum: General Discussion and Questions
Topic: Asyncio in uPython 1.14 has not "run"???
Replies: 18
Views: 1506

Re: Asyncio in uPython 1.14 has not "run"???

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 ...
by Damien
Sat Feb 06, 2021 1:31 am
Forum: General Discussion and Questions
Topic: MicroPython security process?
Replies: 2
Views: 461

Re: MicroPython security process?

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...
by Damien
Tue Feb 02, 2021 8:58 pm
Forum: Other Boards
Topic: MicroPython kills ST-LINK on STM32-H743ZI2?
Replies: 3
Views: 716

Re: MicroPython kills ST-LINK on STM32-H743ZI2?

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...
by Damien
Tue Feb 02, 2021 11:25 am
Forum: Other Boards
Topic: MicroPython kills ST-LINK on STM32-H743ZI2?
Replies: 3
Views: 716

Re: MicroPython kills ST-LINK on STM32-H743ZI2?

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 ...
by Damien
Wed Sep 02, 2020 6:10 am
Forum: Announcements and News
Topic: MicroPython version 1.13 released
Replies: 3
Views: 5473

MicroPython version 1.13 released

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...
by Damien
Wed Apr 29, 2020 4:22 am
Forum: Newsletter archive
Topic: MicroPython Newsletter Issue 10
Replies: 2
Views: 7231

MicroPython Newsletter Issue 10

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...