• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 447 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.

MSP430F169: New MSP-FET for very old MCU

Moti Esh
Prodigy 60 points
Part Number: MSP430F169
Other Parts Discussed in Thread: MSP-FET, MSP-FLASHER

I want to buy a new MSP-FET for very old MSP430F169 (more than 10 years). Does I need some down grading (A nightmare) or it will work as is?

  • 0
    TI__Guru 56685 points
    Hello Moti,

    Our newest MSP-FET supports all programmable MSP430s.

    For a full overview of our debuggers and what devices and features they support, please see Table 1 in the MSP Debugger's User guide (http://www.ti.com/lit/slau647 ) .
  • 0 in reply to Jace H
    Prodigy 60 points

    I have a MSP-FET430UIF, to use it I need to fit the application to the driver to the firmware to the DLL (about 100 trials) otherwise it doesn't work. Does it the same with the new MSP-FET?

  • 0 in reply to Moti Esh
    TI__Guru 56685 points
    Hello Moti,

    I'm not sure of the issues you are having without more detail, however, as shown in the document above, both the MSP-FET and the MSP-FET430UIF have the capability to program all programmable MSP430 and CC430 devices.

    Depending on the FW on your MSP-FET and the debug stack on the IDE (CCS, IAR, etc.) or programmer SW (MSP-FLASHER, Elprotronic Fet-Lite Pro 430, etc.) it may ask you to "upgrade" the firmware on the MSP-FET. The IDE/Programmer will ask you to do this regardless if the FW on your debugger is newer or not. This is due to the IDE/Programmers just doing a simple check if the FW on the debugger is the same as it knows to be the latest or not. If you know on IDE is up to date, and you upgrade the debugger FW to that FW, then if you got to another IDE or an older version, you can safely ignore the upgrade request in most situations. This erroneous FW upgrade request is most apparent when switching between newer and older versions of an IDE or switching from the most up to date version in CCS vs say IAR that may not be on the newest debug stack yet.

**Attention** This is a public forum