MicroPython Forum (Archive)

The only way to get rid of the memory requirements would be to completely write the neopixel driver in C with a live-calculation of the pulses as has been done in FastLED: https://github.com/FastLED/FastLED/blob/master/platforms/esp/32/clockless_rmt_esp32.h The downside to that is that you can't use...

It's for the ESP32/xtensawin, latest git version compiled on MacOS.

That's the error for a division: And that's a comparison:

Anytime I want to do a division or comparison with floats, I get an undefined symbol error by the linker. How can I include them?

See https://github.com/micropython/micropython/issues/5157.

TL;DR; Use the latest micropython version and use the RMT implementation by nevercast: https://gist.github.com/nevercast/9c485 ... 4a22062795

It won't cause problems with official uasyncio as it does not use the RTC as its timebase. But if your own code checks for a time of (say) 3.10.00 to trigger an event, you could have a problem. Say the RTC time was 3.09.55 and an update caused it to be corrected to 3.10.05 the time of 3.10.00 would...

However you do have to be careful about updating a clock which is being used to schedule events. This is because your clock no longer increments in a monotonic fashion: it can jump forwards or backwards by an arbitrary amount. Without care this can cause events to be scheduled twice or to be omitte...

In this MicroPython port you can prepare file system image and flash it to your board. Thanks! Edit: So. I ended up using my own fat image (macOS: brew install dosfstools, most likely included in most Linux distributions): $ dd if=/dev/zero of=test.img bs=1m count=2 $ mkfs.fat -S 4096 -f 1 -s 1 tes...

Hi,

is there an easy way to integrate files into the image (apart from frozen modules)? E.g. supplying my own filesystem image.


Thanks,
Carsten

I would be interested if you can give me some example application where uasyncio is better suited then threads. I guess I can only give the obvious answers. It keeps the code a little simpler, I don't have to make it thread safe, memory footprint is smaller. I have routines that control neopixel in...

Hi, so right now I cant get uasyncio working with your firmware... I'll look into it in detail when I have time, but maybe you've already come across this: >>> loop.run_forever() Traceback (most recent call last): File "<stdin>", line 1, in <module> File "uasyncio/core.py", line 138, in run_forever ...