• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 298 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

Debugging stack issues

MSP-FET: 2/3 Faulty MSP-FET flash tools

cameronk
Prodigy 100 points
Part Number: MSP-FET
Other Parts Discussed in Thread: MSP430FR5994, UNIFLASH

Tool/software: CCS 12.8.0.00012, MSPFlasher v1.3.20

Hi,

We have three MSP-FET flash devices (black ones with CE on the back). These three have been working fine, up until two of them just stopped working.

I am trying to debug/program a MSP430F5994 MCU using JTAG 4-Wire, but whenever I try to debug via CCS I receive the following message on the faulty debuggers:

Error connecting to the target: Could not erase device memory

Going further, I tried to dump some information to terminal using the MSP430Flasher.exe tool. On both the faulty debuggers I get one of the following:

MSP430Flasher.exe -n MSP430FR5994 -r [output.txt,MAIN] -z [VCC=3300]

* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM11 <- Selected
* Initializing interface @ COM11...
# Exit: 19
# ERROR: Interface Communication error

or

* Setting VCC to 3300 mV...done
* Accessing device...
# Exit: 16
# ERROR: Unknown device

Using the non-faulty MSP-FET, the device dumps the information fine and the process completes successfully. Note - UniFlash is able to correctly identify the MCU.

I also have a MSP-FET430UIF debugger and have been using that for the past 5 years with no issues.

I have been trawling through these forums with hopes of a solution, but with as many people who have been experiencing the same problem I am yet to find a solution that actually works.

  • 0
    Prodigy 100 points

    To add, running the DETECT option does not work either:

    MSP430Flasher.exe -i DETECT
    * -----/|-------------------------------------------------------------------- *
    * / |__ *
    * /_ / MSP Flasher v1.3.20 *
    * | / *
    * -----|/-------------------------------------------------------------------- *
    *
    * Evaluating triggers...done
    * Executing FET detection sweep:
    # Exit: 19
    # ERROR: Interface Communication error
    *
    * ----------------------------------------------------------------------------
    * Driver : closed (No error)
    * ----------------------------------------------------------------------------
    */

  • 0 in reply to cameronk
    TI__Genius 9570 points

    So for the sample chip, non-faulty MSP-FET works well but faulty MSP-FET cannot work, right?

    If so then it should be the problem with MSP-FET itself(Maybe hardware issue)

    You can try to update the firmware to test first...

  • 0 in reply to Yuhao Zhao
    Prodigy 100 points

    Hi Yuhao,

    I have already attempted a cold boot as per the FET user guide and this did not solve my issue. Very hard to find any consistency between the 3 FET's we have.

    On the working black FET, it can program and debug the FR5994 chip, but on a FR5964 it cannot debug at all (program load errors in CCS). However, if I use the old UIF programmer then it works fine on both MCU's. 

    I've given up on the other two FET's we have that do not work. They were all purchased at the same time, and the two that have failed I know were both working at one point.

    Regards,

    Cameron.

  • 0 in reply to cameronk
    TI__Genius 9570 points

    Hi cameronk,

    Sorry, if you have already tried a cold boot and it did not work, then I think there is no more methods...

**Attention** This is a public forum