User Tools

Site Tools


doc:crazyflie:api:firmware:deck:howto

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doc:crazyflie:api:firmware:deck:howto [2015-12-09 15:49]
arnaud [Making your first Deck driver]
doc:crazyflie:api:firmware:deck:howto [2020-05-12 14:24] (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://www.bitcraze.io/documentation/system/]]
 +</WRAP>
 +
 +
 +
 ====== Making your first Deck driver ====== ====== Making your first Deck driver ======
  
 This howto is going to describe step-by-step how to make and flash your first This howto is going to describe step-by-step how to make and flash your first
-Crazyflie 2.deck driver. See the deck [[doc:crazyflie:api:firmware:deck|api documentation page]] for more information about the code.+Crazyflie 2.deck driver. See the deck [[doc:crazyflie:api:firmware:deck|api documentation page]] for more information about the code.
  
 ===== Development environment ===== ===== Development environment =====
Line 48: Line 54:
  
 <code make> <code make>
-PROJ_OBJ_CF2 += hello.o+PROJ_OBJ += hello.o
 </code> </code>
  
 ===== Enabling the driver ===== ===== Enabling the driver =====
  
-Decks can contain a memory that contains its name. In our case the hello driver would be initialised only when a deck identified as "myHello" is installed on the Crazyflie. For development purpose it is possible to force enabling a deck driver. To do so create the file tools/make/config.mk with the content:+Decks can have a memory that contains its name. In our case the hello driver would be initialised only when a deck identified as "myHello" is installed on the Crazyflie. For development purpose it is possible to force enabling a deck driver with a compile flag. To do so create the file tools/make/config.mk with the content:
  
 <code make config.mk> <code make config.mk>
Line 62: Line 68:
  
 DEBUG=1 allows to get more information from the Crazyflie console when it starts. Debug should not be enabled if you intend to fly the Crazyflie out of the lab (it disables the watchdog). DEBUG=1 allows to get more information from the Crazyflie console when it starts. Debug should not be enabled if you intend to fly the Crazyflie out of the lab (it disables the watchdog).
 +
 +<WRAP center round info>
 +//**Note**// Each time you modify config.mk you should recompile the full firmware by cleaning up the build folder with 'make clean'
 +</WRAP>
 +
  
 ===== Compile, flash and run! ===== ===== Compile, flash and run! =====
Line 68: Line 79:
  
 <code bash> <code bash>
-$ make +crazyflie-firmware$ make 
-$ make cload+crazyflie-firmware$ make cload
 </code> </code>
  
Line 75: Line 86:
  
 <code bash> <code bash>
-$ make +crazyflie-firmware$ make 
-(..)+(...)
   CC    hello.o   CC    hello.o
 (...) (...)
Line 86: Line 97:
  130660    1636   29828 162124   2794c cf2.elf  130660    1636   29828 162124   2794c cf2.elf
 rm version.c rm version.c
-$ make cload+crazyflie-firmware$ make cload
 ../crazyflie-clients-python/bin/cfloader flash cf2.bin stm32-fw ../crazyflie-clients-python/bin/cfloader flash cf2.bin stm32-fw
 Restart the Crazyflie you want to bootload in the next Restart the Crazyflie you want to bootload in the next
doc/crazyflie/api/firmware/deck/howto.1449672584.txt.gz · Last modified: 2015-12-09 15:49 by arnaud