MicroPython Forum (Archive)

One more observation on this thread. My own PyBoard is still at v1.12 on 2019-12-20. And its behavior is exactly as Peter describes. I cannot replicate the issue that OutOfTheBOTS describes. Also, I threw a scope on the servo output pin (X1 for me) and the waveform timing agrees pretty much exactly ...

as many mentioned, it is also easily possible to use thonny ide for programming which would make it a lot easier. Kevin Köck Thanks, Kevin; that is indeed my plan. Well, I have to say that building your own version of MicroPython is more challenging, but your students won't have to do that once you...

Thanks to all for the information. I think I'm starting to get a feel for the most common use models -- please correct my remaining mistakes. The sweet spot (a.k.a. plurality) of the MicroPython users seems to be hobbyists. They almost exclusively do their development on some flavor of Linux. They a...

To BricoMs: congratulations! Getting good results for a Pyboard on Windows has eluded me so far. How did you work your way through the Windows driver installs necessary for firmware updates? I've not found anything approaching up-to-date documentation for that. To ellisJr: again, congratulations! Pe...

> This is one of a small set of special cases where you need to think about object lifetimes. It is basically a concurrency issue where a background task is accessing a resource which the foreground task has allowed to go out of scope. Agreed completely. I still think that "need to think about objec...

For what it's worth, I'm having similar problems flashing new PyBoard firmware under Windows. If you ever figure out how to do it, please post your recipe. Have you had more luck with an ESP32? Maybe using a PyBoard under Windows was not the best idea.
/Joel

I've probably put 100 hours into learning/using MicroPython on a PyBoard v1.1, but am starting to question whether it's the right road to follow. Any guidance would be appreciated. My project: I teach computer engineering & biology at a university level, and am putting together an introduction-to-en...

Hi Peter, thanks -- that's good information about MicroPython using mark_and_sweep . Given that, the post probably should be retitled "Does the PyBoard DAC.write_timed() point to user memory without telling the mark-and-sweep list of top-level nodes about it?" In the end, perhaps this is somewhat mo...

Thanks, Peter, that's a good hypothesis -- but I'm not quite sure I fully believe it. Here's why. The array object (as returned by array.array()) supports a .append method(). I.e., the actual storage can be extended dynamically. Thus, it's hard to see how that storage could be allocated on the stack...

I've been playing with the DAC on my PyBoard v1.1 and running into some issues that lead me to suspect a bug. I allocate a DAC and then set up a sawtooth. First, buf = array.array ('B', range(256)). Then dac.write_timed(buf, freq, mode=pyb.DAC.CIRCULAR). A scope confirms that the DAC produces the co...