MicroPython Forum (Archive)

Depends. How are your modules communicating with each other? Are you using some kind of synchronization object, or just passing around Python objects? In general, most Python modules haven't been vetted for thread safety, so running in this kind of multi-threaded environment is a bit hazardous. The ...

I've got enough different STM32 tools installed I forget which is which, but you don't need a toolchain to use the stlink. That's just what I do. On Windows, I believe you can use the STM stlink tool to flash the firmware image. You may want to get that to update the firmware on the stlink in any ca...

Which port are you connecting to? The mini USB port is connected to the stlink built into the board, and it will never show up as a dfu port for the STM32F4. It might show up as an stm32flash port if you put the STM32F4 in bootloader mode. The micro USB port is connected to the STM32F4 USB system, a...

RM0090, 18.3.6. They actually get both the width and period using the same technic with a second channel on the timer. Using the capture register in an IRQ that runs on both edges is essentially the same method as most people user on old 8-bit ATMEGAs, made more accurate by using the capture registe...

I saw that. From what I can tell, it's not using the reference manual recipe, which uses the timer hardware to calculate the pulse width. Is there a reason not to follow the recipe in the reference manual?

The STM32F4 timers are a lot more capable than the typical ATMEGA timers, so I was sort of surprised when all the examples I could find of doing PWM input or input capture - either in MicroPython or Arduino - fell back on the typical ATMEGA thing of taking interrupts on value change, and then figuri...

But how many users will bother looking at someone else's profile - on either forum? Personally, my experience is that Google finds answers on SO no more often than it does on any other non-dedicated forum. On the other hand, my questions on an SO board are much less likely to get an answer than thos...

Is https://github.com/dhylands/upy-example ... te_code.py what you want?

FreeBSD and Linux treat bogus tty ioctl values differently. Linux explicitly mask them off, so if you pass a value to the wrong ioctl, all that happens is your setting doesn't happen. FreeBSD doesn't do that, which can cause some really strange behavior. stm32flash had such a bug in it until last ye...

I've done quite a bit of protocol design work, and there are some techniques that can help with things. For instance, you can design the protocol so that it includes acks in the data packets. Having options to indicate "all packets to X received OK" as well as "nothing to ack at this time" can be us...