User Tools

Site Tools


doc:crazyflie:api:firmware:deck

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Last revision Both sides next revision
doc:crazyflie:api:firmware:deck [2015-08-27 14:14]
arnaud created
doc:crazyflie:api:firmware:deck [2019-09-05 15:17]
kimberly
Line 1: Line 1:
 +<WRAP center round important 60%>
 +This page is deprecated and is moved to the main Bitcraze website. Please go to:
 +
 + [[
 +https://www.bitcraze.io/docs/crazyflie-firmware/master/deck/
 +]]
 +
 +</WRAP>
 +
 +
 +
 ====== Deck API ====== ====== Deck API ======
  
Line 7: Line 18:
   * 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:crazyflie:api:firmware:deck:howto|howto]] to get your code running.
 ===== Deck drivers ===== ===== Deck drivers =====
  
Line 54: Line 66:
  
 <code make> <code make>
-PROJ_OBJ_CF2 += myled.o+PROJ_OBJ += myled.o
 </code> </code>
  
Line 61: Line 73:
 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>
doc/crazyflie/api/firmware/deck.txt · Last modified: 2020-05-12 14:23 by kimberly