MicroPython Forum (Archive)

It took some time to become familiar with mpremote, but I managed to transfer some scripts to my Teensy40. Since I have now a working Micropython on the Teensy I was curious about its performance compared to what I experienced with Circuitpython (see my entry of 21 April 2020 in this Forum). So I re...

Thanks Robert! I'll see if I can get things working despite the (hopefully temporary) limitations...
Success with the developments.
Rob.

I just discovered the existence of Teensy40 and Teensy41 boards in the Micropython repository. A make of the firmware for my Teensy40 succeeded and after I loaded the resulting firmware.hex file with the Teensy loader a virtual serial port appeared (ttyACM0). From a serial terminal program I see the...

Solved issue #7296.

Cannot find recent 'daily firmware builds' for the ESP32s anymore.
Would be nice to get 'm back, can anyone take care?
Rob.

OK! I removed esp-idf, re-installed it and now the make runs without errors and apparently produces a working firmware.bin!
Maybe I have a different IDF version now than before which might be the reason for the link-problem.
Thanks for your prompt help!

Thank you for the explanation of 'commit'! Following your suggestion I removed the build-GENERIC directory (the only one in micropython/ports/esp32 with leading 'build'), but still the same error. Then I had a closer look at the console log and noticed the following: Git submodule components/bt/cont...

No, I didn't make clean. But even after that I got the same error message.
I'm not sure what you mean by 'which commit'! I just did a git pull which reports 'already up to date'.
And makes for PyBoard 1.1 and Blackpill run flawlessly: "v1.14-152-g6f06dcaee"

When I run make (for the generic esp32) with the current sources I get the following message: /home/rob/micropython/extmod/modbtree.c:37:10: fatal error: db.h: No such file or directory #include <db.h> ^~~~~~ compilation terminated. I didn't see that before. Could it be related to the btree module (...

Hi Steve,
Your choice of address may be the cause of your problem.
In I2C standards 0x00 - 0x07 and 0x78 - 0x7F are reserved I2C addresses.
Rob.