zephyr

History

Andy Ross f288d1e4a7 tests: samples: Apps shouldn't set tick rate Tick rate is becoming a platform tunable in the tickless world. Some apps were setting it due to requirements of drivers or subsystems (or sometimes for reasons that don't make much sense), but the dependency goes the other way around now: board/soc/arch level code is responsible for setting tick rates that work with their devices. A few tests still use hard-configured tick rates, as they have baked-in assumptions (like e.g. "a tick will be longer than a millisecond") that need to be addressed first. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>		2019-07-02 22:52:29 -04:00
..
src	dts: Rename SW._GPIO_* -> DT_ALIAS_SW._GPIOS_*	2019-07-01 07:14:36 -05:00
CMakeLists.txt	…
README.rst	…
prj.conf	tests: samples: Apps shouldn't set tick rate	2019-07-02 22:52:29 -04:00
sample.yaml	…

README.rst

.. _microbit_sound:

BBC micro:bit sound
###################

Overview
********

This is simple example demonstrating how to use a piezo buzzer connected
to port P0 on the edge connector of the BBC micro:bit board. Note that
the buzzer is not part of the main micro:bit board, rather it it needs
to be separately acquired and connected. A well working example is the
MI:Power board that has a piezo buzzer in addition to a coin-cell
battery. Resellers of this board can be fairly easily found using online
search.

Building
********

The sample can be built as follows:

.. zephyr-app-commands::
   :zephyr-app: samples/boards/microbit/sound
   :board: bbc_microbit
   :goals: build
   :compact:

Sample Output
=============

This sample outputs sounds through a connected piezo buzzer based on
button presses of the two main buttons. For each press the current
output frequency will be printed on the 5x5 LED display.