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
Next revision Both sides next revision
doc:crazyflie:api:firmware:deck:howto [2015-12-09 15:57]
arnaud [Enabling the driver]
doc:crazyflie:api:firmware:deck:howto [2015-12-09 15:59]
arnaud
Line 53: Line 53:
 ===== Enabling the driver ===== ===== Enabling the driver =====
  
-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. 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 68: Line 68:
  
 <code bash> <code bash>
-$ make +crazyflie-firmware$ make 
-$ make cload+crazyflie-firmware$ make cload
 </code> </code>
  
Line 75: Line 75:
  
 <code bash> <code bash>
-$ make +crazyflie-firmware$ make 
-(..)+(...)
   CC    hello.o   CC    hello.o
 (...) (...)
Line 86: Line 86:
  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.txt · Last modified: 2020-05-12 14:24 by kimberly