MicroPython Forum (Archive)

then just stays off. I think the problem is that the main loop is constantly checking the "motion" flag, but if the flag is set then it re-sets "motion_start" to the current time. So once motion is set to True in the interrupt, then it will never "time out" because "motion_start" is always being up...

Problem solved, but I am frustrated that this can even be an issue. Using D1 mini pro, the problematic class was inside a folder, if it makes a difference. I created an account on the forum just to up your issue that still exists. Thanks for reporting. I'd really like to get to the bottom of this i...

The only thing I've seen that's close is Bleak -- https://github.com/hbldh/bleak

duckt14 wrote: ↑

Wed Jul 21, 2021 10:03 pm

I'm using UART but I'm not having success in that.

How is the UART connected to your PC? Do you have a separate UART-USB adaptor (e.g. FTDI) also wired up?

I think I figured it out (as test example) Yep, that looks good. How to terminate "run_forever()"? The simple answer is that "you don't"... i.e. the only reason to terminate run_forever is when your program is stopped (i.e. by you hitting Ctrl-C or resetting the board). Your entire program should r...

njepsen wrote: ↑

Wed Jul 21, 2021 10:28 pm

Thanks for your reply Mike.

FYI Mike's PR was merged and the I2S functionality is now available in the nightly builds (and will be in 1.17)

1) Cannot it be that the Scheduled period is simply too much? (I read that in Firmware 1.16 - there is a limitation to the number of timers = 4 (0 - 3)). (I can send the code - but it is too long ) Possibly, I would need to check. But in general the timers make more sense when you need low-latency ...

The board I'm using is the Adafruit Feather RP2040, and because it has the wrong flash size definition, I had to change the mpconfigboard.h, changing MICROPY_HW_FLASH_STORAGE_BYTES and redefining PICO_FLASH_SIZE_BYTES. However, I can't find where the PICO_FLASH_SIZE_BYTES is normally defined. Ahh I...

ExDes wrote: ↑

Tue Jul 20, 2021 12:49 am

Is this a likely source of the problem?

6.3 was first released in December 2016... I would definitely want to rule that out before trying anything else.

In case I follow this, how do I make sure to put my memory block aside and make sure the filesystem is not expecting to use it? The way the filesystem works is: - In ports/rp2/boards/PICO/mpconfigboard.h we define MICROPY_HW_FLASH_STORAGE_BYTES which is how many bytes of flash to reserve for the "u...