A new version of the toolchain is ready for download. What's new:
You can download it from:
Just download, unzip and install.
THANK YOU SO MUCH!!!!!!!!!!!!! (I want to put more exclamation marks, but don't want to be rude)Seriously, now I don't need VMWare anymore. Thank you.
Just wanted to pop in and say thanks. A couple days ago I went through the whole build rigmarole as described on the official LaunchPad wiki, which ultimately worked but took a couple hours of frustration to get through (missed your comment there the first time around). Setting up a second Mac, used your installer instead, and everything was up and running perfectly in just a couple of minutes. Massive kudos!
Hmm, it's not working for me.I didn't have the prior version so I just installed the latest version.XCode is already installed. I downloaded the breathing led demo and tried compiling it. Here's what I see after unzipping ~/launchpad/demo-breathing-led → make installmsp430-gcc -Os -Wall -g -mmcu=msp430x2012 -c main.cmake: msp430-gcc: No such file or directorymake: *** [main.o] Error 1tab completing msp on the command line indicates that mspdebug IS installled:→ which mspdebug/usr/local/bin/mspdebugA few notes.1) I had tried installing the toolchain via the launchpad wiki and failed, perhaps that's where mspdebug came from.2) I don't suppose that your pkg assumes that some software is installed via macports, but if so on my machine I have done away with macports and use homebrew instead.
Thanks a lot! After a bit of frustration compiling with the instructions on TI's wiki I came across your comment.A few things: I can confirm that it also works on the 10.6.5 version of snow leopard. Also, the temperature demo that you link to in the older blog post does not compile with 'make' -- their makefile is in a different folder, and it is a hard-coded mess. You should rather recommend your breathing LED demo; it is much better!Thanks again! Great job!
Interesting. I can't get this working at all under Mac OS/X 10.6.6 - it simply won't talk to it MSPDebug version 0.12 - debugging tool for MSP430 MCUsCopyright (C) 2009, 2010 Daniel Beer This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.Trying to open interface 1 on 009rf2500: can't claim interface: Result too largerf2500: failed to open RF2500 devicemake: *** [install] Error 255The Result too large is because it is trying to display an error message code that it can't cope with. But it is failing at the same place mentioned here:http://sourceforge.net/mailarchive/forum.php?thread_name=053.b23c0a2b2e017df586b58ff72c44e7c2%40libusb.org&forum_name=libusb-devel(you have to get past the initial silly argument)
@arcade: interesting, it seems that Apple removed support to hijacking devices from user space using the codeless kext driver on 10.6.6... I will look and post an update if I find a solution.
Bill (who put together the codeless kext extension) appears to be the one at odds with libusb team. I have looked at the HID library they suggest and it doesn't look that hard to extend to work with the launchpad. Adding another drive into mspdebug specifically for the fet430uif seems like it would be an interesting challenge and it might work cross platform without the messyness.
I have managed to build an initial port for the Mac just using the HID library and bypassing the need for the kext hack. I have deployed the slow blinking led demo on your site and it works nicely!
Richard: Great!! Are you planning to contribute your patch to the mspdebug project? If you do, please let me know. I will repackage the upstream code and post a new .pkg here.
New MSP user here. I am wanting to develop using the new G2553 chip which I have been told will be supported in the Uniarch version in the next week or so. I'm building the current version now to get all the dependancies worked out.However, I am still very confused about what I need in the way of drivers for OS/X to program the launchpad. Is BillW's driver all I need, or is there something else? If I need something else, can I get it without installing your entire package? And if so, where?Many thanks in advance!
@Rockets: I suggest you install the pre-compiled package, that will give you msp430-gcc 4.4.3, mspdebug, BillW's driver and libusb. The installer creates a link in /usr/local/msp430-toolchain that points to /usr/local/msp430-gcc-4.4.3. You can compile and install another version of gcc, just re-point the symlink to the new toolchain and have both coexist without problems.If you want to install everything manually, it's also doable, but painful: Install homebrew, then 'brew install libusb-compat'. Download mspdebug, configure, make and make install. Download the gcc toolchain and buildgcc.sh. Lastly, download BillW's driver (link on my very first post) and install.
I had considered exactly what you suggest, but I'm the kind of person who like to know what is going on under the hood. And I must admit, sometimes I am a glutton for punishment.I'm a Macports guy (had troubles with brew when I tried it a while back, maybe it is better now) and libusb-compat is in there, so that shouldn't be so bad.As to the driver, this is the only one I need, correct?http://mspdebug.sourceforge.net/misc/ex430rf2500-kext.zipI did see some references to patches required for mspdebug at one point. Are these still required, or have they been merged into the current sources?Also, can we get some confirmation that this works under 10.6.7?
Understood... I also like to know what's going on, especially in OSX with such a mediocre package management.Macports should be okay... I tried both, but I can't remember what made me go for brew.That is the link to the driver. It's an Xcode project, but it also comes pre-compiled.The story with mspdebug is: it used to work, then it broke with 10.6.6 because of the kext not being compatible anymore. Richard (above) came up with a patch for mspdebug to use the HID library instead of libusb, making the kext no longer necessary. But, we never heard from him again. Eventually 10.6.7 came out and Chris reports that everything is back to normal (ie. both the kext and mspdebug work unpatched).
Ok. I think that explains why I have seen so much conflicting information on the web.I ran into some problems compiling uniarch last night, went to bed, and got a lead on how to fix them, so I'm back off to it now...
Many thanks for all the help. I now have a working uniarch toolchain under os/x, and have used it to compile and program your breathing light demo on a g2231 using the Launchpad.Doing the build really isn't so bad at all once you know what to do. The trick is just figuring it out.
Thanks for Launchpad's toolchain version 20101112, it works really fine with my OS 10.6.7 and LaunchPad.Now I need to work with a MSP430G2332, so an Update for MSPDebug is necessary. While I'm an artist, non-computer-man, i feel unable to do things like »homebrew« etc.I'm asking myself if there is a program that "updates" all the components of the toolchain automatically. Or a new release Launchpad's toolchain version 20110510?Thanks!
Thanks a million! This works great!
thanks for your work!do you plan to bring back the support for usb/acm0 devices? (i.e.serial port capability?)p.s. i wonder if it will ruin my avr setup ;-)) hope, crosspack will survive)
As far as I know, the Virtual COM Port (VCP) has never worked on OSX. TI has never released a proper driver.Crosspack will be okay. The Launchpad toolchain is in /usr/local/msp430-gcc-*, and the avr stuff is in /usr/local/CrossPack-AVR-*. They don't conflict each other. I have both :)
Oh, man, so awesome. I just dowloaded the installer and the demo code, started a new terminal (to read in the new path), ran make and then make install. Bingo! No more VM!
Has anyone got it to work on OSX 10.6.8?I get similar errors:spdebug rf2500 "prog main.elf"MSPDebug version 0.12 - debugging tool for MSP430 MCUsCopyright (C) 2009, 2010 Daniel Beer This is free software; see the source for copying conditions. There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.Trying to open interface 1 on 006rf2500: can't claim interface: Permission deniedrf2500: failed to open RF2500 devicemake: *** [install] Error 255
Try with sudo
@Javi: had already tried it with sudo, still doesn't work!
@tekstop, @javi: Did you ever figure out the 'Permission denied' problem. I'm having the same issue. Tried using sudo - doesn't work. Also using OSX 10.6.8.Is there any other information I can post that will help?
rf2500: can't claim interface: Permission deniedrf2500: failed to open RF2500 device@JoeyJoe This allowed me to connect and program the MSP http://mspdebug.sourceforge.net/faq.html#rf2500_osxviahttp://www.senslab.info/?p=425