• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 80 subscribers
  • Views 1335 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.

Migrating from msp-fet430uif to the new msp-fet

Christopher Carl
Intellectual 350 points
Other Parts Discussed in Thread: MSP-FET, ENERGYTRACE, MSP430F2274, MSP-TS430DA38, MSP430G2231, MSP430G2533

Hello,

We recently purchased the new msp-fet debugger/programmer device as we discovered the msp-fet30uif was being discontinued.  However, I am now running into quite a few problems trying to get the new device to work.

I am using Code Composer Studio V 5.4.0.00091.  When i try to load my program onto a board, an error pops up that there is no device available.

I also use Elprotronics Fet-Pro430 Lite, and that as well is having issues, flashing an error that the msp430.dll has trouble initializing.  So i upgraded to the latest Fet-Pro430 Lite (V3.3), and while I don't get the .dll error with the new msp-fet, now NEITHER the msp-fet nor the msp-fet430uif will load code or read memory, each of which fails at verifying the security fuse.

Has anybody made the switch from the msp-fet430uif to the msp-fet, and/or can anyone provide any insight as to what could possibly be my problem?

Thanks in advance!

  • 0
    Guru 227245 points
    I guess, CCS doesn't support tools that were developed after its own release date. When CCSV5 was released, the MSP-FET wasn't there. So it isn't supported.
    You'll need to upgrade to CCS V6 to use the MSP-FET.
    Likewise, the Elprotronic tool needs a MSP430.DLL that has support for the MSP-FET built-in. As well as the (USB) drivers for MSP-FET. I'm not sure the tool comes with an own copy of the TI MSP430.DLL or uses the one of your CCS installation.

    Try installing the latest CCSV6 free version (or update your full license), along with the MSP-FET drivers and the MSP430.DLL. The Elprotronic software should work then too. The older FET430UIF might require a firmware update.
  • 0 in reply to Jens-Michael Gross
    Guru 14640 points
    Jen-Michael:Is this also true for IAR Tools?
    If I am using an older version, do I need to update to the latest version in order to use the MSP-FET?
    Here is a quote from the Hardware User's Guide (slau278t):
    "Make sure to use the latest IDE version, otherwise the USB drivers might not be able to recognize the MSP-FET."
  • 0 in reply to Jens-Michael Gross
    Intellectual 350 points
    Thanks for the quick response! I was afraid I was going to have to upgrade to CCSv6, but have already prepared myself for that being a possibility.

    I did manager to get the Elprotronic tool to work. I first had to upgrade to the latest version, and then I realized my connection type got changed from Spy-bi-wire to JTAG. So switching that back gave me the results I was looking for.

    Thanks again!
  • 0 in reply to Todd Anderson78572
    Guru 227245 points
    Todd, of course even IAR doesn't support devices that weren't there when the IDE was released. :)
    I don't know how close the MSP-FET command structure is to the older FET430UIF. At least the support for EnergyTrace is new and requires an IDE update, but maybe the old IDE's debugger still works as soon as you got a newer MSP430.DLL and the USB drivers running.
    Hence my suggestion of installing the CCSV6 free version, which will of course come with the USB drivers and the MSP430.DLL. (same for the free IAR version).
    IIRC, you can install CCS on a different system and find the USB drivers (and the MSP430.DLL) in the installation path and copy it over.
  • 0 in reply to Jens-Michael Gross
    Prodigy 50 points

    Hi, I have ended up in a similar situation.

    I just switched my old MSP-FET430UIF to a new MSP-FET, using the latest IAR 6.20, but when trying to debug I get the device not found error:

    Thu Jan 15, 2015 12:05:08: Using license: Standalone license - IAR Embedded Workbench for Texas Instruments MSP430 6.20 
Thu Jan 15, 2015 12:05:09: Firmware version 3.4.3.4 
Thu Jan 15, 2015 12:05:09: Interface dll version 3.4.3.4 
Thu Jan 15, 2015 12:05:09: Unknown device : (OpenDevice) , Device=MSP430G2xx3, PwLength=0x0 
Thu Jan 15, 2015 12:05:12: Fatal error: Could not find device (or device not supported)   Session aborted!

    If I connect the 14-pin target-cable to the old MSP-FET430UIF instead (and disconnecting the MSP-FET from the computer) then it works and has worked for the past months.

    In my device manager I see "MSP Application UART1 (COM14)" and "MSP Debug Interface (COM13)", is this correct?

  • 0 in reply to COLA
    Guru 14640 points

    COLA:

    We recently procurred an MSP-FET, and I also have IAR 6.20 - with the F5528 and F5529, I had no problem connecting. One of the first things that I remember was the MSP-FET needed an update, but after that I was able to detect the processor, download and debug my code.

    Not sure if this is related to the device you are using or not - you may want to try a different MSP (if you have one) to see if it is related only to the device you have?

     

  • 0 in reply to Todd Anderson78572
    Prodigy 50 points

    Yes the MSP-FET was also upgraded for me when I first connected with IAR6.20.

    I have tested some more now with different MCUs/boards:

    1) MSP430F2274 on a MSP-TS430DA38 target board with 14-pin cable connected directly to 14-pin connector - working.

    2) MSP430F2274 on a MSP-TS430DA38 target board with Vcc, Vss, TEST and RST connected directly from MSP-FET to MCU pins - working.

    3) MSP430G2231 on a LaunchPad board - not working.

    4) MSP430G2533 on my custom PCB (equivalent to the second and third connection) - not working.

    I'm using the Spy Bi-Wire (2 Wire JTAG) connection in tests 2, 3 and 4: 

    http://processors.wiki.ti.com/index.php/JTAG_%28MSP430%29#Spy_Bi-Wire_.282_Wire_JTAG.29_for_MSP430F2xx.2C_MSP430G2xx.2C_and_MSP430F4xx,

     

    I have tried to manually select the Debug protocol but it didn't change anything, still the same error.

    Maybe the value-line MCUs are not supported by the MSP-FET?

  • 0 in reply to COLA
    Prodigy 50 points
    It works if I disconnect TEST/VPP (pin 8 on MSP-FET)...

**Attention** This is a public forum