Page 2 of 2
Re: question about the Deck-driver structure
Posted: Tue Dec 08, 2015 3:52 pm
by arnaud
Did you add your driver to the Makefile and did you enable it by defining DECK_FORCE as described here:
https://wiki.bitcraze.io/doc:crazyflie: ... mware:deck ?
If your driver is compiled it is going to be listed (if you add DEBUG=1 in tools/make/config.mk).
If you set DECK_FORCE you will see the initialization.
Re: question about the Deck-driver structure
Posted: Wed Dec 09, 2015 1:34 pm
by anasios
Hello arnaud! I can't see the deck-driver initialization on my console! However, i have added the DECK FORce in my makefile. You can find attached a block of my makefile :
Code: Select all
# Init
ifeq ($(F405), 1)
PROJ_OBJ = main.o platform_cf2.o
else
PROJ_OBJ = main.o
endif
# Drivers
PROJ_OBJ += led.o exti.o nvic.o
PROJ_OBJ += sensor.o
CFLAGS += -DDECK_FORCE=myIRSensors
Re: question about the Deck-driver structure
Posted: Wed Dec 09, 2015 1:39 pm
by anasios
I have also this in my makefile and i have no rule to make target deck_digital.o needed by 'cflie.elf'. Stop.
Code: Select all
# Expansion boards
PROJ_OBJ += exptest.o
PROJ_OBJ += deck_digital.o
PROJ_OBJ += deck_analog.o
PROJ_OBJ += deck.o
PROJ_OBJ += deck_info.o
PROJ_OBJ += deck_drivers.o
PROJ_OBJ += deck_core.o
PROJ_OBJ += deck_constants.o
Re: question about the Deck-driver structure
Posted: Wed Dec 09, 2015 2:41 pm
by arnaud
This is strange, it should work.
I have made a small howto on the wiki:
https://wiki.bitcraze.io/doc:crazyflie: ... deck:howto by following it you will get your code running in Crazyflie 2.0.
Re: question about the Deck-driver structure
Posted: Sat Dec 12, 2015 2:36 pm
by anasios
Hi Arnaud! thank you for your answers. In fact, I have followed your configuration as it should; However, i still can't screen my debug messages on the console and i don't know why! In other words, the driver is not configured and the code is never run!
Re: question about the Deck-driver structure
Posted: Sun Dec 13, 2015 8:11 am
by arnaud
Hi,
Are you sure you are on the master branch with the latest commit from Github? I re-run everything from a clean tree to write the documentation so from this state it should work.
/Arnaud