xpg

Eclipse plugin for mspdebug and msp430-gcc

250 posts in this topic

I just came home, made coffee, got me a big pot and a cigarette and was thinking of you and the plugin. Powered the PC - notification of your post here. LOL :smile:

 

I have eclipse-cdt installed too. I think you're talking about the package at eclipse.org. Same there, but I will try from scratch again.

 

Is your plugin open source ? I mean, I've just started learning Java but maybe I stumble over the problem by accident...

How do you get the list of supported MCUs ? This seems to fail.

 

Thanks for coming back, I'll do some testing next weekend and report here.

 

Stephan

Share this post


Link to post
Share on other sites

I just came home, made coffee, got me a big pot and a cigarette and was thinking of you and the plugin. Powered the PC - notification of your post here. LOL :smile:

:-)

 

I have eclipse-cdt installed too. I think you're talking about the package at eclipse.org. Same there, but I will try from scratch again.

I wouldn't expect this to be causing any trouble. However, I cannot see what should be causing trouble at all, so it must be something that I find unlikely :-)

 

Is your plugin open source ? I mean, I've just started learning Java but maybe I stumble over the problem by accident...

How do you get the list of supported MCUs ? This seems to fail.

Yes, the plugin is available at gitorious: https://www.gitorious.org/msp430eclipse/msp430eclipse

It's not the prettiest code around, so feel free to ask questions about it.

 

The list of supported MCUs is extraced from the linker scripts from GCC. The code can be found here. It's not a particular elegant way of doing it, but it -- usually -- works.

Share this post


Link to post
Share on other sites

Hello everyone!

 

I'm new to ubuntu, new to eclipse and new to linking toolchains and libraries. So I guess thats the worst combo possible.

 

I've

-downloaded and unpacked the package msp430-toolchain-linux-amd64-3.0.tar.bz2

-downloaded unpacked and run eclipse indigo

 

while trying to merge it together like in: http://youtu.be/XWz_vpkP5QI?t=48s

I was not albe to choose MSP430 Linux 64-bit GCC toolchain.

Thus I have only system tools option in: http://youtu.be/XWz_vpkP5QI?t=2m23s

Or I can browse dirs.

 

Will I get any help here?

Thanks

Share this post


Link to post
Share on other sites

-downloaded unpacked and run eclipse indigo

while trying to merge it together like in: http://youtu.be/XWz_vpkP5QI?t=48s

I was not albe to choose MSP430 Linux 64-bit GCC toolchain.

Thus I have only system tools option in: http://youtu.be/XWz_vpkP5QI?t=2m23s

Or I can browse dirs.

So, first off, the video is somewhat obsolete. I should probably replace it with a new one.

Toolchains are no longer installed through eclipse. You are supposed to extract the toolchain somewhere and tell eclipse about it:

From the menu in Eclipse select MSP430->Tool Manager. Click the "Add..."-button, and browse to the tool-package directory. Select the tool-chain and press the "Activate"-button in order to tell Eclipse to use it.

 

Let me know if that works for you.

 

Cheers,

Paul

Share this post


Link to post
Share on other sites

in Eclipse select MSP430->Tool Manager. Click the "Add..."-button, and browse to the tool-package directory. Select the tool-chain and press the "Activate"-button

Excuse me sir, but where do I find tool-package directory or even tool-chain file? In my msp430-toolchain-linux-amd64-3.0 folder there are no such objects.

 

Cheers,

MK

Share this post


Link to post
Share on other sites

Excuse me sir, but where do I find tool-package directory or even tool-chain file? In my msp430-toolchain-linux-amd64-3.0 folder there are no such objects.

The idea is that the msp430-toolchain-linux-amd64-3.0 folder is the tool-package directory. It should contain a file named "tool.info".

So, if you have extracted the zip file to $HOME/msp430-toolchain-linux-amd64-3.0, then simply choose that directory when adding the toolchain in the toolchain manager.

Share this post


Link to post
Share on other sites

Have you had a look at the Red Hat GCC provided by TI yet? I've tried adding its toolchain to msp430 eclipse plugin, but when creating new projects, the target configuration window only shows "Other" msp430 family. Hence there's no way for me to choose msp430g2553 device.

Share this post


Link to post
Share on other sites

Have you had a look at the Red Hat GCC provided by TI yet? I've tried adding its toolchain to msp430 eclipse plugin, but when creating new projects, the target configuration window only shows "Other" msp430 family. Hence there's no way for me to choose msp430g2553 device.

I have not yet tried out the Red Hat toolchain. But I'm not surprised that the device list will not populate: The way I extract the list from the toolchain is quite ugly and very dependent on the way the mspgcc toolchain works.

How is the Red Hat toolchain compared to the old mspgcc one? Is it ready for prime time yet?

 

I'll put it on my todo list to check it out.

 

Cheers,

Paul

Share this post


Link to post
Share on other sites

