The blueNRG-1 chip will burn out automatically when running the program (solved)

千本樱大白

The blueNRG-1 chip will burn out automatically when running the program (solved) [Copy link]

 

 

邀请：@littleshrimp   参与回复

Phenomenon: After welding, the chip can be connected normally without a program at first. It is also normal without a system reset after burning the program. However, once the system is reset, the entire chip is broken and can no longer be connected.

This phenomenon is similar to the phenomenon I have when I take someone else's normal board and remove the capacitors of VDD1V2. Last time I asked the administrator, he has redone the pins and line widths to make them closer and wider, which is equivalent to copying someone else's board, but this phenomenon still occurs.

千本樱大白

This phenomenon occurs because the crystal oscillator uses an active crystal oscillator.

chunyang

If there is no wrong soldering, the chip should not be damaged. If the circuit, PCB design or decoupling is poor, it may work abnormally, but I have never seen a chip burn.

littleshrimp

If it is convenient, you can send me a broken board and a board that has been soldered but not programmed, and I will help you test it.

freebsder

A system reset shouldn't damage the chip. Magic.

千本樱大白

chunyang posted on 2020-11-9 19:46 If there is no wrong soldering, the chip should not be damaged. If the circuit, PCB design or decoupling is poor, it may work abnormally, and I have never seen a chip burn.

The most amazing thing is that if there is no program for the first time, you can use STlink to connect, but when you start running the program, the chip will be broken.

千本樱大白

littleshrimp posted on 2020-11-9 19:51 If it is convenient, you can send me a broken board and a board that has been soldered but not programmed, and I will help you test it.

I'll send you the extra ones if you have any. PM me the address?

千本樱大白

freebsder posted on 2020-11-9 22:27 System reset should not damage the chip. It's amazing.

It seems that it started running after the system restart because there is a program. It is normal when there is no program.

dcexpert

It is probably not a chip problem, but a program problem. Check the configuration and initialization codes more.

chunyang

Senbenzakura Dabai posted on 2020-11-9 22:53 The most amazing thing is that if there is no program for the first time, you can use STlink to connect, but when the program starts running, the chip is broken

The question is: How do you tell if the chip is burned?

千本樱大白

dcexpert posted on 2020-11-9 23:01 It should not be the chip that is broken, but a program problem. Check the configuration and initialization code more.

The program is from the official example, how could it be wrong? And it is normal to burn it on someone else's development board.

千本樱大白

chunyang posted on 2020-11-10 00:03 The question is: how do you determine whether the chip is burned?

Because I soldered the chip to a normal board, it also doesn't work, VDD and SMPS don't work, both are 0V

chunyang

Senbenzakura Dabai posted on 2020-11-10 01:36 Because I soldered the chip on a normal board, it didn't work either, VDD and SMPS didn't work, both were 0V

There are many reasons why it does not work. Check the local oscillator and program. The chip will burn only if there is a serious error in your circuit, causing some external short circuits such as IO or PA. If the circuit is correct, even if your PCB design is unreasonable, resetting the system will burn the chip, which can only mean that there are serious problems with the chip design. How can the manufacturer, as an international leading manufacturer, put such an obvious chip design error into production and sales? ! So many top engineers from various countries, but no one has discovered it for so long? ! It is impossible! The problem can only be that your judgment is wrong, and there is no such thing as burning the chip. If it really burns, it is either because there is a serious error in the circuit, or there is a serious problem with the power supply or peripheral devices you use, or it is caused by some of your operations, which has nothing to do with the chip. There is nothing else.

千本樱大白

chunyang posted on 2020-11-10 11:45 There are many reasons why it does not work. Check the local oscillator and the program. As for burning the chip, unless there is a serious error in your circuit, causing some external short circuits such as IO or PA...

Because this chip is all official modules, I have searched tb and other things and have not developed anything myself. This chip is also not used by many people. As for the selection of peripheral components, schematics, and PCB design, they are all 1:1 according to the official ones, otherwise there would be no program that can connect to it. What confuses me most is that if there is a problem with the design, I should not be able to connect to it the first time.

chunyang

Senbenzakura Dabai posted on 2020-11-10 12:14 Because this chip is all using official modules, tb and the like have been searched and there is not much secondary development by myself. This chip is also used by few people...

You have to pay attention to the difference in the operating environment between the first run and after reset. I guess the problem lies here. The system initialization operation must be correct, complete and suitable for your system. The program you found may not be suitable, at least not complete, and it is just a coincidence that it can run for the first time. In other words, the chip you thought was "burned" did not happen at all, and it is impossible to happen. It is completely a program problem, but you misunderstood it.

