Bitcraze Forums

Posted: **Wed Oct 04, 2017 1:55 pm**

This is very unlikely to be related to the EEPROM. The EEPROM is only used to store configuration like the radio channel and address.

This looks like the bootloader has been erase from the STM32, most likely by someone working with a JTAG prorammer. You can build and flash the bootloader from this project: https://github.com/bitcraze/crazyflie2- ... r/Makefile. If you have a debug addapter and a jlink2 you can do "make" and "make flash" from the project folder.

Since this is not an EEPROM related issue, I suggest you make a new forum topic about flashing the bootloader.

Posted: **Thu Oct 05, 2017 10:15 am**

arnaud wrote: ↑Wed Oct 04, 2017 1:55 pm This is very unlikely to be related to the EEPROM. The EEPROM is only used to store configuration like the radio channel and address.

This looks like the bootloader has been erase from the STM32, most likely by someone working with a JTAG prorammer. You can build and flash the bootloader from this project: https://github.com/bitcraze/crazyflie2- ... r/Makefile. If you have a debug addapter and a jlink2 you can do "make" and "make flash" from the project folder.

Since this is not an EEPROM related issue, I suggest you make a new forum topic about flashing the bootloader.

Thanks for the answer. I understood now the difference.
I figured out that the problem is actually a connection problem with the zrange. Indeed i guess something is not connecting properly with it. When i detach the zrange the drone works properly, when the zrange is connected the drone "get stucked" with the 2 blue led stucked. I will open another topic about that.

Bitcraze Forums

EEPROM Reset

Re: EEPROM Reset

Re: EEPROM Reset