It seems to be more promising and "official" than mspgcc; afaik RH GCC has been sent upstream to gcc 4.9. You can find a review from TI E2E community here.

However, some TI intrinsics and macros are still unsupported.

Another problem worth mentioning: I'm unable to access project properties when right-clicking "MSP430 GCC Cross Application" project in ccsv6 beta 4. I don't know whether this is eclipse's bug or your plugin's problem :(

Share this post


Link to post
Share on other sites

Have you had a look at the Red Hat GCC provided by TI yet? I've tried adding its toolchain to msp430 eclipse plugin, but when creating new projects, the target configuration window only shows "Other" msp430 family. Hence there's no way for me to choose msp430g2553 device.

Wait, that's exactly my problem. Does debian ship the RedHat one ? How can I tell one from the other ?

Share this post


Link to post
Share on other sites

@@OppaErich The RH stuff has a different prefix, pretty easy to see the difference msp430-elf-gcc vs msp430-gcc.

 

@op Right now it seems to make sense to just use CCS 6 Beta if you are interested in trying the RH version of msp430 gcc.  CCS 6 is closer to a standard eclipse distribution than the previous versions.  Why flog yourself trying to mix and match?

 

-rick

Share this post


Link to post
Share on other sites

No elf in the name. I found a comment by Peter Bigot in the copyright file, so this looks good. Sadly though, it would have been an explanation for my problems.

 

Cheers @@Rickta59

Share this post


Link to post
Share on other sites

Well, for some reason this is working now. Still siduction but a fresh install - I bought a SSD.  B)

Uhh. I am very happy to hear that. Although I have no clue what was wrong... oh well, let's just hope that it keeps working :-)

 

Cheers,

Paul

Share this post


Link to post
Share on other sites

But I'm not surprised that the device list will not populate: The way I extract the list from the toolchain is quite ugly and very dependent on the way the mspgcc toolchain works.

I have the same problem, different naming of files in the ldscripts folder broke this. Also, I needed to add a link to a new gcc executable. I don't know how would the plugin find the new gcc otherwise.

 

Could anyone help me understand how these gcc linkers work? How does gcc map mcu name (from -mmcu= parameter?) to an ldscript file and why are there multiple files with the same name but different extensions? Sorry, I know Java, but not C and especially not GCC internal workings. Here's how my ldscripts directory (from the new msp430 gcc) looks like: http://pastebin.com/TDxeFEha

From what I understand, mcu names don't match 1 to 1 with ldscript files anymore. Any ideas about how this could be fixed?

Share this post


Link to post
Share on other sites

I have the same problem, different naming of files in the ldscripts folder broke this. Also, I needed to add a link to a new gcc executable. I don't know how would the plugin find the new gcc otherwise.

 

Could anyone help me understand how these gcc linkers work? How does gcc map mcu name (from -mmcu= parameter?) to an ldscript file and why are there multiple files with the same name but different extensions? Sorry, I know Java, but not C and especially not GCC internal workings. Here's how my ldscripts directory (from the new msp430 gcc) looks like: http://pastebin.com/TDxeFEha

From what I understand, mcu names don't match 1 to 1 with ldscript files anymore. Any ideas about how this could be fixed?

 

Basically, we just need a proper way to extract the possible -mmcu values. When I created the plugin I didn't find any way to do that, so I ended up extracting the information from the ldscripts, which happened to match the -mmcu  values. But it was a hack.

It is fairly easy to replace the current mechanism with something else, given that there is a good way to extract the support devices.

Unfortunately, I don't have time to look into this myself at this point. However, if someone comes up with a way to get the mcu list from gcc I'll implement it :-)

Share this post


Link to post
Share on other sites

Hello all!

 

I'm new to Linux Mint 17, Eclipse and to linking toolchains and libraries. Although I have been using CCS5 under Windows XP for a few years.

 

I've

-downloaded and unpacked the package msp430-toolchain-linux-i386-2.1.tar.bz2

-downloaded unpacked and run Eclipse Luna

-Installed the http://eclipse.xpg.dk/ patch into Eclipse

 

My platform is the MSP430G series Launchpad that I'm using in the SBW mode to work with a MSP430F5172 project of mine.

My problem is that I'm unable to load the program into the F5172 board. I am able to load a program into a MSP430G2553 no problem and am able to load the F5172 program when using CCS5 under Windows XP (I have a Win VM in my Linux Mint machine).

When I choose the "rf2500" platform, I get the following error:

 

Args: [/opt/msp430-toolchain-linux-i386-2.1/bin/mspdebug-wrapper, rf2500, prog /home/jim/workspace/UCS_Test/Debug/UCS_Test.elf]
Waiting for mspdebug to finish
MSPDebug version 0.20 - debugging tool for MSP430 MCUs
Copyright © 2009-2012 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to open interface 1 on 006
Initializing FET...
FET protocol version is 30066536
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0x3080
msg28_data: [0x1a bytes]
    30 80 30 10 08 0a b2 5b 94 46 19 00 04 00 f8 fe
    de ee 91 04 11 00 1a 00 04 05
