Hi, I have a Crazyflie 1.0 I built it and tested the functions, then I compiled and updated the firmware on the copter. After starting (beeping, turning the propellers) the copter, it blinks red four times, I wanted to debug and noticed that the method watchdogNormalStartTest is called from system.c and it retruns false.
I also noticed that the 20ms stablilizer isn't added and started when I oppened the Log Blocks Debugging Tab in the Crazyfie Client software.
I also deployed the same firmware to the DOF10 model I have and this works fine. Do I have to compile the firware differently for DOF 6 and DOF10? Or what could be the issue here?
Here the debug output after connecting:
SYS: Crazyflie 1.0 is up and running!
SYS: Build 21:db840bd81948 (2015.08.1-21) CLEAN
SYS: I am 0x872252374855725066CFF51 and I have 128KB of flash!
CFGBLK: Verification [FAIL]
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883L I2C connection [FAIL].
IMU: MS5611 I2C connection [FAIL].
MPU6050: Self test [OK].
SYS: The system resumed after watchdog timeout [WARNING]
SYS: No assert information found
Thanks for your help in advance.
watchdogNormalStartTest retruns false
Re: watchdogNormalStartTest retruns false
Did you compile an test the very latest version from Git?
You can try to compile in debug mode (make DEBUG=1 or add DEBUG=1 in config.mk), then the watchdog will be disabled.
You can try to compile in debug mode (make DEBUG=1 or add DEBUG=1 in config.mk), then the watchdog will be disabled.
Re: watchdogNormalStartTest retruns false
Hallo,
first of all, thanks a lot! The CF1.0s are flying again. That is really cool.
Anyway, I think a discussion with the developers would be useful. As far as I understand the error message indicate, that something with storing the configuration is going wrong. The log entry is generated during start-up calling configblockInit
There are two different files (see Makefile)
with the same function. One is using the flash the other is using the eeprom for storing the information. I will try to understand the code a little bit deeper. But one short question... What's the logical connection between the configuration and the watchdog?????
One problem is still open, I can not configure the CF1.0, but this an other problem. I will first search the forum.....
Again, Thanks a lot!
Karsten
PS:
first of all, thanks a lot! The CF1.0s are flying again. That is really cool.
Anyway, I think a discussion with the developers would be useful. As far as I understand the error message indicate, that something with storing the configuration is going wrong. The
Code: Select all
CFGBLK: Verification [FAIL]
There are two different files (see Makefile)
Code: Select all
PROJ_OBJ_CF1 += configblockflash.o
PROJ_OBJ_CF2 += configblockeeprom.o
One problem is still open, I can not configure the CF1.0, but this an other problem. I will first search the forum.....
Again, Thanks a lot!
Karsten
PS:
Both are 10-DOF CF1.0.Are the Crazyflie's you're using 6-DOF or 10-DOF?