This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I'm having a problem with XT2 (8 MHz) starting on one PCB but it works fine on another PCB (same PCB, same firmware). The symptoms are that XT2OUT goes high and XT2IN stays low. I have tried a different crystal and different capacitors, but this didn't help. Swapping out the chip is a PIA.
I'm using the MSP430F552x_UCS_08.c code for starting the oscillator. If I heat the MSP430, the chip starts oscillating. After about an hour, it stops oscillating. I have Vcore set to 1 before starting the oscillator. Any ideas short of replacing the chip?
Regards,
Scott
Looks liek you're not the only one with this kind of problems.
There have been more than a couple of other threads with similar symptoms.
We too have lots of devices (about 10% of our production) which won't start their crystals. This is so for about two years now. We didn't change the layout but older batches didn't have this problem (<<1% failure rate).
We suspected the crystals (which we solder together with all the other through-hole parts), despite the fact that out distributor lists them as same type as before. We suspected the capacitors (which are machine-soldered together with all other SMDs by the PCB manufacturer), the firmware (which hasn't changed in this section, but since old parts don't fail with the newest firmware, this is not the reason) and the quality of our own soldering work.
But until recently we didn't suspect the MSPs, as it happens for MSP430F1232 and MSP430F1611 as well. And both didn't undergo a silicon revision when the problem appeared first.
Now it looks like the MSPs of newer production seem to have changed somehow and without having officially changed at all.
It is really disturbing.
Your test with heating the chip was an interesting idea. We will repeat this test as soon as we build the next batch and have some test devices. (usually, changing the crystal and/or the capacitors made the failing devices work, so we don't have one at hand right now).
If we can confirm the same with our devices, this will harden the suspicion of the MSPs being the problem.
I hope we'll get a solution soon (or at least a workign workaround). If not, it can well be that out next generation of metering devices is based on a different processor series. (Which would effectively remove me from this forum. Hint, hint!)
Please keep us informed if you get more insights on this topic.
**Attention** This is a public forum