fet: unknown device
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 30066536
Configured for Spy-Bi-Wire
Sending reset...
Set Vcc: 3000 mV
Device ID: 0x3080
msg28_data: [0x1a bytes]
    30 80 30 10 08 0a b2 5b 94 46 19 00 04 00 f8 fe
    de ee 91 04 11 00 1a 00 04 05
fet: unknown device
fet: identify failed
 

So it's not recognizing the F5172 signature.

 

If I select the "tilib" platform, I get an error window saying the file libmsp430.so file cannot be found. I have located a copy of this file but don't know which directory to put it in? ... and if this will work or not?  I have read the post about the Olimex platform supporting the F5172 with a possible workaround but it involves recompiling a fet_core.c file after making changes to it but I don't know how to do that.

 

Anyone know what I can do besides going back to CCS5 on Windows?

Thanks

Jim

Share this post


Link to post
Share on other sites

Hello all!

 

I'm new to Linux Mint 17, Eclipse and to linking toolchains and libraries. Although I have been using CCS5 under Windows XP for a few years.

 

I've

-downloaded and unpacked the package msp430-toolchain-linux-i386-2.1.tar.bz2

-downloaded unpacked and run Eclipse Luna

-Installed the http://eclipse.xpg.dk/ patch into Eclipse

 

My platform is the MSP430G series Launchpad that I'm using in the SBW mode to work with a MSP430F5172 project of mine.

My problem is that I'm unable to load the program into the F5172 board. I am able to load a program into a MSP430G2553 no problem and am able to load the F5172 program when using CCS5 under Windows XP (I have a Win VM in my Linux Mint machine).

Anyone know what I can do besides going back to CCS5 on Windows?

Thanks

Jim

 

Hi Jim,

 

This is caused by an old version of mspdebug bundled with the msp430-toolchain.

I will try to get some time to rebuild the pre-build toolchain to include a newer version of mspdebug.

 

Cheers,

Paul

Share this post


Link to post
Share on other sites

Hi Jim,

 

This is caused by an old version of mspdebug bundled with the msp430-toolchain.

I will try to get some time to rebuild the pre-build toolchain to include a newer version of mspdebug.

 

Cheers,

Paul

Paul,

Thanks! No real hurry now as I have worked around this issue... I acquired a MSP430FR5969 Launchpad with a newer FET emulator. I then installed CCS6 on my Linux Mint machine. Using this newer Launchpad as a SBW host to my F5172 board (same as I did with the value-line Launchpad), I am now able to run and debug my application on it via CCS6.

Thanks again!

Share this post


Link to post
Share on other sites

Paul,

Thanks! No real hurry now as I have worked around this issue... I acquired a MSP430FR5969 Launchpad with a newer FET emulator. I then installed CCS6 on my Linux Mint machine. Using this newer Launchpad as a SBW host to my F5172 board (same as I did with the value-line Launchpad), I am now able to run and debug my application on it via CCS6.

Thanks again!

This scheme has only been partly successful! The F5172 program compiles and loads into the device fine but the debugger does not work well. I've had to resort back to the CCS5.4 app under the VirtualBox VM on my Linux machine to have any success here.

Share this post


Link to post
Share on other sites

This scheme has only been partly successful! The F5172 program compiles and loads into the device fine but the debugger does not work well. I've had to resort back to the CCS5.4 app under the VirtualBox VM on my Linux machine to have any success here.

 

Thanks for the updates. That sounds somewhat annoying. I'll try to allocate some time to rebuild the tools so that you can give Eclipse and the MSP430 plugin a try.

(I'm just really busy these days, but I'll get around doing it :-))

 

Cheers,

Paul

Share this post


Link to post
Share on other sites

Hi,

 

just some positive feedback. I've moved from Debian to Fedora 21. Using the Fedora toolchain installed via yum and Juno the plugin works fine.

 

Indigo crashed during startup probably due to Java 8 being default for Fedora 21.

 

Thanks,

Stephan

Share this post


Link to post
Share on other sites

Hi

I realize that this topic is a little old but I hope that someone will be able to help me. I installed toolchain and eclipse both on a mac and windows. Everything was going great until I come to a point where i have to activate msp 430 toolchain. I tried on both systems with 32bit and 64bit versions and different location of the toolchain folder. Whenever I create a new project and go to preferences I cannot display the list of MCUs. It's just empty. Is there any solution to the problem? Can anyone help?

 

 

Best Regards

Robert 

Share this post


Link to post
Share on other sites

Hi,

 

Does this plugin work with the TI version of the MSP430GCC compiler?

 

Thanks in advance.

Hi,

 

I'm not quite sure. It haven't used the plugin myself for a long time myself.

It has generally been far too long since I've had time to do anything with an MSP430 chip (which is also why I haven't really been active in here).

 

But if you try it out please let me know how it goes.

bluehash likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now