Timer example not working

[Oli_]

I notice there's a new firmware build out today (29th Dec). Perhaps this might fix it?

It seems that there are no diff in the source with a previous version.

[v923z]

I notice there's a new firmware build out today (29th Dec). Perhaps this might fix it?

Where did you find the new firmware? On github, the last commit was on Nov 18th.

Cheers,
Zoltán

[pythoncoder]

Oh dear - sorry if I've caused you wasted time. I must admit my WiPy is sitting on a shelf pending firmware bugfixes.

[Oli_]

I notice there's a new firmware build out today (29th Dec). Perhaps this might fix it?

Where did you find the new firmware? On github, the last commit was on Nov 18th.

Cheers,
Zoltán

You can find the last build of the Wipy firmware as this address : http://www.micropython.org/download/
It's nearly to the bottom of the page.
The direct link for today's build : http://micropython.org/resources/firmwa ... ff2dd2.zip

[pythoncoder]

To celebrate the new year I exhumed my WiPy from its sarcophagus and downloaded the latest (2016) firmware. I really don't enjoy being critical but alas even the first timer example fails:

Code: Select all

>>> from machine import Timer
>>> tim = Timer(4)
>>> tim.init(mode=Timer.PERIODIC)
>>> tim_ch = tim.channel(Timer.A, freq=2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: invalid argument(s) value

So I guess my WiPy will be interred for a few more months in the hope of firmware which can at least run the demos. Or is it the documentation which is wrong?

@Danicampora The docs are confusing in that http://micropython.org/resources/docs/e ... neral.html directs users to https://github.com/wipy/wipy/releases for firmware rather than http://micropython.org/download/. The github site does seem long out of date.

[Roberthh]

For low frequencies/long periods, you have to use tim.channel(Timer.A | Time.B, freq=2). And yes, the documentation is somewhat concise, not telling when to use which. The example in the doc about registering a callback handler is also wrong. That's what misled me first. And I'm not sure whether the time module works well. But until now I had no real need to determine.
But besides this: Happy New Year.

[v923z]

You can find the last build of the Wipy firmware as this address : http://www.micropython.org/download/
It's nearly to the bottom of the page.
The direct link for today's build : http://micropython.org/resources/firmwa ... ff2dd2.zip

Thanks, Oli! However, this raises another issue: if there is binary firmware that is newer than the latest commit on github, then github is obviously not the main platform for code development. I think this is really confusing, and hinders collaborative work. E.g., if I were to fix the timer code, I have no idea where I should get the source from.

I ordered the micropython board when it was announced on kickstart two years ago. In about a week, Damien released his source code, and made the work on the code extremely transparent, and exactly this is what makes the micropython project so lively. Based on this experience, I expected a similar attitude from the creators of wipy, especially, that wipy was staff picked on kickstart. I was obviously wrong.

Zoltán

[v923z]

Oh dear - sorry if I've caused you wasted time. I must admit my WiPy is sitting on a shelf pending firmware bugfixes.

Don't worry, no harm was done.

Zoltán

[Roberthh]

Besides the micropython.org download site for binaries, the whole source code including the versions for WiPy can be found here: https://github.com/micropython/micropython. The WiPy version is the one in folder cc3200.

[pythoncoder]

@Roberthh

the documentation is somewhat concise

That's a very diplomatic way to express it I can handle "concise" but demos which don't actually work and links to outdated source code are profoundly offputting.

Thanks for the pointers. I'll try once again to make sense of the WiPy and its timers. Happy new year, everyone