TI E2E Community
Code Composer Studio
Code Composer Forum
Is there a request for CCS on MAC OSx?
Starting a separate thread is a good idea. I just stumbled upon the original post while looking for something else and thought: "don't need fancy IDE, need a working toolchain". As I said the TU3410 is in all MSP430 programming devices by TI, so CCS couldn't be used on Mac for MSP430 even if it would exist.
No drivers are of course the best. However, do you know of a USB-2-UART chip that doesn't require drivers? Even the FTDI series, which works well on Mac, requires drivers. Maybe Windows cannot use CDC at all, even with drivers? :)
So, where is that separate thread, Matthias?
This is turning into a general Mac support topic, but I will briefly say that only the FTDI series requires drivers. Unfortunately, the FTDI Chip line is too popular, much more popular than it should be given how poorly it works. All other CDC devices that I have used will simply work on OSX without a driver. Many of these are based on the PIC chip, which can be programmed to be compliant with any USB Class.
I am not familiar with the TU3410, and it does not appear anywhere when I search on the Texas Instruments site by part number. If it is merely a transceiver, then you should be able to program your MSP430 to be USB CDC Class compliant. If not, then I have no idea what to suggest since I can find no data sheets for this part.
there's no separate thread (yet). The TUSB3410 is used as USB-2-UART chip to be able to communicate to the MSP430 chip over UART in those cases.
Before, I used Silabs USB-2UART chips with the BTnode (http://btnode.ethz.ch), it worked perfect on Linux, and rather well, but not perfect on Mac, it required a driver.
I've use the very cheap Profilic USB-2-RS232 cables which needed drivers and had to be patched.
As for the TUSB3410 (I hope I didn't mispell it before). It's shown here: http://www.ti.com/product/tusb3410
I would definitely not used it in my design :) but it's used in by all MSP430 dev tools, e.g the eZ430 dev kits, http://www.ti.com/tool/ez430-f2013
Then, it is used by the MSP-FET340UIF - http://www.ti.com/tool/msp-fet430uif
and also on the newest MSP430 board: http://www.ti.com/tool/msp-exp430f5529
I should clarify my comments, since I started out referring to "drivers" and later suggested that (actual) drivers should be discussed in another topic.
What I mean by those seemingly contradictory statements is that USB CDC drivers for any given operating system should not be part of this thread or part of CCS. Some emulators will be proprietary, and some will be class compliant. The Class compliant emulators should have a two-layer solution, where the low-level USB CDC Driver is provided by OSX, and a higher-level "emulation" layer should exist on top of the standard serial devices that are part of the BSD Unix segment of OSX. Proprietary emulators that are not class compliant would still need high-level "drivers" that would handle both layers. Fortunately, OSX allows user level code to talk directly to USB Devices, so the proprietary emulators could easily be handled by high-level "drivers" without writing actual kernel drivers.
For the purposes of this discussion, I put "drivers" in quotes when I am talking about a piece of plugin code that is specific to CCS and which talks to emulators. When I use driver without quotes, I'm talking about an official driver installed in OSX. I have a great deal of experience with OSX and have developed several USB devices, both class compliant and proprietary, and I see no reason that CCS should need any actual OSX drivers. Everything can be handled with higher level user code rather than system code.
There are plenty of better directions for you to choose. It seems that you have tried several USB-to-serial adaptors that have poor performance. The TUSB3410 seems like a wasteful choice for an MSP430 design, because the TUSB3410 incorporates a 24 MHz 8052 processor which loads and executes its own firmware. Such a design ends up with two processors on the same board (the 8052 and the 430) with severe limitations on the efficiency of the USB communications. The TUSB3410 is probably better suited to legacy serial designs that cannot be updated, whereas if you are creating a new MSP430-based product then it would make more sense to streamline your hardware and firmware design to reduce redundancy.
I would recommend that you select one of the many MSP430 chips that incorporate USB on board. There are a couple of dozen choices. MSP430 + USB - TI.com
With USB on the MSP430, you will have better control over the data and control flow.
thanks for all your well intended advice. However, you're missing the point, or rather, you have to tell TI about the limitations of using the TUSB3410. This chip is build into all TI MSP430 development boards you can purchase today, so I'm merely interested in using those boards as they are. (Also, I'm software guy and not developing any MSP430 based hardware). I shouldn't have highjacked this thread. Sorry.
Best , Matthias
I see discussion still continues regarding TI supporting CCS sw dev for the MPS430 on Mac OS X. The last time I posted here was about 2 years ago (1 Jul 2010 8:54 PM):
TI's MCU products look attractive and I can see interesting possibilities for them. However, I find it a disappointment that your dev tools are so wedded to the Windows OS. Yes, those of us who prefer OS X are aware of the various ways to get Windows running on a Mac. But being required to jump through such hoops just to proceed with MCU dev is, IMO, unacceptable.Until TI comes up with native OS X tools, I will stick with Arduino and its excellent multi-platform software support.
As others posting here have noted, many folks prefer Macs for dev work. No doubt many more use Macs now than 2 years ago. I wonder if TI's response to this trend will move beyond forum posts in the next 2 years.
It would be great if we can have CCS for MacOSX! I am a DSP programmer as well as MacOSX user. In order to develop/debug DSP code,
I have to run DSP debugger in VMware, which is really slow and resource-consuming. CCS can be executed on Linux and CCS is actually
a plug-in for Eclipse, I don't see any obstacle for TI to port CCS to MacOSX. Personally I prefer to have the same CCS environment on MacOSX, i.e.
Eclipse-based CCS. After all, TI should maintain product consistency among platforms. For people who prefer to customize their tools, e.g. Xcode/Emacs,
they can easily integrate them into Xcode/Emacs once TI provides native CCS toolchain binary.
I'm trying to figure out how to use CCS Windows binary and wine to run it on MacOSX. But I really want a native CCS on MacOSX! Thanks, TI!
Please put Mac OS X development on your road map soon! There are many of us that want it!
Please port it!
Just to give everyone an update - We have some tentative plans to support MAC OS in the future. And initially, support would be limited to a few devices. Since the plans are tentative, there are no specific dates or devices I can name as of right now (so please hold your questions regarding those). But I just wanted to let everyone know that it is on the table and something we are looking to do.
Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.
Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.
Having CCSv5 problems? Check out the CCSv5 Troubleshooting Guide
Click here to track an issue. Enter your bug id in the "Find Record ID" box
Now That's good news!
Thanks, TI, for these fabulous devices and experimental boards. Please add my vote to the folks who would appreciate ANY tools for building on Mac OS. CCS would be a dream, but even some minimal command line tools would be welcome. Many of us are competent to compile and debug purely on the command line.
Right now my solution is VMware.
+1 for native CSS (using latest Eclipse and CDT) on Mac OS X CCS :)
Right now my solution is VirtualBox -- works well but chews up more RAM, different meta keys between systems (ctrl v command), different versions of Eclipse (4.2 v 3.7 CCS).
I use Eclipse Juno (4.2) on OS X for code browsing, editing for C/C++, generally using Makefiles. If the compiler/debuggers could be ported to OS X that would be a good start, as then we could customise build commands. It shouldn't be that difficult as it is POSIX like and I know there are MSP430 mac ports for gcc and clang.
Of course a fully supported distribution would be great ;-)
On a side note, my biggest issue with CDT is storing the .cproject file under source control (Bazaar) and using branches, but I think this is a more general Eclipse issue.
Brendan Simon (eTRIX)
Another vote for a native CCS osx native app!
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.