A fault phenomenon:
(1) burning USES is the SWD pin pin number 5, burning program on jlink lights flashing in red, green, MDK error (pictured),

Foot (2) reset voltage is very low, only about 0.9 V, can remove the reset foot found normal burning inside, program can run,
(3) remove the reset after foot record into the program, use jflash read the whole chip, found that the data is written to flash the,
(4) workshop mass burning, about 10% of probability
Two, I think:
To prevent abnormal, the program to add the processing of the reset to restart, I estimate is the abnormal program to reset to restart it won't cause burning in

 void HardFault_Handler (void) 
{
NVIC_SystemReset (); 
} 

Three, now worry for help how to find bugs, don't like the program can normal to run the debug it would be nice to find problems,

CodePudding user response:

Burning device power supply or circuit board power supply? Low voltage reset the feet and should write device is burnt pull low, whether to eliminate burning device failure, abnormal program can also lower reduction and feet?

CodePudding user response:

You this is an error prompt STM32 was open the write protect, brush program prerequisite clearance on STM32 may well,
I was in a mass burning tend to have offline downloader, SWD USES 4 pin can, if you are offline downloader burning, pay attention to check the burning power supply voltage is 3.3 V or 5 V,
When some Jlink write chip burn, Jlink own VDD may not power supply, there is a jump line Jlink cap, it is ok to change, also can try other power supply to the power supply, Jlink not supply power to the board (note to)

CodePudding user response:

Thank you two brother help upstairs, SWD USES 4 pin is, indeed, can the normal burning, but 90% normal way of 5 pin board can also be normal burning, I was to find the 10% burn write error problem,

CodePudding user response:

Program to run up is bad to find problems, understand the expert help myself!

CodePudding user response:

Since the program stuck up, what's that got to do and procedures, or you think NVIC_SystemReset (); There is a problem, then he take out, if only in a factory environment problems, and it is a few straightforward, personally think that is the power of the hardware interference or ESD interference,

CodePudding user response:

@ nanshan asked, single-chip computer if there is a problem will lead to this situation?

CodePudding user response:

Microcontroller is refers to the circuit board, you say this is not necessarily a circuit board, but external disturbance, personal experience, with dupont lines to connect different modules, need a total power, if you don't need a module, only the power cord, pull ground or signal lines attached to, also is easy to cause the jlink questions, and reset signal itself is more sensitive, thread derivation, it more susceptible to interference, especially line a long time,

CodePudding user response:

SCM is refers to the stm32 here said

CodePudding user response:

reference 5 floor poetryTang reply:

since the program stuck up, what's that got to do and procedures, or you think NVIC_SystemReset (); There is a problem, then he take out, if only in a factory environment problems, and it is a few straightforward, personally think that is the power of the hardware interference or ESD interference,

10% probability have the following possibilities:
1, this batch single chip itself exists some problem, before I was working as a touch screen with a similar problem, but it was the emergence of USB interface burning, there is a 9% probability of burn, the original factory analysis itself is single chip USB performance differences, in a piece of good, you can have a try, for burn-in problem in a single chip microcomputer, to rule out other problems;
2, if need to replace the microcontroller is still have some problem from your circuit board or burning device to analyze and see whether there is a capacitor or walk on the clock signal line capacitance
3, burning device, also need to analyze the probability of problems, of course, the probability and chips were relatively small