STM32 MDK (keil5) contents mismatch error summary

Hardware 、 Software background

• ODrive Control panel ：ODRIVE V3.6-56V
  • Firmware version ：fw-v0.5.1( The updated firmware is no longer completely open source , use odriveTool When an error )
  • Equipped with dissipation resistor ：2Ω
• Encoder ：TLE5012B
• The motor ：X2212-13 （ Install the radial magnet ）
  • KV：980
  • Outer rotor
  • Number of slots ：12N14P
  • Interphase internal resistance ：92mΩ
  • No load current ：0.6A
  • Maximum continuous power ：385W
  • Maximum continuous current ：26A/30S
  • It is recommended to use current ：20~30A
• Downloader ：
  • STLink/V2
  • PWLINK2
• USB To serial port ：CH340

Problem description

test ODrive The program , The configured ODrive circuit 、 Motor parameters 、TLE5012 Magnetic encoder 、 Controller configuration 、 Trapezoidal acceleration and deceleration . Reference resources ODrive Step on the pit （ Two ）3508 Motors and TLE5012B Magnetic encoder parameter configuration 、 calibration 、 Position closed-loop mode rotation motor （TLE5012B-E1000）. When the configuration is complete , Start motor and encoder calibration , Input motor parameters after calibration ,odrivetool No response .

#  Calibrate the motor parameters （ The motor will beep after operation ~ A voice ）
odrv0.axis0.requested_state = AXIS_STATE_MOTOR_CALIBRATION

Perform the following tests ：

1. ODrive Power off and restart the circuit board ,odrivetool No response
2. sign out odrivetool,ODrive After the circuit board is powered off and restarted , Restart odrivetool： Prompt to connect the device , explain ODrive Circuit board and odrivetool No connection established , There's something wrong with the hardware
   
3. sign out odrivetool,ODrive The circuit board is powered off , Pull out USB head , Reconnect the USB,ODrive Power on the circuit board , open odrivetool. Still can't connect
4. Check device manager , Plug USB head , The device manager did not respond . It means that the hardware is not started at all USB The driver .
5. use STM32CubeProgrammer+STLink Back to the STM32F405 Burn firmware , Click burn , The software will flash back . Replace PowerWriter+PWLINK2 to STM32F405 Burn firmware , Burn successfully . Re plugging USB Head test , The device manager is still unresponsive .（ doubt MCU Something went wrong. ）
6. Use... Again PWLink2 Download program , Unable to connect to the chip
7. Write the simplest flash program , use MDK（keil5）+ STLink To test the burning program ： Report errors Contents mismatch at: 0800D03AH (Flash=FFH Required=C2H) !Verify Failed!
8. The same procedure , use MDK（keil5）+ PWLink2 Try downloading burning , Report the same mistake
   

error analysis

Contents mismatch at: 0800D03AH (Flash=FFH Required=C2H) !
Verify Failed!

This error explains STLink Download the program to STM32 In chip , When the download is complete STLink Would be right STM32 In chip Flash The content of （ Hexadecimal ） And MDK Corresponding .bin Verify the contents of the file （Verify）. Found during verification STM32 chip Flash Address 0800D03AH The content of the section is similar to .bin The documents are inconsistent ,Flash=FFH（ Empty space ,Flash After erasing it is FF）, And the correct content is Required=C2H. So there's an error . To solve this problem, I tried the following methods , It is currently invalid ：

1. stay MDK in ,Options for target–>Debug–>Settings–>
   Flash Download in , Get rid of Verify, No validation . Although it won't be wrong , But use oscilloscope to test , The program is still not running . This is obviously a cover up o(╥﹏╥)o
   

2. Reference resources use KL16 Chips appear in other people's programs BUG_ resolved Ideas provided ：

   • Reset circuit hardware error ？ When downloading and burning , Try resetting several times . No effect

   • Erase the whole Flash. The test has no effect

   • use STM32 Cube Programmer Read STM32 chip Flash Chinese content , use PowerWriter Read .bin/hex file , Compare the differences .
     

   • keil Version is too low ？ My current test is keil V5.23.0.0+STM32F4x_DFP V2.16.0;keil V5.36.0.0+STM32F4x_DFP V1.0.8, Neither version can be downloaded . Replace STM32F103 The chip can be burned normally , It shouldn't be about software 、DFP Package problem
     
     

3. Reference resources Keil : Contents missmatch at:08000E84H Verify Failed! Ideas provided ：

   • Whether the chip power supply pin is added with decoupling capacitance ？ added
   • Whether the message wave is too large , Is stable ？ Stable
   • Whether the circuit is faulty ？ Replace F103RET6, The test can be downloaded and used normally
   • The downloader cable is too long （ May cause voltage 、 Communication is unstable ）？ Lead wires should be as short as possible , Problems still exist

5. MDK in Options for target–>Target–>Memory Problems setting up the ？ The whole project uses STM32CubeMX Generated , Default settings used , Tried two IRAM Address , But the problem remains

summary

STM32 There is a problem downloading and burning , Direction of investigation ：

1. Burner problem ： Confirm the connection of the burner , Replace the burner / Connecting line
2. STM32 Chip power supply ： Test the power supply pin for power supply 、 Ripple size 、 decoupling capacitors
3. STM32 chip Flash Download setup problem ： Check Target Tab IROM、RAM Address segment , Check Debug Tab erase full chip,erase sector,programming algorithm
4. IDE Software version problem ：MDK（ Or other software ） edition 、STM32 PACK Package version
5. chip Flash damage , Replace the chip
   At present, all the problems you can think of have been tested , Only buy a new chip, replace it and try again . But the specific problem is still not found , I always think it's a hidden danger .