Analysis of the reasons why Lingdong MM32 cannot be burned

火辣西米秀

Analysis of the reasons why Lingdong MM32 cannot be burned [Copy link]

 

There are many reasons why Lingdong MM32 cannot be burned. We analyze it from two aspects: hardware and software:

Hardware reasons:

1. The debugger used does not support debugging and downloading of MM32 MCU. The emulator selection/configuration on IAR/KEIL is incorrect. MM32 MCU has been officially certified by Segger. On the Segger official website, J-Link driver version 6.40 and above supports the MM32 MCU series. MM32 MCU supports MM32-Link, U-link, J-Link, DAP-Link, etc. to access the kernel, peripherals, and FLASH using SWD/JTAG (M3).
2. The minimum system of MM32 MCU is incomplete, and the reset circuit design is wrong, the MCU power supply is abnormal, etc., which will also cause the device to be unable to be recognized. MM32 MCU supports a wide voltage of 2.0-5.5v power supply. When users design the product PCB themselves, it is recommended that users reserve VCC, SWDIO, SWCLK, GND, and NRST five-wire download port mode. Please refer to the demo board for design when designing the circuit.
3. The two pins PA13 and PA14 of SWD are poorly soldered, the external hardware is pulled up or down, the connection with the debugger is incorrect or not connected, etc.

Software reasons:

1. Program download error. MM32 MCU has five series: F, L, SPIN, W, and P. We have different libraries, startup files, and routines for different MCUs. Before downloading the program, please check whether your MCU version model corresponds to the program to be downloaded. For example, MM32F031C6T6 is divided into version q and version n. The two models have different clock domain configurations, so the program cannot be directly shared.

2. The MCU is in read/write protection state. When the MCU is in read protection state, the FLASH space is in write protection state. At this time, the SWD protocol cannot be used to access the core, peripherals, and FLASH, and download and debugging cannot be performed.

3. The MCU is in a low-power state. When the MCU is in a low-power state in different modes, the peripheral area of the MCU will be in a power-off state. The debugger recognizes that the MCU is in a power-off state and cannot be downloaded and debugged.

4. The two pins PA13 and PA14 of SWD are multiplexed as other functions or general IO, and PA13 and PA14 are configured as other working modes. At this time, PA13 and PA14 cannot work normally in SWD mode, and the debugger cannot download and debug through the SWD protocol.

5. An error occurred during program download. Due to reasons such as download speed and debugger version characteristics, an error occurred during the download process, causing the MCU to enter the HardFault state (program runaway), and download debugging is not possible at this time.