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.

MSP-FET 430UIF USB-Debug-Interface error

Other Parts Discussed in Thread: MSP-FET, MSPDS, MSP430BT5190

I have a MSP-FET 430UIF USB-Debug-Interface that I am trying to set up using the FET-Pro430 Flash Programmer Lite software.

After installing the software (which included installing a USB driver and updating the firmware on the Interface device), when I click "Verify Security Fuse", I get an error that says that the Target Microcontroller is not responding.

I'm confident that my microcontroller is functional because we have another MSP-FET 430UIF USB-Debug-Interface in the office (which was installed by someone who is no longer in our office) and this microcontroller responds without error using that other Interface setup.

I'm also confident that our physical connections are not the issue because if I use this debugger with the other (working) station's connectors, I get this same error.

I feel as if I'm missing something in the installation procedure, and I was wondering if someone could help me troubleshoot the errors I am getting.

  • Hello,

    So one MSP-FET430UIF tool operates correctly in the exact same test setup whereas the other does not? This could indicate an issue with the driver/firmware update. Can you please confirm inside of your computer's device manager that the MSP-FET430UIF is enumerating as "MSP-FET430UIF - CDC" under your COM ports? Also, inside of FET-Pro430 please go to About/Help -> About Software and report the MSP-FET430UIF Firmware. Do you get any similar errors if using a different IDE like CCS or IAR? The solution may require an upgrade and downgrade of the MSP-FET430UIF MSPDS: processors.wiki.ti.com/.../MSPDS_Debugger_Up-_and_Downgrade

    Regards,
    Ryan
  • Thank you for your help.

    Here is how the driver is being reported in my Device Manager.


    Here is the information reported in About/Help -> About Software

    This is the setup that does not work:

    This is the setup at the PC station that does work:

    I haven't tested this setup with CCS, IAR or other IDEs because they are not part of the workflow at this station.

    I have performed the downgrade procedure located in the Tools menu, but the same error occurred.

    After that I ran the upgrade procedure in the Tools menu (which required me to update the firmware) and the same error still occurs.

  • Does the MSP-FET430UIF run properly on the working PC station that uses software version 3.1-2? What specific MSP430 device are you trying to program?

    Regards,
    Ryan
  • Yes, this MSP-FET430UIF has worked at that station. I think I can recover the installation file for that version of the Fet-Pro430 Lite software from that station. I'll install that version at this station and let you know how it goes.
  • This is quite strange since I've successfully used the MSP-FET430UIF with Firmware v3.05 and FET-Pro430 v3.4. However I still do not know specifically which MSP430 device you are trying to communicate with. I'm looping in an Elprotronic expert to see if they can provide any extra insight into this matter.

    Edit: Along with the MCU please also provide whether you are using SBW or JTAG interface.

    Regards,
    Ryan

  • I uninstalled Fet-Pro430 v3.4 and installed version 3.1-2 on the non-working station to make the software on both the same.

    I'm still getting the same error.

    Here is About Software screen on the non-working station, now:

    I'm attempting to communicate with a MSP430BT5190 using JTAG.

  • Just to confirm progress so far:

    1. Have you been able to communicate with a MSP430BT5190 device using a MSP-FET430UIF and FET-Pro430 on the working station?
    2. Do you have two separate MSP-FET430UIF tools, both of which work on the old station and do not on the new station?
    3. What are the OS versions of each work station?
    4. What is the common denominator, the MSP-FET430UIF tool or the FET-Pro430 software?

    Regards,
    Ryan
  • 1. Yes

    2. The configurations I've tried include:

    PC-A + ConnectorsA + DebuggerA = Works (Working Station)
    PC-A + ConnectorsA + DebuggerB = Works
    PC-B + ConnectorsB + DebuggerB = Doesn't Work (Non-Working Station)
    PC-B + ConnectorsA + DebuggerB = Doesn't Work

    I haven't tried other configurations because I don't want to accidentally damage the working configuration because we use it daily.

    3. Both are Windows 7

    4. I'm not sure what you mean. I have two debuggers that are the same model, and I have attempted to install the same versions of the software on the two separate PCs. I thought that the connectors themselves might be the problem, but if I take the connectors from the working station and attach them to the nonworking PC and debugger, I get the same error.
  • After working with you and feeling more comfortable with the software, I got authorization to do further testing with the working station's components. I discovered the following:

    PC-B + ConnectorsA + DebuggerA = Works
    PC-B + ConnectorsA + DebuggerB = Works (which didn't before, so maybe changing the software on this machine helped)

    So it does seem like ConnectorsB is still a problem.
    We quickly built a ConnectorsC and the results were:

    PC-B + ConnectorsC + DebuggerB = Works.

    So I think we're good to go.

    Thank you so much for helping me work through this.

**Attention** This is a public forum