This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
doc:crazyflie:api:firmware:deck [2015-08-27 14:14] arnaud created |
doc:crazyflie:api:firmware:deck [2020-05-12 14:23] (current) kimberly |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <WRAP center round important 60%> | ||
+ | This page has deprecated and moved to the new documentation framework of the main Bitcraze website. Please go to [[https:// | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
====== Deck API ====== | ====== Deck API ====== | ||
Line 7: | Line 13: | ||
* Optionally provides a task to run in (arduino-like setup and loop) (//not started yet//) | * Optionally provides a task to run in (arduino-like setup and loop) (//not started yet//) | ||
+ | If you want to get started you can follow the [[doc: | ||
===== Deck drivers ===== | ===== Deck drivers ===== | ||
Line 54: | Line 61: | ||
<code make> | <code make> | ||
- | PROJ_OBJ_CF2 | + | PROJ_OBJ |
</ | </ | ||
Line 61: | Line 68: | ||
The deck driver will be initialized only if a deck is connected with the right | The deck driver will be initialized only if a deck is connected with the right | ||
OW memory content. During development it is possible to force the initialisation | OW memory content. During development it is possible to force the initialisation | ||
- | of a deck by adding a define in ```config.mk```: | + | of a deck by adding a define in ```tools/make/config.mk```: |
<code make> | <code make> |