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.

MSP430F5438: system halted when power on

Part Number: MSP430F5438

Hi all

In the use of MSP430F5438 design system,It is an abnormal phenomenon that system halted when power on。

The 5 products  have been  such abnormal phenomena in the production of 3500 products.

I want to know What may be the cause?

  • Hi Ming,

    This could be due to core voltage failure but it is hard to discern with such little information. Please provide schematics, code initialization, and oscilloscope screenshots of VCC, RST, XT1/2, and COREV pins for more assistance with the issue. Note that the MSP430F5438 is NRND and that the pin-compatible MSP430F5438A should be used instead, differences are covered in SLAA419: http://www.ti.com/lit/an/slaa419b/slaa419b.pdf 

    Regards,
    Ryan

  • Hi,

    Could you please provide more information on this? How do you know that the system has been halted? And what kind of system is this? What peripherals are being used?

    Regards,
    Nathan
  • hi Ryan

    The related circuit schematic and code are as follows:

    It is an abnormal phenomenon that system halted when power on, but when I short C32 device,RST to GND, the Circuit is OK.The follow-up can be used normally, and the phenomenon can not be recovered.

    But The phenomenon can be recovered when the following operations are carried out:

    Non contact static electricity test for the whole product,±16KV,20HZ,20pps.

    after 2-3 times the product gets into the abnormal state (no liquid crystal display),which is an abnormal phenomenon that system halted when power on. Unless RST is pulled to the ground.

    It seems that MSP430F5438 is in a certain state of protection, with tweezers short connected to both side of C32 (RST to GND ), the system can be normally on power, and MCU can be started.

    it may be the design of the reset circuit is unreasonable, how much capacitance and resistance should be set?

    Or in what way does it improve? Or MSP430F5438 has some kind of protection mechanism?

  • You should increase the decoupling capacitance at each DVCC pin to at least 4.7 uF + 100 nF. Hopefully the VCORE pin has a 0.47 uF capacitor connected and you are not changing the default PMM levels inside your application. It is recommended that the RST capacitance be reduced to 1 or 2.2 nF. All MSP430 devices are rated up to IEC 6100-4-2 which applies for up to 15 kV (read SLAA530 for more details): www.ti.com/.../slaa530.pdf

    Regards,
    Ryan
  • Hi,Ryan

       Thanks for your reply.

       This problem may involve the reasonable setting of external capacitance and the customer schematic diagram as below.

       How does this match,RST capacitance C98\C99 C32; The DVCC(DVCC1\DVCC2\DVCC3\DVCC4

    ) pin capacitance C30\C31\C34\C35\C36 and the Vcore pin capacitance C33? How many capacitance values are set, setting reference value can avoid this problem? 

      Can you provide internal principle description?

  • CVCORE (C33) is in direct violation of the Recommended Operating Conditions from Section 5.3 of the Datasheet and must be rectified immediately. The bare minimum DCVCC/CVCORE is met with C31 but TI recommends this capacitance value at all VCC pins.

    Regards,
    Ryan
  • Hi Ryan,

    How do we know it's MSP430 core stop running or customer code issue? Is there any ways to verify it?

    While customer doesn't copy TI recommended SCH strictly for years. It hasn't this issue in past. Why a smaller caps on Vcore would lead 430 core to stop running? What's the power performance requirement for Vcore?

    Thanks a lot.
  • Hi Daniel,

    It could be a customer code issue as well given that the subfunctions are not provided. But the fact remains that Vcore capacitance must be 470 nF for proper power-up and operation of the MSP430 device. Other values could have gotten by in past designs but are unsuitable for all device revisions, lots, and board designs

    Regards,
    Ryan

**Attention** This is a public forum