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.

Strange Linux policy of TI

Other Parts Discussed in Thread: MSP-EXP430FR5739, ENERGIA, MSP-GANG, MSP430F5510

Hi folks,

I am a bit astonished about the Linux policy of TI.
On the one hand it will be pronounced that Linux is supported for the Launchpads (indirectly), on the other hand it seems that it does not work.
Or I am to unhandy to deal with it. I hope I can clarify  this here and I do this on the right way.

First of all I bought 4 Launchpads over the time, because I really like the less expensive and well equipped devices:
http://www.ti.com/tool/MSP-EXP430G2
http://www.ti.com/tool/msp-exp430fr5739
http://www.ti.com/tool/ek-lm4f120xl (Stellaris)
http://www.ti.com/tool/launchxl-f28027 (C2000 Piccolo)
and the fancy watch http://www.ti.com/tool/ez430-chronos.
OK, the Stellaris and C2000 Piccolo are no MSP430, but I think the case is the same.

All of them are advised as programmable with CCS5. And the Code Composer Studio exists in Windows and Linux version. So I thought the LaunchPads are programmable under Linux with CCS5.  

On Windows I can program the MSP-EXP430G2, on Linux I can't. The error "Error initializing emulator: No USB FET was found" appears. With the MSP-EXP430FR5739 the same problem.
The point is, it is a known  issure:
JohnS (TI Employee):
"Per,

The LaunchPad is not supported on Linux at this time.

John"
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/171173/688729.aspx#688729 
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/221603.aspx 

So, why is that Link broken:
X is Programmable with CCS5-->CCS5 exists for Linux-->X is programmable on Linux? ;) 

At least the EXP430G2 is programmable on Linux:
http://hackaday.com/2010/08/11/how-to-launchpad-programming-with-linux/
http://losinggeneration.homelinux.org/2010/07/02/msp430-launchpad-on-linux/
But it bypasses the CCS5. Why is it not possible to include the tools (MSPGCC & MSPDEBUG) in the tool chain of CCS5? Or is it?
What is with the other LaunchPads, are there solutions for programming on Linux?
Or what else can I do to program MSP430-Controller with CCS5 on Linux? Even without a LaunchPad?

___

Similar problem with other tools. The tool FRAM_GUI is a Windows binary. But the source is open. Exists a compilation for Linux already?

Thanks to all
Fabian Hoemcke
Berlin

Code Composer Studio Version: 5.4.0.00091
- installed as user
- install_drivers.sh executed as sudo
Ubuntu 13.04 (32bit) 

 

  • Why not install virtual machine?

    You can find more info on Linux support here:http://processors.wiki.ti.com/index.php/Linux_Host_Support

    Regards,
    Maciej 

  • Thanks Maciej,

    I am using a Dell Inspiron Duo with an Atom processor.
    The only device I have right now.

    I think this would be to much for it. Windows 7 is already running on it, as slow as Windows is.

    Thank you for that link, I used this page for installing CCS5 on Linux.

    Regards
    Fabian 

  • I finally got my Ubuntu 14 / CCS-6.10 / Open Source Tool Chain / Launchpad debugging to work using the mspdebug server:

    mspdebug rf2500 gdb

    CCS C++ Remote Application configuration:

    Debugger:
    Main:
    GDB Debugger: /opt/ti/gcc/bin/msp430-elf-gdb
    GDB Command File: ~/.gdbinit
    Using GDB (DSF) Manual Remote Debugger Launcher
    Connection:
    Type: TCP/IP
    Host name or IP Address: localhost
    port: 2000

    Quite an ordeal but worth the effort in the end.
  • You will need to create a ~/gdbinit file:

    set remoteaddresssize 64
    set remotetimeout 999999

    I will put together a complete step by step.

  • Christopher Smith54 said:
    set remoteaddresssize 64
    set remotetimeout 999999

     In answer also to original post, on installscript an MSP430 installation shell is present, after launching this you can debug MSP430 on CCS but not with TI on launchpad G series, 5529 and FR are supported and work well, so attaching G to these one work fine.

     Again this remain unsupported when is perfectly supported by energia and MSPDebug, just on MSPDebug rule file must be created.

  • Christopher,

    I would like to see how you setup this in linux as well.

    It also perplexes me greatly why TI wont support CCS and launchpad g2 but works just fine on windows.

    I'm really curious if it's truly a technical reason or something else.

  • Jens Jensen1 said:
    It also perplexes me greatly why TI wont support CCS and launchpad g2 but works just fine on windows.

     This is not really true, winzz has some bug on drivers used by Ez series debugger and sometimes burn them...

     On Linux this bug is not present and connection is more and more stable...

    Jens Jensen1 said:
    I'm really curious if it's truly a technical reason or something else.

     This is a very strange way they won't support where it can work better.

     Also other tools are not supported in Linux CCS version like Elprotronics and Olimex. Olimex ISO series of debugger is very useful when isolation is needed, Elprotronics is a very good tools (expensive too) but again appreciated for ruggedness...

  • Roberto Romano said:

    This is a very strange way they won't support where it can work better.

     Also other tools are not supported in Linux CCS version like Elprotronics and Olimex. Olimex ISO series of debugger is very useful when isolation is needed, Elprotronics is a very good tools (expensive too) but again appreciated for ruggedness...

    I guess that other tools are not supported in Linux, also as standalone (from Elprotronic/Olimex side), without CCS.

    Anyway, my msp-gang like flasher (not related to TI interface / dll) working on Win / Linux as standalone.

    ThinkPad:~/msp430$ flash -p /dev/ttyACM0 -f test_msp430f5510.txt -e -w -v -crcr -mrr

    File: "test_msp430f5510.txt"
    Address: 08000  Words: 16384
    Size: 32768 bytes

    Get Device
    # JTID Fuse Device Core Hard Soft LotWafer DieX DieY
    0  91   OK   3081  2106  10   10  B7A50951 0A00 1100
    1  91   OK   3180  1104  12   12  013BB046 0D00 1E00
    2  91   OK   5435  0100  10   10  ADE98146 0400 2000
    3  91   OK   3180  1104  12   12  013BB046 1200 1E00
    4  91   OK   3080  1104  30   10  B15B9446 2000 1700
    5  91   OK   3180  1104  12   12  34449346 2200 3600
    6  91   OK   3881  1106  10   10  219CA446 1800 0F00
    7  91   OK   3180  1104  12   12  013BB046 2700 2E00

    Erase

    Write
    Time: 423 ms  Speed: 75.7 KB/s

    Verify
    Time: 159 ms  Speed: 201.3 KB/s

    CRC Rev
    File  #0   #1   #2   #3   #4   #5   #6   #7
    C841 C841 C841 C841 C841 C841 C841 C841 C841
    Time: 40 ms  Speed: 800.0 KB/s

    Marginal Read Rev
    Mode File  #0   #1   #2   #3   #4   #5   #6   #7
      0  C841 C841 C841 C841 C841 C841 C841 C841 C841
      1  C841 C841 C841 C841 C841 C841 C841 C841 C841
    Time: 460 ms  Speed: 69.6 KB/s

    Release Device

    Total Time: 1268 ms

    ThinkPad:~/msp430$

**Attention** This is a public forum