MicroPython Forum

2. What could be the possible cause of the RuntimeError: maximum recursion depth exceeded? The stack size of the thread was too little? That is indeed a possibility. This error is thrown when the stack overflows, and that usually happens when there is a runaway recursion. According to the current s...

As far as I can say this function is not documented. However, looking in the source code one can see that currently the esp32 port of the esp module deals with the log level by declaring The function esp.osdebug which can have one or two arguments. With one argument, only the value None is recognize...

I use the same combination. However the latest (3.2.x) version of Thonny includes a remote file explorer if the device supports it. One can edit and run files on the device. I just tested with my M5Stack (running an old lobo firmware).

One thing about the DTH series is their low sample rate (around 1Hz). It is very possible you overwhelm the sensor by requesting values too frequently. Another thing would be to encapsulate the measures within a try: except: block and manage the errors...

I think the problem is in the to_bytes() method because if I remove it the error is not showing but the program is not functional. Any ideas on this ? You are missing the parameter specifying endianness. One should write: a=12345 print(a.to_bytes(2,'big')) print(a.to_bytes(2,'little')) and that eve...

Just to be sure: have you tried running your M5Stack using a USB charger instead of your computer? Apart from resetting the WDT, is there something else hapening in your code? The reset could very well be caused by a brown-out due to excessive current consumption. I had that on an ESP8266 connected ...

That's the weird bit: normally the bno's address should be 0x28 or 0x29, depending on the state of its COM3 pin. If you are using the adafruit package, this pin is accessed through the ADR pin and defaults to COM3 low and 0x28 as the I2C address. So first things first: check if your bno is properly ...

Weird. The scan should consistently show 40 (or 41) not a mix of 40, 41 and none of the others.

What addresses do you see? The bno055 chip should answer 0x28 or 0x29, and the SSD1306 0x3c or 0x3d

Excluding the UNIX port, I am not quite sure that one can get such a figure. In many cases micropython is running on bare metal without any os, so the "load" would be 100%...