A chip needs programs to function, miniaturizing all components into one or more integrated circuits; an integrated circuit can accept coded instructions at one or more of its terminals, execute these instructions and output signals describing its state. The process of storing programs into the chip is called chip programming. Chip programming sometimes presents a strange phenomenon: for example, the programmer shows PASS throughout, but after the chip is mounted on the board, the product cannot function properly. Naturally, one would first suspect equipment problems. Next, let us learn about the related content together with the editors of Chuangxin Testing.

To make the test stricter and reproduce the problem, we learned about the chips and files the customer programmed and conducted tests. Through testing, we found the programming file was unusual: the chip programming file needed to be converted into two files, but during use it was not correctly transferred to these two files. Under guidance, the customer completed the test with no abnormal feedback.



The common approach is certainly to check:

Whether the batch chips themselves have a defect rate;

Whether the programming equipment and testing are normal.

If no problem is found in these two points, novice engineers may be a bit troubled. Why is my chip normal, and the mass production equipment is also the equipment used for R&D testing? Why is this happening?

This is because several implicit issues are often overlooked:

Although the mass production programming equipment is consistent with the equipment used in the R&D testing stage, do they all use original emulators? Or other dedicated programming equipment not suitable for mass production?

It should be noted that for chip programming, dedicated mass production programmers can achieve one-key operation, suitable for batch production by factory personnel with weaker foundations, ensuring batch output. Original emulators are R&D-oriented and their operation cannot be this simple. They may require operating the host computer software buttons each time, and may require connecting and then programming, introducing the possibility of human operational errors.

Furthermore, the feedback of emulator programming results is not obvious; it may be printed strings, or buzzer and light signals. For actual factory production personnel with weak professional knowledge, errors may occur because they do not understand the principles. Finally, emulators are not mass production equipment and cannot guarantee output.

2. If the selected programmer is for mass production, is it in-circuit programming or socket programming? If a programmer adapter/chip fixture is needed, are there maintenance issues with the fixture? What is the current fixture lifespan?

This point is often overlooked. If the equipment is already a mass production programmer and previous programming was normal, then look at your programming fixture, that is, the so-called programming socket, or how long the programmer adapter has been used. Programming fixtures have a number of uses, that is, the so-called service life. However, most domestic manufacturers currently do not provide customers with professional programming socket/fixture operation manuals or maintenance documents, and it is difficult to download the corresponding ones online. Many minor faults such as poor contact come from the programming socket.

If the number of programming operations approaches the service life of the programming socket, it depends on whether the contact between the socket fixture and the chip pins has been damaged by frequent chip insertion/removal collisions or uneven pressing force. Most minor problems come from here. The simplest test method is to replace with another socket for comparative testing, which can quickly locate the problem.

Other possible programming failures also include incompatibility between the programmer host software and the chip, requiring firmware package updates, etc. These will be discussed later. Finally, we remind all engineers that programming sockets require maintenance. You can refer to the standard programmer adapter maintenance manuals of reputable companies, and use auxiliary pressing equipment such as press levers when necessary, to maximize the service life of the programming socket.

So how to simply determine the cause of this phenomenon? Careful engineers have summarized some field experience, which is very practical.

1. Conduct small-batch verification before mass production, and only proceed with mass production after verification passes, avoiding large losses;

2. Ask the corresponding software engineer for accurate guidance and detailed explanation of configuration parameters to ensure programming accuracy;

3. Restrict operations available during production and assign permissions to necessary personnel to avoid misoperation.

The above is the related content of "Analysis of Causes of Abnormal Chip Programming". Through this article, we hope it can be helpful to everyone.