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

how to update the msp430 jtag tool on Linux.

Eric Decker
Expert 1420 points
Other Parts Discussed in Thread: MSP-FET, MSPDS

The current (April 2016) situation with the msp430 USB Debug Interface (Jtag pod) is very confusing. I have ordered various units from TI as well as various distributors.  Sometimes I get V3 sometimes I get V2.   I've been trying to get the V2s updated to V3 but haven't found a good method.  Here is what I know...

1) The MSP-FET430UIF is the older (gray body).  If you order it from TI or a distributor you get it loaded with V2 fw.

2) You can also order a MSP-FET.  It is the latest version and comes in a smaller form factor and a black case.  It comes with V3 fw.

The big question is how to get the V2 FETs upgraded to V3.  The TI page processors.wiki.ti.com/index.php/MSPDS_Debugger_Up-_and_Downgrade only references windows and I'm exclusively on Linux.

MSPFlasher doesn't seem to know how to deal with V2 FETs.

I've tried installing CCS 6 onto my Linux box but it doesn't seem to understand V2 FETs.

There is a tool, Uifv3Updater that the mspdebug package knows about that used to work but now seems to break setting Vcc.  I can work around that by manually flashing the V3 into the grey body FETs but that is a pain.

How can I update from V2 to V3 on a Linux box?

thanks.

eric

  • 0
    Expert 1420 points

    I've done some more research into this problem.  In particular I've looked at the source code that comes with MSPFlasher.

    FETs are found using library calls into libmsp430.so V3 library.

    When running on Windows, it doesn't have a problem finding both V2 and V3 FETs.  MSPFlasher will find the V2 FET and offer to update the FW to V3.

    On a Linux box however, the V2 FETs aren't found.

    The routine MSP430_GetNumberOfUsbIfs and MSP430_GetNameOfUsbIf (libmsp430.so routines) are used to find FETs.  And on Linux the library doesn't find the V2 FETs so MSPFlasher fails to update the V2 FET.

  • 0 in reply to Eric Decker
    TI__Intellectual 1140 points

    Hello Eric,

    The libmsp430.so is the driver, which is doing all the communication with your debug probe. Basically there are to major versions of this driver available, the V2 and the V3. V2 is a Windows only driver and includes not support for Linux. V3 is is supporting Linux, Mac and Windows.


    I think the FET you are using is currently a V2 FET that is not supported by linux. I would suggest you do a major update on a Windows machine. V2 --> V3. After that you can use your FET on linux.

    Thanks & Regards

    Florian

  • 0 in reply to Florian Berenbrinker
    Expert 1420 points

    Hi Florian.

    I know about V2 and V3 and also that I can use Windows to migrate to V3 from V2.

    It is clear all the data paths exist h/w wise because I use the same machine to run Windows and Linux.

    I've also managed to modify the FET on Linux using UifV3Updater (but it doesn't have the correct library and it breaks the FET).  I can then fix this by forcing the FET to have a current V3 fw load.

    In other words, the library on Linux could update V2 to V3 if it wanted to but currently can't find the V2 when it mounts (as /dev/ttyUSBn) on Linux.

    It would be wonderful if you guys fixed this.  Maybe you could pass this on to the guy who actually wrote the program.

    eric

**Attention** This is a public forum