zephyr/samples/boards/bbc_microbit/pong
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 license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
prj.conf tests: samples: Apps shouldn't set tick rate 2019-07-02 22:52:29 -04:00
README.rst
sample.yaml samples: add test identifier 2019-03-29 17:44:11 -04:00

.. _microbit_pong:

BBC micro:bit pong game
#######################

Overview
********

Play pong over as single player or Bluetooth between two micro:bit
devices.

The game works by controlling a paddle with the two buttons of the
micro:bit (labeled A and B). Initially the playing mode is selected: use
button A to toggle between single- and multi-player, and press button B
to select the current choice. To start the game, the player with the
ball launches the ball by pressing both buttons.

When multi-player mode has been selected the game will try to look for
and connect to a second micro:bit which has also been set into multi-
player mode.

If the board has a piezo buzzer connected to pin 0, this will be used to
generate beeps whenever the ball hits a wall or the paddle.

Building
********

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