MicroPython Forum (Archive)

I'd like to do a PR but since I already have a fork of CircuitPython I cannot create another fork of MicroPython.

Does anyone have a solution for dealing with this?
I prefer not having two github accounts or deleting the CircuitPython branch.

Thanks for the instructions! If you add the following to the Makefile (e.g. after the section ## Create binary .hex file from the .out file ### Create a .uf2 file from the .hex file uf2: $(BUILD)/$(OUTPUT_FILENAME).uf2 $(BUILD)/$(OUTPUT_FILENAME).uf2: $(BUILD)/$(OUTPUT_FILENAME).hex $(ECHO) "Create ...

Thanks for the instructions!

Warning: No memory allocation (heap) in the finaliser. I don't know the VM enough to vouch there are no other issues. MemoryError spells trouble (obviously). Although I managed to get around that problem in my application, I ran into other issues. As already pointed out by others, finalisers have ve...

Link to the code: https://github.com/iot49/micropython/blob/finaliser/extmod/modfinaliserproxy.c Usage pattern: try: from finaliser_proxy import FinaliserProxy except ImportError: # CPython compatibility class FinaliserProxy: def __init__(self, cleanup): pass class FP(FinaliserProxy): def __init__(s...

This solution presumably carries a guarantee of immediate execution No guarantees, as CPython gives no guarantee. Only IF the gc collects the object, the proxy function is called. I have an application where I "join" two Python interpreters. Objects on the server are proxies in the client. When the...

Edit: See warning below. I'm no longer sure this is useful for anything. Micropython does not call finalisers for user defined classes. Although alternatives are usually preferable, there are situations were finalisers are useful. To enable finalisers with user define classes, I created a class Fin...

I've recompiled with idf v3.3 and the error is gone. No idea why. Also, when trying to compile with idf 3 I got undefined errors. Fixed by adding a line to sdconfig.base. Not sure why I got these errors nor if this is the correct fix, but it ***works*** in my case. # v3.3-only (renamed in 4.0) CONFI...

Not a solution, but a small step towards diagnostic information: elf=$IOT49/iotpython/ports/esp32/build-GENERIC_OTA/application.elf backtrace="0x4011aa95:0x3ffe3be0 0x40082763:0x3ffe3c20 0x4008298d:0x3ffe3c70 0x4007943c:0x3ffe3c90" arm-none-eabi-addr2line -a -f -e $elf $backtrace output 0x4011aa95 s...

I have no problem with esp32-idf3-20200902-v1.13.bin (current ESP32 binary on micropython.org) but with the version compiled with IDF 4 I get the error at the end of this message. Same for binaries I compiled myself (with IDF 4). Does anyone have suggestions for analyzing the backtrace? I've tried h...