Bitcraze Forums

Hi there,
I flashed my crazyflie to update the firmware to its 2019.01 version( https://github.com/bitcraze/crazyflie-release/releases) using VM. After that crazyflie_client cannot detect the drone anymore. How should I modify the firmware now? (I also tried eclipse, but I guess the USB radio dongle just does not recognize it, ) I don't have the debugger cable. Is there any other way to modify the firmware.
I tested it on Ubuntu machine and it worked fine. I guess the issue is the USB drives of my mac. I'm running Os Mojave version 10.14.2. Has anyone else encountered such a problem?

Thanks

2019.01 has a bug that affects radio communication if more than one deck is installed. Maybe you are hitting this bug. It could also be that the flashing operation failed, does your Crazyflie starts correctly?

Anyway, it is always possible to flash again: the bootloader cannot erase itself so you can always recover your Crazyflie.

If the Crazyflie is still working, press the button until the blue LED blinks to enter bootloader mode and flash the version 2019.02.1 which does not have the radio bug.

If the crazyflie does not start you can disconect the battery, press the button, connect the battery while the button is pressed and release the button when the blue LED blinks. This way you can enter the bootloader again and flash version 2019.02.1.

Thanks, Arnaud! I was able to flash it using a Windows machine. Mainly I wanted to modify the firmware and activate the Kalman filter Estimator. It is working fine now. That being said, do you still recommend changing the firmware to 2019.02.1? (Here's a demo how my crazyflie hovers currently.) Let me know if I have to flash it again.

https://youtu.be/reBzRPjIRBA


Thanks

I would recommend updating to 2019.02.1 because of the kind of severe bug in 2019.01.

Thanks for your rapid reply. I did update the firmware to 2019.02.1 and I'm running a launch file that gives off some log readings however I still don't receive anything and most cases it gives the low link quality warning. Is there still something with my firmware version or shall I fix sth else?

Thanks

2019.02.1 has no other known bugs, so the version should be alright. What channel/bitrate are you running at? For best result you should use the 2M bitrate and you can try changing the channel to avoid interference with local wifi and other transmitters in the 2.4Ghz region.

Also a follow up question, you are flashing the .zip file and not only the .bin?

Hi Tobias!
Sorry, it took me a while to get back, I got busy with sth else. Yea I did flash the zip file as far as I remember, but then I modified the firmware to activate the KALMAN_FILTER. I'm still not able to print logs using crazyflie_demo launch files of whoeing's repository.

For your question, after I flashed it for the first time, it gave me an error in eclipse regarding 'tools/make/config.mk', it can't determine URI to config.mk even though it's still there, so I have been flashing the firmware in terminal following the command sequence 'make clean', 'make', 'make cload' since then.

Figured it out!! you may close this forum. There was an issue with my ROS implementation, the firmware seems good.

Thanks