COCOFLY Tutorial - Crazy Shell Drone Series Quick Start [5] Remote Controller Firmware Burning

小壳壳

COCOFLY Tutorial - Crazy Shell Drone Series Quick Start [5] Remote Controller Firmware Burning [Copy link]

Remote control firmware burning

Remote control firmware burning

The firmware here refers to the Hex or Bin file compiled from the source code , where Hex is a hexadecimal file and Bin is a binary file. The following figure shows the Hex file compiled from the remote control code .

As long as this firmware is burned into the Flash of the remote control's main core STM32F103C8T6 , the remote control code can run. The compiled firmware has been placed in the "【5 】 Remote Control Firmware Burning" folder, as shown in the following figure.

The specific burning steps are as follows:

( 1 ) Connect the matching downloader to the download port of the remote control, and connect the other end to the computer via a data cable. The port location is shown in the figure below.

( 2 ) OpenJ-Flash ARM, click "Start J-Flash", then a box will pop up for selecting the correspondingJ-flashfile, find the model "STM32F103CB.jflash", and click to open it. As shown in the figure below.

( 3 ) The model of the main chip of the remote control is clearly " STM32F103C8T6 ", so why is " STM32F103CB.jflash " selected ? This is because the overall code size of the remote control has exceeded the 64kB size of " STM32F103C8T6 ". According to the official solution provided by STM32 , the model selected in MDK is changed to " STM32F103CBT6 ". After compilation, the firmware can also be downloaded to the " STM32F103C8T6 " chip, as shown in the figure below.

This is possible because the STM32F103C8T6 and STM32F103CBT6 are manufactured on the same wafer, but when ST officially tests, it only tests the contents included in the parameter range provided in the manual, which means that the STM32F103C8T6 also has 128kB Flash , but only the first 64kB is tested , and then the STM32F103C8T6 mark is added. Therefore, the problem of excess code capacity can be solved in this way. After a lot of tests, the remote control code runs normally.

( 4 ) Then drag the corresponding firmware ( Hex file) to the J-Flash ARM software to open it. Press F7 or click " Auto " under " Target " to complete the firmware download.

Unplug the downloader and restart the remote controller. All functions of the remote controller will run normally.