f288d1e4a7
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> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _microbit_display: BBC micro:bit display ##################### Overview ******** A simple example that demonstrates how to use the 5x5 LED matrix display on the BBC micro:bit board. Building ******** This project outputs various things on the BBC micro:bit display. It can be built as follows: .. zephyr-app-commands:: :zephyr-app: samples/boards/microbit/display :board: bbc_microbit :goals: build :compact: Sample Output ============= The sample app displays a countdown of the characters 9-0, iterates through all pixels one-by-one, displays a smiley face, some animations, and finally the text "Hello Zephyr!" by scrolling.