chunyang

Please note that when burning the program, the internal burning code will perform certain operations on the chip, and the impact of these operations will not be removed after the burning is completed. These "impacts" do not exist after reset, so the operating environment is different, the code does not match, and it seems that it cannot work.

chunyang

There is also a special case where your system is not reset correctly due to inappropriate component parameters, which can also cause problems. Inappropriate decoupling capacitors can prevent the chip from operating normally under the power supply you are using, which is also a problem to pay attention to.

千本樱大白

I will write down the comparisons I have made. I call the boards bought from others that can be repeatedly burned and programmed as G (good) boards, and the boards made by myself with problems as B (bad) boards.
1. The same program and the same new chip, first soldered on the G board, can be burned and programmed repeatedly, removed and soldered on the B board, STlink cannot be connected, prompt "Connection to device is lost: check power supply and debug connection. If the target is in low power mode, please enable "Debug in Low Power mode" option from Target->settings menu." (If you erase the program first, the B board can be connected, but it will become the second case.)
2. The same program and the same new chip, first soldered on the B board, STlink can be connected repeatedly without a program, and after the burning program is automatically reset, STlink automatically disconnects and can no longer be connected. The prompt is the same as above. Remove it and solder it on the G board, and STlink cannot be connected. The prompt is the same as above.
3. When the B board is not programmed, VBAT1,2,3=3.3V; VDD1V2=1.2 V; SMPSFILT1 is a 1.4 V periodic waveform like a peak; SMPSFILT2 is 1.4 V.
After programming, VBAT1,2,3=3.3V; VDD1V2=0.45 V; SMPSFILT1 graph is rather strange, and it looks different at different oscilloscope gears. The following figure shows that it should fluctuate at 0.4V; SMPSFILT2 is 0.4 V.
4. Tried to solder only the above-mentioned pin capacitors and inductors, as well as the resistor and inductor of the reset pin, and the TEST pin biased to ground on the B board, without soldering the crystal oscillator and antenna parts, but the phenomenon remained the same (it can be connected without the program, but it cannot be connected with the program, and the chip does not run)
5. Tried to remove the above-mentioned pin capacitors and inductors from the G board, and solder the resistor and inductor of the reset pin on the B board, without soldering the crystal oscillator and antenna parts, and the phenomenon was the same as above.
6. I changed the program to be burned. I tried GPIO_IOToggle.hex and BLE_Chat_Server.hex respectively. The same phenomenon occurred.
7. When burning the program with STlink, I removed the automatic reset after burning. I did not reset the system. The B board can be erased and the program can be repeatedly connected.
8. The schematic diagram and PCB were drawn according to the official PDF.

9. The B board can be connected without a program, but cannot be connected with a program. The chip also does not run. This phenomenon also occurs when the large capacitor of VDD1V2 is removed from the G board and the program is reset.

Use the 1V position of the oscilloscope to see the waveform of the SMPSFILT1 chip on the B board that has been programmed.

Use the 500mv position of the oscilloscope to see the waveform of the SMPSFILT1 chip on the B board that has been programmed.

千本樱大白

chunyang posted on 2020-11-10 12:39 You have to pay attention to the difference in the operating environment between the first run and after the reset. I guess the problem lies here. The system initialization operation must be correct, complete and suitable for your system...

I wrote more details on the second floor. In fact, it didn't run successfully once. I can connect repeatedly without the program. I can't connect with the program.

yibin_cai

Thousand Sakura Dabai posted on 2020-11-10 16:16 I wrote more details on the second floor. In fact, it didn't run successfully once. Only when there is no program can it be connected repeatedly. If there is a program, it can't be connected

Don't jump to the conclusion that the chip is damaged.

Assuming your problem is "the chip cannot connect to st-link"

For this problem, you can try the following:

1. For the official development board, STEVAL-IDB011B1, press and hold the PUSH1 button, then press the RESET button to see if you can connect to the ST-link

2. For third-party boards, the operation method is similar to that of the development board. You can give PA10 IO a high level, then trigger a reset, and then release PA10 IO to see if the ST-link connection can be restored.

千本樱大白

yibin_cai posted on 2020-11-10 17:47 Don't jump to the conclusion that "the chip is damaged". Suppose your problem is that "the chip cannot connect to st-link&rdq ...

My chip is blueNRG-132, which does not have the PA10 pin.