Jump to content
43oh

programming a MSP430G2955?


Recommended Posts

  • 2 weeks later...
  • Replies 84
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Picture (MSP430F2132) from http://e2e.ti.com  

Good news for those who want to use G2955.   You can program it with the new F5529 LaunchPad!  

Hi kendalls,   Sorry for all of the frustration this has caused. I thought I might be able to provide some useful information for others trying to use G2955 in the future and an update on some of th

Posted Images

attachicon.gifmsp430G2955_Development_Board.jpg

 

Rob's boards are in. I'll be sending a couple down to him. The rest(first batch) will be in a GB. Thanks for the quick design Rob.

 

Yay!

 

I too managed to program a MSP430G2955 by targetting it as a F2274. Didn't have any success with the Blinky yet (but haven't spend too much time on it yet).

Looking forward to see official support in GCC.

Link to post
Share on other sites

I too managed to program a MSP430G2955 by targetting it as a F2274. Didn't have any success with the Blinky yet (but haven't spend too much time on it yet).

Looking forward to see official support in GCC.

 

Here is 55.75 KB (2100 - FFFF) firmware with test pattern (and P1.0 blinking) that I prepared for MSP430G2955, so you can try it. Of course, if you destroy flashing tool and/or target device, it is not my problem.

 

sbw_test_56.rar

Link to post
Share on other sites
I too managed to program a MSP430G2955 by targetting it as a F2274. Didn't have any success with the Blinky yet (but haven't spend too much time on it yet).

Looking forward to see official support in GCC.

 

TI hasn't even acknowledged my proposal that they support my efforts in maintaining mspgcc during the transition to the new RedHat toolchain.  I'd like to provide this support for the community, but a new release is a fair amount of effort and I have to focus my time on things that might eventually produce income or at least are of direct interest to me personally.  At this time I have no plans for another mspgcc release.

Link to post
Share on other sites

TI hasn't even acknowledged my proposal that they support my efforts in maintaining mspgcc during the transition to the new RedHat toolchain.  I'd like to provide this support for the community, but a new release is a fair amount of effort and I have to focus my time on things that might eventually produce income or at least are of direct interest to me personally.  At this time I have no plans for another mspgcc release.

 

That's very understandable. Is there anything we can do to help you? Tests, or code that needs to be updated?

Link to post
Share on other sites

That's very understandable. Is there anything we can do to help you? Tests, or code that needs to be updated?

Thanks, but there's nothing technical in the way of doing this.  I don't have any of the newest chips to use, but I have no reason to believe that they would cause trouble.  It was only the change to the FRAM interrupt vectors that caused a headache that prevents using any of the current compiler releases with an updated msp430-libc, and I already have the required compiler modifications in place and have been using it for my own stuff.

 

The issue with a release is that it's 20+ hours effort to do the git repository manipulations to pull patches into the right branches, build the system on a couple Linux releases, and run the test suite on a couple different types of boards.  The next release should be an LTS one, probably based on 4.7.2, which requires a little more testing since it's a pain to put out patches.

Link to post
Share on other sites

Thanks, but there's nothing technical in the way of doing this.  I don't have any of the newest chips to use, but I have no reason to believe that they would cause trouble.  It was only the change to the FRAM interrupt vectors that caused a headache that prevents using any of the current compiler releases with an updated msp430-libc, and I already have the required compiler modifications in place and have been using it for my own stuff.

 

The issue with a release is that it's 20+ hours effort to do the git repository manipulations to pull patches into the right branches, build the system on a couple Linux releases, and run the test suite on a couple different types of boards.  The next release should be an LTS one, probably based on 4.7.2, which requires a little more testing since it's a pain to put out patches.

 

I see. Sounds both very time consuming and not very fun.

 

I hope Red Hat will soon be able to make their first release of a toolchain. But I guess that it might be quite far out in the future.

Link to post
Share on other sites

My SBW+ programmer can flash MSP430G2955. Just to confirm that testing file "sbw_test_56.hex" attached in my last post is OK. So if you have problems with your programmer, trying to figure out how to flash MSP430G2955, use my test file. If you are able to flash MSP430G2955 with test file without verify error, and after flashing P1.0 LED is blinking, everything is OK.

 

http://forum.43oh.com/topic/2972-sbw-msp430f550x-based-programmer/?p=33806

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...