Hello.
I made a patch to add Arduino style tone() and notone() functions for MapleIDE 0.0.9.
Now the Maple can BEEP using hardware PWM.
patch:
http://ideone.com/45dy7
demo:
http://youtu.be/MjRLknXoCDc
Since tone(pin, frequency, duration) looks pretty complex to implement, it is not supported yet.
mbolivar
LeafLabs
Hi Fadis,
Thanks for the patch! Unfortunately, it won't apply to the current development libmaple development code (which is the "refactor" github branch). Much has changed in libmaple since the last release, and the low-level timer API you are using no longer exists.
For now, preliminary information on how libmaple is being restructured is available here:
http://static.leaflabs.com/mbolivar/libmaple_design/index.html
The old file timers.h became the new timer.h; the new version has been made public, and is available here:
https://github.com/leaflabs/libmaple/blob/refactor/libmaple/timer.h
I am trying to finish the work going on in the refactor branch by the end of the week; we are doing it in order to provide you and the growing number of other community contributors with a stable API to work against. The new libmaple interfaces are not expected to change for the foreseeable future.
We would love to see this patch redone in terms of the new timer API. Thanks again!
gbulmer
Moderator
mbolivar - presumably the processor frequency is factored out to a 'well known' constant label so that code can use a libmaple exported value rather than wiring in 72000000L?
(It would be preferable for the value to be a visible value, rather than simply a global name, so that things like (float)MAPLE_FREQUENCY get done at compile time)
> https://github.com/leaflabs/libmaple/blob/refactor/libmaple/timer.h
The new libmaple looks interesting!
I'm busy these 2 days, but I'll try to write a patch for the development code after that.
mbolivar
LeafLabs
gbulmer,
mbolivar - presumably the processor frequency is factored out to a 'well known' constant label so that code can use a libmaple exported value rather than wiring in 72000000L?
Yes, the constant CYCLES_PER_MICROSECOND can be used for this purpose; see e.g.
https://github.com/leaflabs/libmaple/blob/refactor/wirish/boards/maple.h#L38
Edit: These sorts of values are documented under the "board-specific values" page, which will be included with the regular HTML docs under leaflabs.com/docs. Here is that page as it stands in the current refactor tree:
https://github.com/leaflabs/libmaple/blob/refactor/docs/source/lang/api/board-values.rst
gbulmer
Moderator
mbolivar - that is a very helpful page, thanks.
I have a small concern about the space consumed by the supporting tables.
Should I assume it is very cheap, or I don't "pay" (in space) if I don't use them?
Do they live in Flash if I do use them?
(full disclosure: I am not a member of the LeafLabs staff)
mbolivar
LeafLabs
gbulmer,
They live in Flash when they are used. We call GCC with -fdata-sections -ffunction-sections, and call the linker with --gc-sections, so unless those arrays are used (directly or indirectly) by functions you call, the linker should be able to optimize them out.
You must log in to post.
