How to switch cf2.0 to cf2.1

[CasperLiZ]

I made a large-size 8520 hollow cup aircraft according to the CF2.1 schematic, but the solid information was displayed as CF2.0, which caused the IMU initialization to fail.

Thanks

[krichardsson]

Hi,
there is something called the "device type", this is an identifier that is written to the hardware in production and is used when the system is booting to figure out how to configure it. If no device type identifier is found, the system will use Crazyflie 2.0 ("CF20") as a default, I assume this is what is happening in your case.

The device type is read in platform.c.

There are two options for you

1. Write the correct device identifier to the hardware. I don't remember how to do this though, @tobbeanton can you help with this? Also, be a bit careful, I think this is memory that can only be written one time and never erased.
2. Compile the firmware with DEVICE_TYPE_STRING_FORCE defined as "CF21" to override the default behavior. This is obviously easier and safer than 1.

[CasperLiZ]

Using OTP is obviously very dangerous, because the number of times the STM32 OTP can be modified is limited. You can refer to
How to write STM32F4 OTP Area

[justinleeyang]

if we compile the firmware with 2.1, and download , It is OK, but when cf-client-python OTA the HW, the firmware still be 2.0, how to slove the issue?

[CasperLiZ]

You can see this instruction in the src/platform/src/platform_stm32f4.c file. You only need to change the corresponding hardware version to achieve it. When using cf-client-python OTA, the firmware is still "DEFAULT_PLATFORM_STRING "0;CF20""

[justinleeyang]

I have tested ok use "0;CF21", but if cf-client-python OTA, still "DEFAULT_PLATFORM_STRING "0;CF20", crazyflie2.1 report MPU9250 error, no use BMI088, it is fail, how to sloved the issue ? only a method, OTP wirte ？

[justinleeyang]

I haved write OTP value as follow, but restart stm32f405 don't start up, why ?