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.

MSP430F5638: MSP-FET CCS and command line options to reset MCU and test MSP-FET

Part Number: MSP430F5638
Other Parts Discussed in Thread: MSP-FET

Tool/software:

Custom SBC using an MSP430F5638 and an MSP432P401R. Generally code working very well on both MCU's. Tried sending data from 430 SPI (3 pin + STE as GPIO CS) to 432 SPI (4 pin) and may have fried the 430!

Using CCS ver. 12.8.1.00005. What tools are available for the MSP-FET from within CCS, and the command line - to try and reset the 430 and at least confirm the MSP-FET is working ok?

I've found similar tools for the XDS110 within CCS, and at C:\ti\ccs1230\ccs\ccs_base\common\uscif\

  • Hi,

    I do not think we have any tool for MSP-FET integrated in CCS. If you want to reset the MCU, there should be reset device button in the CCS debug interface. 

    For debugging the SPI communication issue, I would suggest to capture the SPI signals with a logic analyzer first to check if there is anything wrong on the bus.

    Best regards,

    Cash Hao

  • I'm already using a scope on the 430 SPI bus, was working fine until this crash. Current 430 MSP-FET Error message below.

     

  • Hi,

    I have not encounter this kind of issue before. It seems that the XML file is damaged in the project. I would suggest to debug with a different project and test if the MSP-FET can work. 

    Best regards,

    Cash Hao

  • Yesterday I tried different PCB's, different MSP-FET, different USB port - they all work with a different project. This specific CCS project, which was running when things locked up, is definitely corrupted. Can't get it running on any PCB. A symptom is the project does not show up in the Run | Load list, and shows the error message above.

    Will create a new version of the corrupted project. And try to run a working project in debug mode on the possibly dead PCB's MSP430, just to see if it's still there, LCD is blank white.

  • I found the problem. I have several different PCB holders I use for assembly / rework / HW SW dev testing. All have worked well for years, I removed the PCB holder and reran the same problem PCB and was able to load and run code from different projects. I had to recreate the corrupted project and it is running fine now on the same PCB.

    This holder uses spring loaded posts with an insulating plastic washer on the top and bottom of the gripping surface. They all visually look good, and the posts are coated metal - no visible bare metal. Also just checked with an ohmmeter and the posts read as open circuit.

**Attention** This is a public forum