Bitcraze Forums

Hi everyone,

I have recently started working with crazyflie2.0. I am facing issues with the firmware upgrade.
I am working on Ubuntu 18.04, cfclient version - 2021.6, crazyflie current firmware version: 2016.11
I tried the crazyflie-ros package of Wolfgang Hönig (https://github.com/whoenig/crazyflie_ros). I am able to hover it with the command roslaunch crazyflie_demo teleop_xbox360.launch using my wireless joystick. I could see the IMU Vector in ROS Visualizer (as described in https://act.usc.edu/publications/Hoenig ... OS2017.pdf, Page 11). Also, there is no error in "Crazyflie Client"/"Console" after connection with crazyflie.

I tried both the methods for upgrading firmware
1) https://www.bitcraze.io/documentation/r ... re-upgrade
2) https://www.bitcraze.io/documentation/r ... very-mode/

While attempting the first method, when I press "connect" in "Connect Crazyflie" tab, M1 LED starts blinking RED 5 times in a second followed by a second off. On restart, the crazyflie works normal.

While attempting the second way, I am able to get to "Connected to Bootloader", but when I "Program" the new firmware(from the list), the Status remains "IDLE" and then crazyflie gets disconnected.

Please let me know if any other information is also required. Any help is appreciated.
Thanks in advance

This might be a version mismatch between cfclient and cflib. Could you try to uninstall them both and reinstall cfclient using pip3 (cfclient should bring in the right version of cflib)?

tobias wrote: ↑Wed Sep 29, 2021 9:06 am This might be a version mismatch between cfclient and cflib. Could you try to uninstall them both and reinstall cfclient using pip3 (cfclient should bring in the right version of cflib)?

Hi tobias,
Thanks for the quick reply. I would like to tell that I have installed cfclient and cflib using pip3.
The versions are listed below:
1. cfclient - 2021.6
2. cflib - 0.1.16
3. crazyflie 2.0 - 2016.11

Please let me know if any other information is also required.

This firmware definitely needs to be updated, most likely using the recovery option.

What is the state of the Crazyflie leds when you put it in bootloader mode according to the recovery instruction? Both blue LED must blink on the Crazyflie when it is in bootloader mode.

arnaud wrote: ↑Thu Sep 30, 2021 9:11 am This firmware definitely needs to be updated, most likely using the recovery option.

What is the state of the Crazyflie leds when you put it in bootloader mode according to the recovery instruction? Both blue LED must blink on the Crazyflie when it is in bootloader mode.

Hi arnaud,
First of all, sorry for the late reply.
The blue LEDs Status - M2: Blinking and - M3: ON

But when we try connect to firmware, the crazyflie will restart and M1(Red LED) starts blinking five times repeatedly after a pause.

Let me know if any other information is also required.
Thanks.

If you switch ON the Crazyflie in bootloader mode, by pressing the button until M2 blinks and then releasing it, you get in a state where M2 is blinking but M3 is fixed? If so, it likely means that your bootloader in the STM32 is not there anymore, this can happen if someone has programmed the Crazyflie over JTAG or USB.

There is some documentation on how to reflash the bootloader over US there: https://www.bitcraze.io/documentation/r ... r-recovery

Once the bootloader is flashed, both M2 and M3 LEDs should blink when the Crazyflie is in bootloader mode. For context: M2 is connected to the nRF51 radio chip that also handles the on/off button. M3 is connected and indicate the state of the STM32. So if M3 is not blinking, the STM32 is not in bootloader mode.

arnaud wrote: ↑Wed Oct 06, 2021 12:00 pm If you switch ON the Crazyflie in bootloader mode, by pressing the button until M2 blinks and then releasing it, you get in a state where M2 is blinking but M3 is fixed? If so, it likely means that your bootloader in the STM32 is not there anymore, this can happen if someone has programmed the Crazyflie over JTAG or USB.

There is some documentation on how to reflash the bootloader over US there: https://www.bitcraze.io/documentation/r ... r-recovery

Once the bootloader is flashed, both M2 and M3 LEDs should blink when the Crazyflie is in bootloader mode. For context: M2 is connected to the nRF51 radio chip that also handles the on/off button. M3 is connected and indicate the state of the STM32. So if M3 is not blinking, the STM32 is not in bootloader mode.

The solution worked! Thank you so much @arnaud.