Crazyflie 1.0 and firmware > 2015.1

Post here to get support
Post Reply
Hovy
Beginner
Posts: 5
Joined: Tue Apr 05, 2016 9:39 pm

Crazyflie 1.0 and firmware > 2015.1

Post by Hovy » Tue Apr 05, 2016 9:56 pm

Hello all,

I can not use on my Crazyflie 1.0 a firmware higher than 2015.1!
After flashing a higher version the LED's are on, but he does not respond to inputs.
I use the client version "Cfclient 2015.08", the last installer version.

The logfile after flashing "crazyflie1-2015.1.bin", everything works fine:
-->
SYS: Crazyflie is up and running!
SYS: Build 0:02dd0d49962c (2015.1) CLEAN
SYS: I am 0x8712173654568549670FF50 and I have 128KB of flash!
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
<--

The logfile after flashing "crazyflie1-2015.08.1.bin", no response to inputs:
-->
SYS: Crazyflie 1.0 is up and running!
SYS: Build 0:61e23e51d7d3 (2015.08.1) CLEAN
SYS: I am 0x8712173654568549670FF50 and I have 128KB of flash!
CFGBLK: v0, verification [OK]
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
SYS: The system resumed after watchdog timeout [WARNING]
<--

The logfile after flashing "cf1-2016.02.bin", no response to inputs:
-->
SYS: Crazyflie 1.0 is up and running!
SYS: Build NA:NA (2016.02) CLEAN
SYS: I am 0x8712173654568549670FF50 and I have 128KB of flash!
CFGBLK: v0, verification [OK]
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
SYS: The system resumed after watchdog timeout [WARNING]
SYS: No assert information found
<--

Please help me, what can I do?


Regards
Georg



chad
Expert
Posts: 555
Joined: Sun Sep 28, 2014 12:54 am
Location: New York, USA
Contact:

Re: Crazyflie 1.0 and firmware > 2015.1

Post by chad » Wed Apr 06, 2016 6:46 pm

Hi Georg,

This is quite possibly a problem with older client and newer firmware. I will try on my CF1 when I have a chance but have you tried using the latest client with the newest firmware?
Crazyflier - my CF journal...
4x Crazyflie Nano (1.0) 10-DOF + NeoPixel Ring mod.
3x Crazyflie 2.0 + Qi Charger and LED Decks.
Raspberry Pi Ground Control.
Mac OS X Dev Environment.
Walkera Devo7e, ESky ET6I, PS3 and iOS Controllers.

Hovy
Beginner
Posts: 5
Joined: Tue Apr 05, 2016 9:39 pm

Re: Crazyflie 1.0 and firmware > 2015.1

Post by Hovy » Thu Apr 07, 2016 8:47 pm

Hi Chad,

thanks for your help, I will test it on the weekend.

How do I install the update?
Unzip and copy over the old files?


Thanks
Georg

Hovy
Beginner
Posts: 5
Joined: Tue Apr 05, 2016 9:39 pm

Re: Crazyflie 1.0 and firmware > 2015.1

Post by Hovy » Mon Apr 11, 2016 10:57 am

Hello all,

I have now testet with the Client version "Cfclient 2016.02" under Windows 10.

And it does not run! :?

What I noticed is, the battery state will not be indicated.

Here the output in the log file:

crazyflie1-2015.08.1.bin
-->
IMU: MPU6050 I2C connection [OIMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
SYS: The system resumed after watchdog timeout [WARNING]
<--

cf1-2016.02.bin
-->
IMU: MPU6050 I2C connection [OK].
IMU: HMC5883 I2C connection [OK].
IMU: MS5611 I2C connection [OK].
MPU6050: Self test [OK].
HMC5883L: Self test [OK].
MS5611: Self test [OK].
SYS: The system resumed after watchdog timeout [WARNING]
nd
<--


With version "crazyflie1-2015.1.bin" everything runs without problems!

What can I do?


Regards
Georg

otto
Beginner
Posts: 19
Joined: Sat Dec 28, 2013 5:03 pm

Re: Crazyflie 1.0 and firmware > 2015.1

Post by otto » Mon Jun 13, 2016 2:24 am

I am experiencing the same issue

chad
Expert
Posts: 555
Joined: Sun Sep 28, 2014 12:54 am
Location: New York, USA
Contact:

Re: Crazyflie 1.0 and firmware > 2015.1

Post by chad » Mon Jun 13, 2016 3:47 am

Hi @otto,

What client and firmware versions do you have? I have confirmed that:

client: 2016.4
and
firmware: 2016.02
work fine together without this issue...
Crazyflier - my CF journal...
4x Crazyflie Nano (1.0) 10-DOF + NeoPixel Ring mod.
3x Crazyflie 2.0 + Qi Charger and LED Decks.
Raspberry Pi Ground Control.
Mac OS X Dev Environment.
Walkera Devo7e, ESky ET6I, PS3 and iOS Controllers.

Post Reply