• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 79 subscribers
  • Views 2190 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR58891: The Chip died?

Gary Armstrong
Expert 1845 points

Part Number: MSP430FR58891
Other Parts Discussed in Thread: MSP430FR5969, , MSP-FET

The chip has failed. Can not attach with the debugger. Can not download to it. I have 3.3V at all VCCs. I double checked power and ground connections.There is no voltage going to the 16MHz crystal connection to XT2 (pin 54). I'm using IAR Embedded Workbench 6.50.2 with the MSP430 USB-Debug-Interface (MSP-FET430UIF).

I have tested my tools out with the LaunchPad msp430fr5969 demo board and everything is working fine.

Its been working for a couple of months while I have been doing development but now nothing? It quit this weekend and would not reboot, had to download the program to it, but it did restart. I have a LabVIEW interface thru a serial/USB port monitoring  24/7 for the past couple of months. It died overnight and will not do anything?  Can I get some suggestions?

  • 0
    TI__Guru 56685 points
    Hello Gary,

    I assume you have a custom board for the MSP430FR58891. What kind of error messages do you see from IAR when trying to connect to the device? Can you try to download a simple blink LED program to it?
  • 0 in reply to Jace H
    Expert 1845 points

    Yes on the custom board. When I down load the FW a download dialog pops up and the program hangs. At that point I have to kill the application (IAR). I can still download a blink program to my Launchpad demo board, so the tool still works. I have another board showing up next week and plan to put a simple blink program on it and let it run for several days.

  • 0 in reply to Gary Armstrong
    TI__Guru 56685 points
    Hello Gary,

    It is unusual that the dialog box hangs and gives you no information. Normally you would get a "Could not Identify Target" or " Target Voltage is not correct" , or "Target is not connected". From there we would debug your SBW connections by ensuring you have the right circuitry on the board or make sure the correct pins are connected to the JTAG header on the MSP-FET depending if the device is self powered or powered by the MSP-FET. With no additional information here however, I am unsure on how to proceed. My first thoughts are maybe you have a short somewhere on the board or the device could of been over-volted and damaged. What kind of application are you designing? Is there any risk of over-voltage to the part? What kind of power source are you using? Do you have the ability to swap the chip out with a new one?
  • 0 in reply to Jace H
    Expert 1845 points
    64 pin PM or RGC package (p. 10 on the 58891 Data sheet). It's soldered in place and I don't ave tools to replace. I will ask the supplier if he can replace the chip. As I have about 50 wires going from bread boards to DB15 connectors with terminal strips it is entirely possible that something came loose. I don't see any loose connections. I tested all connections from the power supply. I have an old HP power supply powering the board. However it was running when I left the lab as I have a heartbeat test on the LabVIEW program monitoring the chip and the log indicates that it ran for a few hours before quiting. I can email you the schematic for the board. The design is based on a 2272 design that has run in the field for years. My client is upgrading to a 58891 to allow for buffering the data. We are going to take the two 3.3V linear regulators supplying the AVCC and DVCC and consolidate to one as suggested in the data sheet.
  • 0 in reply to Gary Armstrong
    TI__Guru 56685 points
    Gary,

    Can you do test with the multimeter to make sure every wire you have soldered is still connected properly? Normally the diode/short detection with one probe on MSP pin and the other at the end of the wire will tell you if they are connected. This is where I would start. If your board was working before then your schematic should be ok, but if you want me to check it, send me a PM with the details.
  • 0 in reply to Jace H
    Expert 1845 points
    Have asked the vendor to verify that the kludge wire between the digital and analog gnds is still good. I sent the board back to the vendor Monday of Tuesday. No response as of yet. I sent you a friend request for your email so that I could send you the schematic.
  • 0 in reply to Gary Armstrong
    TI__Guru 56685 points
    Hello Gary,

    I do not see anything glaringly wrong with your schematic. As you mentioned, tying AVSS and DVSS together as well as AVCC and DVCC together is recommended for most applications. As another test, can you try to reprogram the device with only the JTAG, VCC (DVCC+AVCC), and GND (DVSS+AVSS) connections? This way we isolate the chip from all other components of your board to see if it can program correctly.
  • 0 in reply to Jace H
    TI__Guru 56685 points
    Hello Gary,

    Have you been able to resolve your issue? If so can you post the resolution?
  • 0 in reply to Jace H
    Expert 1845 points

    No reply back from the board manufacturer. However, the board manufacturer and I were developing in parallel. I would send him FW changes so that we worked off the same version of code. He has never seen this type of problem.  I have been "hot " swapping the JTAG connector in the evenings to keep the sleep mode on m Windows7 computer from killing the uC in the evening. I suspect that this may be the source of my problem. Now I power the uC down, remove the USB cable to the MSP-FET430UIF and then re-power the system.

**Attention** This is a public forum