[Resolved] Crazyflie 2.0: Big Quad deck: 'DECK_INFO: Warning! No driver found for deck.
Posted: Thu Aug 10, 2017 4:45 am
Summary:
Put config.mk file in /tools/make not ./, where the Makefile lives. This was not clear to me even after rereading the directions later, though the example config.mk file is in that directory on Github. Maybe I need to spend more time writing C code and using makefiles.
------------------------------------------------------------------------------------------------
Hi all,
I have been building a quad host for a Big Quad build. I have double checked all my wiring, ESCs appear to function properly. After making/flashing firmware to my Crazyflie, I see the following in my console: (The first entry is without BQ attached 0 deck enumerated (obviously), second is the problem, with the BQ deck attached. It seems it sees it but can't talk to it.)
SYS: Crazyflie 2.0 is up and running!
SYS: Build 5:dc3de5771fa2 (2017.06-5) CLEAN
SYS: I am 0x333136313335510731004B and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_DRIVERS: Found 10 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
ESTIMATOR: Using estimator 1
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
SYS: Free heap: 20056 bytes
SYS: ----------------------------
SYS: Crazyflie 2.0 is up and running!
SYS: Build 5:dc3de5771fa2 (2017.06-5) CLEAN
SYS: I am 0x333136313335510731004B and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_DRIVERS: Found 10 drivers
DECK_INFO: Found 1 deck memory.
DECK_INFO: Warning! No driver found for deck.
DECK_CORE: 1 deck enumerated
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
ESTIMATOR: Using estimator 1
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
SYS: Free heap: 20056 bytes
Using cfclient 2017.04, and get the same result on both Linux and Windows. The arrows on the CF and the BQ deck line up correctly. I have examined this thread, and while I have not taken voltages, the electronics seem to function normally but I can do that tomorrow.
viewtopic.php?f=6&t=2069&p=10501
When giving thrust, the crazyflie motors turn slightly, and the ESCs think they need to go into programming mode. I think some weird signal is coming out of the BQ deck as they don't do this and function normally when connected to my ESC programming card. Wish I had an oscilloscope to take a look. Also, the crazyflie appears to attempt to beep, I know the setup instructions say it should not beep or spin the rotors after this firmware mod. But it seems the BQ driver is not working properly.
Firmware appears to be functioning normally, as I can fly it just fine without the BQ deck, but maybe I can't make this assumption? Have to go to bed, to get up in a few hours, I am having way too much fun with this. You guys did an awesome job I did not truly appreciate my first few months with this platform! I appreciate any help, and will do my best to give help back.
Put config.mk file in /tools/make not ./, where the Makefile lives. This was not clear to me even after rereading the directions later, though the example config.mk file is in that directory on Github. Maybe I need to spend more time writing C code and using makefiles.
------------------------------------------------------------------------------------------------
Hi all,
I have been building a quad host for a Big Quad build. I have double checked all my wiring, ESCs appear to function properly. After making/flashing firmware to my Crazyflie, I see the following in my console: (The first entry is without BQ attached 0 deck enumerated (obviously), second is the problem, with the BQ deck attached. It seems it sees it but can't talk to it.)
SYS: Crazyflie 2.0 is up and running!
SYS: Build 5:dc3de5771fa2 (2017.06-5) CLEAN
SYS: I am 0x333136313335510731004B and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_DRIVERS: Found 10 drivers
DECK_INFO: Found 0 deck memory.
DECK_CORE: 0 deck enumerated
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
ESTIMATOR: Using estimator 1
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
SYS: Free heap: 20056 bytes
SYS: ----------------------------
SYS: Crazyflie 2.0 is up and running!
SYS: Build 5:dc3de5771fa2 (2017.06-5) CLEAN
SYS: I am 0x333136313335510731004B and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_DRIVERS: Found 10 drivers
DECK_INFO: Found 1 deck memory.
DECK_INFO: Warning! No driver found for deck.
DECK_CORE: 1 deck enumerated
MPU9250 I2C connection [OK].
AK8963 I2C connection [OK].
LPS25H I2C connection [OK].
ESTIMATOR: Using estimator 1
EEPROM: I2C connection [OK].
AK8963: Self test [OK].
SYS: Free heap: 20056 bytes
Using cfclient 2017.04, and get the same result on both Linux and Windows. The arrows on the CF and the BQ deck line up correctly. I have examined this thread, and while I have not taken voltages, the electronics seem to function normally but I can do that tomorrow.
viewtopic.php?f=6&t=2069&p=10501
When giving thrust, the crazyflie motors turn slightly, and the ESCs think they need to go into programming mode. I think some weird signal is coming out of the BQ deck as they don't do this and function normally when connected to my ESC programming card. Wish I had an oscilloscope to take a look. Also, the crazyflie appears to attempt to beep, I know the setup instructions say it should not beep or spin the rotors after this firmware mod. But it seems the BQ driver is not working properly.
Firmware appears to be functioning normally, as I can fly it just fine without the BQ deck, but maybe I can't make this assumption? Have to go to bed, to get up in a few hours, I am having way too much fun with this. You guys did an awesome job I did not truly appreciate my first few months with this platform! I appreciate any help, and will do my best to give help back.