Crazyflie not turning on

[cflie2]

Hi arnaud,

The one crazyflie which can be enter DFU mode is working with official firmware by following your instruction.

After running the following command, I did not know that it can be get bootloader mode by pressing the button for 3 sec.

Code: Select all

sudo dfu-util -d 0483:df11 -a 0 -s 0x08000000 -D cf2loader-1.0.bin

Anyhow, I got bootloader mode, and then I flashed .zip file for the latest firmware. (I used cfclient & usb port)
I really appreciate it.

However, what can I do for the other crazyflie...?
This one seems not to be able to get into DFU mode..
$ lsusb did not show any DFU mode device..
Furthermore, bootloader mode did not work.
The led pattern is like
https://youtu.be/2gjfFRy3uzc
after that, yellow led flash at 1Hz.

Do you have any idea for this?

Thank you so much.

[arnaud]

Great for the first one!

For the second one, the M2 LED pattern looks good, can you enter the mode where the 2 LED blinks fast?

[cflie2]

Yes, I can make the LED blink very fast (about 1Hz) like a DFU mode by pressing the button for 5 sec.

However, $ lsusb did not show any DFU mode device as I said in the previous post.
The output is shown in the following.

Code: Select all

ubuntu:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Furthermore, cfclient did not detect anything at all.
Bootloader in cfclient did not work at all neither.

[tobias]

It is sometimes tricky to get the DFU bootloader running (some timing issue we are not fully aware of)). Did you disconnect the battery and held down the button while inserting the cable as described in this wiki page?

[arnaud]

So, just to confirm, exactly the same procedure as what you used on the first Crazyflie (ie. Disconnecting the battery and connecting the USB port while pressing the button) does not work for the second Crazyflie?

Do you know how PX4 was installed in these Crazyflies, was a SWD debugger used to program them?

[cflie2]

Hi arnaud,
sorry for my tardy reply.

The link you gave me does not work.
As I already mentioned, there is no dfu mode devide detected when I run "lsusb"

When I flashed PX4, I followed the link; https://docs.px4.io/en/flight_controlle ... flie2.html
I used the usb cable and dfu mode, not SWD debugger.
(Recently, I bought it. So please let me know if I can do something with SWD debugger)

P.S. QGroundControl does not detect any cf2 neither.

[arnaud]

Yes if you have an stlink and the debug adapter you can flash the bootloader this way.

To do so, clone the crazyflie2-stm-bootloader project and run in a console:

Code: Select all

make
make flash

If the stlink is connected to the debug addapter which is connected to the Crazyflie debug connector, the bootloader will be flashed.

Looking at the doc you followed, it means that the DFU mode has worked before on this Crazyflie, strange that it does not work anymore.

For QGroundControl, I have recently tried PX4 and I did not manage to connect to it either. Though I have never used PX4 so I am pretty sure I was doing something wrong.

[cflie2]

Thank you for your reply.

I need to buy stlink.......
Do you think the following is okay?
https://www.amazon.com/DAOKI-ST-Link-Pr ... =stlink+v2
Thank you.

[arnaud]

I have only been using the white slightly larger version. I have seen this one popped-up lately but we have not had the chance to test it.

In theory, yes, it should work fine since it is advertised as an st-link V2 programmer.

[cflie2]

Hi, arnaud

recently I receive stlink, and try flash stm-stm-bootloader..
The result, however, is shown in the following..

Code: Select all

~/crazyflie2-stm-bootloader$ lsusb
Bus 002 Device 021: ID 0483:3748 STMicroelectronics ST-LINK/V2
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
~/crazyflie2-stm-bootloader$ make flash
openocd -d2 -f interface/stlink-v2.cfg  -f target/stm32f4x_stlink.cfg -c init -c targets -c "reset halt" \
                 -c "flash write_image erase cf2loader.elf" -c "verify_image cf2loader.elf" -c "reset run" -c shutdown
/bin/sh: 1: openocd: not found
Makefile:170: recipe for target 'flash' failed
make: *** (flash) Error 127

Do you have any idea?

P.S. I connected all stm pin on debug board to stlink usb device.
Also, I connected cf2 to debug board. Then, cf2 powered on as like when I plug a battery in, (showed the same pattern of LED)