Code Composer Studio v6.1.1 for OS X Beta 2 Is Available

Martin Imrisek

Other Parts Discussed in Thread: CC2650, CC3200, MSP-FET, ENERGYTRACE, BLE-STACK, CC1350, CC2540, TM4C129XNCZAD, SYSBIOS, CC2640

CCS 6.1.1 Beta 2 for OS X is now available for download.

Please download from www.ti.com/.../swlicexportcontrol.tsp

New in this release:

Support for MSP430, MSP432, CC3200, CC2650, Tiva, C2000 and Hercules Launchpad devices
Support for MSP-FET, XDS100, XDS110, XDS2xx emulators
Includes EnergyTrace for MSP430 and MSP432
Supports OS X 10.10 and 10.9

This release is Beta quality and should not be used in a production environment.

Known issues include:

Web installer is not available for the Beta 2.
Conditional breakpoints and breakpoints with actions may not work as expected on some emulators.
An error dialog about unreachable sites is reported when checking for new software. This can be ignored.
Program load and debug performance may not be fully optimized.

Please submit your Beta feedback and issues through the forums.

over 9 years ago

Martin Imrisek over 9 years ago

TI__Intellectual 1710 points

I have updated the link in the original posting to point to an updated Beta 2 build.
New in this build are:
• Fixed update site registration for TI codegen tools.

Leo Oxvox over 9 years ago in reply to Martin Imrisek

Intellectual 460 points

I'm using the 1st Beta release and don't use codegen tools. I'm having enough problems at the moment and none of them have to do with CCS functionality. Do I need to install Beta 2?

Joseph Parness over 9 years ago

Intellectual 600 points

I getting the following error when trying to build with the Beta:

Description Resource Path Location Type
Product 'com.ti.rtsc.TIRTOSsimplelink' v2.13.0.06 is not currently installed and no compatible version is available. Please install this product or a compatible version. SensorTag SensorTag Problems

I could not find a BLE stack installer for the Mac so I installed the BLE stack on a VM got it building in CCS for Windows then copied the project to my Mac.

Joseph Parness over 9 years ago

Intellectual 600 points

Note that item 6 "<Install-Folder>/ccsv6/install_scripts" in README_FIRST.txt does not exist after the installation is complete.

DJ Lemkes over 9 years ago

Prodigy 30 points

As Joseph Parness, I was also wondering if there are any plans (or workarounds) to include the BLE-stack for the CC26xx soon?

AartiG over 9 years ago in reply to Joseph Parness

TI__Guru**** 173310 points

Joseph Parness said:
Note that item 6 "<Install-Folder>/ccsv6/install_scripts" in README_FIRST.txt does not exist after the installation is complete.

That is correct. Step 6 is no longer required, but the README wasn't updated to reflect that.

Albert Skog1 over 9 years ago

Prodigy 45 points

Great to see mac support coming, I am very happy!!

I have one issue though; I get the error "No USB FET was found" and figured out it was because of ez430rf2500.kext in /System/Library/Extensions/. I tried removing it, but the error still persists, even after rebooting and re-installing CCS.. Any tips?

Edit:

I tried some more things; if I press debug quickly after connecting the Launchpad I get a different error - "Error connecting to target: Frequency out of range."

Looking at dmesg it seems it enumerates fine at first, but then it is not responding:

➜  ~  sudo dmesg | tail -n 20
PM response took 353 ms (52, powerd)
en1: BSSID changed to 00:18:f8:3c:09:ca
en1: channel changed to 11
----------------------------------------------------
Texas Instrument LaunchPad / EZ430-RF2500 CDC/ACM Driver
           Version 1.0.3b - Terence Ang 2011
----------------------------------------------------
Device Name = Texas Instruments MSP-FET430UIF
Serial Number = 2FFF4A7AB74A381B
----------------------------------------------------
waitForBSDClientGated - bsdClientState is already 1 no need to wait...
MSP430LPCDC : Version number - 1.0.3b, Input buffers 8, Output buffers 16
AppleUSBCDC: Version number - 4.3.2b1
AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
[0xffffff80198cbc00](1)/(5) Device not responding
com_apple_driver_AppleUSBCardReaderUMC:: Stop::Controller Reset
USBF:    39660.843    AppleUSBOHCI::SuspendUSBBus Processing WDH before suspending
USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833, 2
AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.

I also found a forum thread suggesting looking at the output from system_profiler, but I am not sure what it should be...

➜  ~  system_profiler SPUSBDataType | grep -A 10 MSP
        Texas Instruments MSP-FET430UIF:

          Product ID: 0xf432
          Vendor ID: 0x0451  (Texas Instruments)
          Version: 1.05
          Serial Number: 2FFF4A7AB74A381B
          Speed: Up to 12 Mb/sec
          Manufacturer: Texas Instruments
          Location ID: 0x04100000 / 4
          Current Available (mA): 500
          Current Required (mA): 100

Torsten Robitzki over 9 years ago

Expert 2452 points

I'm just installing CCS and realize that the CCS installer is installing a second copy of eclipse on my computer. As on many developers computers eclipse might be already installed and eclipse is a very big package to install, maybe you can use an already existing version of eclipse?

Torsten Robitzki over 9 years ago

Expert 2452 points

I've created a new project, just with an empty main(). I don't know if it's up to me to copy the correct startup code into the project or if the IDE wizardry should have done this, but I get an unresolved symbol to ResetISR

Ki over 9 years ago in reply to Torsten Robitzki

TI__Guru**** 463481 points

Hello

Torsten Robitzki said:
I'm just installing CCS and realize that the CCS installer is installing a second copy of eclipse on my computer. As on many developers computers eclipse might be already installed and eclipse is a very big package to install, maybe you can use an already existing version of eclipse?

It is not possible to install the CCS components to an existing Eclipse installation. Sorry.

Ki over 9 years ago in reply to Torsten Robitzki

TI__Guru**** 463481 points

Hello

Torsten Robitzki said:
I've created a new project, just with an empty main(). I don't know if it's up to me to copy the correct startup code into the project or if the IDE wizardry should have done this, but I get an unresolved symbol to ResetISR

Usually that is the case for that template. Though this can vary per device. What device are you using?

Thanks

Torsten Robitzki over 9 years ago in reply to Ki

Expert 2452 points

Hi Kim,
I'm using a cc2650. I think, the problem was that I did not installed the TI RTOS libraries and eclipse plugins. I've setup a Windows VM to use CCS now and there I do not have the problem.

Cheers,
Torsten

Moritz over 9 years ago

Prodigy 70 points

I was happy to see that MSP432 type launchpads are now also supported in CCS on Mac OS. However, when I imported a project targeting the MSP432P401R from the CCS cloud (that builds successfully in the cloud) into CCS Version: 6.1.1.00027 I get the following error:

File devices/msp432p401r.xml does not exist. Was included by file <projectpath>/targetConfigs/MSP432P401R.ccxml

Suggestion was to update the project properties to match the device but no MSP432 devices are selectable in that menu. Did I miss something to activate MSP432-support in the CCS beta 2?

As a side notice: I already had the first beta installed and chose to install beta 2 in the same directory, assuming that this would actually update the installation. Turned out that this is not the case and I am stuck with 1.2Gb of wasted disk space. Two questions:
1. Is this possibly linked to my problem described above?
2. How do I get rid of the old beta 1 installation?

TiA

danishinnis over 9 years ago in reply to Moritz

TI__Mastermind 22060 points

You can just delete the old beta 1 folder.

Moritz over 9 years ago in reply to danishinnis

Prodigy 70 points

Ok, installing beta 1 and beta 2 in the same directory obviously really messes things up. This is how I finally got it working:

I deleted the complete CCS installation directory with the beta 1 and 2 inside (thanks for the tip danishinnis but since both installations were in the same folder, I didn't know which files/folders belong to beta 1 and which to beta 2). After that, I re-installed the CCS beta 2 in a new directory.

And voila: works like a charme. So it was all my fault. However you (TI) might consider to pop-up a warning during installation so that others do not run into the same situation.

desouza over 9 years ago in reply to Moritz

TI__Guru**** 171034 points

Hi,

>>installing beta 1 and beta 2 in the same directory obviously really messes things up.

This is a general statement valid for all CCS releases for all OSes. Installing CCS over a pre-existing older version is usually a bad idea.

Cheers,
Rafael

pixbroker over 9 years ago in reply to desouza

Genius 5820 points

Great news about CC2650 and XDS200 support for Mac! Thanks! Can you clarify if this supports only CC2650 specifically or CC26xx family? furthermore, does it support CC13xx family? We are particularly interested in CC2540 and CC1350 variant with XDS200. Thanks.

pixbroker over 9 years ago in reply to pixbroker

Genius 5820 points

I tried the RTOS object view and it doesn't seem to show any objects. Also the other RTOS tools like execution analyzer seem to be missing. Is this is know limitation or something broken in my installation? I know this is beta and we appreciate the great work you guys do to bring CCS to the mac! Thanks!

pixbroker over 9 years ago in reply to pixbroker

Genius 5820 points

I imported the SimpleBLEPeripheral from the BLE Stack 2.1 and adjusted all the paths and got it to compile, but i couldn't find the mac version of the Boundary tool, so the post build step fails. Is the Boundary tool something we can expect to work on the mac as well? If not, how would a BLE Stack project build on the mac? Thank you.

Torsten Robitzki over 9 years ago in reply to pixbroker

Expert 2452 points

As far a I understand the build process, the boundary tool is a post processing step, that greps the map files of both images and changes the linker scripts if the application image gets to large. I think the tool is developed with dot net and to run under OS/X something like mono is required.

I think an example should be build-able without that post processing step. But I wonder if TI ported there compiler to OS/X

desouza over 9 years ago in reply to pixbroker

TI__Guru**** 171034 points

pixbroker,

As Torsten mentioned, this is a windows-only application and it was created by the group that designed the BLE Stack software package. In this case, I would voice your concerns at their forum room so they would take action or show their roadmap for Mac OS support.

Regards,

Rafael

PedroGelabert over 9 years ago

TI__Expert 6995 points

Nice to have a CCS Mac version! After 15 years...

I compiled the NIRscan Nano Tiva sources. This uses TI-RTOS 2.10.1.38, so I just copied over this directory from Windows VM. It detected and install the older TI-RTOS. The project also uses Trivaware libraries driverlib and usblib, along with the DLP Spectrum Library. It builds mostly, but at the end I get two errors when I build for Debug.

gmake: *** No rule to make target 'configPkg/linker.cmd', needed by 'configPkg/compiler.opt'. Mobile Spectroscopy TIVA EVM Unknown C/C++ Problem
gmake: *** No rule to make target `/Users/pedro/Developer/DLP/MobileSpectro/Mobile'. Stop. Mobile Spectroscopy TIVA EVM Unknown C/C++ Problem
xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2: .xdchelp /Mobile Spectroscopy TIVA EVM line 209 C/C++ Problem

CCS for Windows does not have this issue.

Here is the detail console output. Seems to hang up on the space in the directory.

**** Build of configuration Debug for project Mobile Spectroscopy TIVA EVM ****

/Applications/ti/ccsv6/utils/bin/gmake -k all

Building file: ../appNano.cfg

Invoking: XDCtools

"/Applications/ti/xdctools_3_31_01_33_core/xs" --xdcpath="/Applications/ti/tirtos_tivac_2_10_01_38/packages;/Applications/ti/tirtos_tivac_2_10_01_38/products/bios_6_41_00_26/packages;/Applications/ti/tirtos_tivac_2_10_01_38/products/ndk_2_24_01_18/packages;/Applications/ti/tirtos_tivac_2_10_01_38/products/uia_2_00_02_39/packages;/Applications/ti/ccsv6/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4F -p ti.platforms.tiva:TM4C129XNCZAD -r debug -c "/Applications/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5" "../appNano.cfg"

making package.mak (because of config.bld) ...

configuring appNano.xem4f from package/cfg/appNano_pem4f.cfg ...

generating custom ti.sysbios library makefile ...

Starting build of library sources ...

gmake: /Users/pedro/Developer/DLP/MobileSpectro/Mobile: No such file or directory

gmake: *** No rule to make target `/Users/pedro/Developer/DLP/MobileSpectro/Mobile'. Stop.

Build of libraries failed.

error: xdc.cfg.SourceDir: "/Applications/ti/xdctools_3_31_01_33_core/packages/xdc/cfg/SourceDir.xs", line 209: xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2:

js: "/Applications/ti/xdctools_3_31_01_33_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed!

gmake: *** [package/cfg/appNano_pem4f.xdl] Error 1

gmake: *** Deleting file `package/cfg/appNano_pem4f.xdl'

gmake: *** [package/cfg/appNano_pem4f.xdl] Deleting file `package/cfg/appNano_pem4f.h'

gmake: *** [package/cfg/appNano_pem4f.xdl] Deleting file `package/cfg/appNano_pem4f.c'

js: "/Applications/ti/xdctools_3_31_01_33_core/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.

making ../src/sysbios/sysbios.aem4f ...

gmake[1]: Entering directory '/Users/pedro/Developer/DLP/MobileSpectro/Mobile Spectroscopy TIVA EVM/src/sysbios'

gmake[1]: Nothing to be done for 'all'.

gmake: *** No rule to make target 'configPkg/linker.cmd', needed by 'configPkg/compiler.opt'.

gmake[1]: Leaving directory '/Users/pedro/Developer/DLP/MobileSpectro/Mobile Spectroscopy TIVA EVM/src/sysbios'

gmake: *** No rule to make target 'configPkg/linker.cmd', needed by 'configPkg/compiler.opt'.

gmake: Target 'all' not remade because of errors.

**** Build Finished ****

PedroGelabert over 9 years ago

TI__Expert 6995 points

Is there future support for Spectrum Digital XDS560v2STM emulator?

By the way, it seems to work in El Capitán (10.11.1)

Best regards,
Pedro

JohnS over 9 years ago in reply to PedroGelabert

TI__Guru**** 162255 points

Pedro,

There are no plans to support XDS560v2 class probes at this time. The release is for MCU and Connectivity devices and XDS560 doesn't really offer much for those devices beyond what you get with XDS200. The XDS560v2 class products are targeted for processors customers.

Regards,
John

pixbroker over 9 years ago in reply to JohnS

Genius 5820 points

Pedro,

can you clarify which device your are targeting? We did some testing of the different XDS class products recently and IMO, XDS200 is the sweet spot or price performance. Therefore, it's great that it is now supported on OS X and i encourage you to take a look at it.

PedroGelabert over 9 years ago in reply to JohnS

TI__Expert 6995 points

John,

Thanks for the quick note. Since XDS200 did not work with Mac in Parallels, I only have an XDS560v2. Unfortunately, we do not have XDS200, just some really slow XDS100. By the way, XDS560v2 running under Parallels was faster than XDS200 running natively in windows when debugging a Tiva TM4C1299.

XDS200 has a sweet price/performance ratio. But as an old DSP guy, I was pampered with my trusty old XDS560v2.

JohnS over 9 years ago in reply to PedroGelabert

TI__Guru**** 162255 points

We have run a number of benchmarks (on Windows) for the various probes. For a device like TM4C129 the XDS200 is actually a bit faster on most benchmarks. Where the XDS560v2 really shines is if you are doing a binary load or save of large amounts of data. Then its much higher TCLK comes into play. For processors then the XDS560 does consistently better on the other benchmarks as well.

XDS560v2 also gives you System Trace if you are using an enabled processor. However for something like TM4 something like ITM/SWO is more important. That feature is supported by XDS110 and XDS200.

We have some known performance issues on MacOS now that will need to be addressed.

R K Anand over 9 years ago

Prodigy 85 points

Martin - is the TI RTOS for the CC2650/CC2640 part of this CCS Beta Release. Thanks.

AartiG over 9 years ago in reply to R K Anand

TI__Guru**** 173310 points

R K Anand said:
is the TI RTOS for the CC2650/CC2640 part of this CCS Beta Release.

You can install TI-RTOS for SimpleLink after installing CCS, using the CCS App Center.

Nikolaus Wittenstein over 9 years ago

Prodigy 150 points

Just installed, taking a look. Thanks for thinking of us OS X users!

One quick question from the install process: is it possible to switch from a custom .app installer to a standard OS X .pkg? OS X packages are nice because of the way they're integrated into the system and because it's possible to examine a package's contents before installing.

Thanks again!

Nikolaus Wittenstein over 9 years ago

Prodigy 150 points

I have another question—I have the arm-none-eabi gcc tools installed, and I've been using them for other ARM core processors. Is there a way to get CCS to use this compiler? I've tried going to my project options, but it won't let me select anything other than the TI compiler.

JohnS over 9 years ago in reply to Nikolaus Wittenstein

TI__Guru**** 162255 points

If you go the the preferences dialog and then browse to Code Composer Studio -> Build -> Compilers it will let you specify locations to look for compilers. If you specify it there then CCS will try to discover the compiler at that location. If it is able to discover it then it will show up in the list of compilers in the project options

Nikolaus Wittenstein over 9 years ago in reply to JohnS

Prodigy 150 points

Yeah, that's what I tried—in the main options I added the folder where arm-none-eabi-gcc is installed (/usr/local/bin), but it still doesn't show up in the list of available compilers. How does CCS tell if something is a compiler? When I add the folder in the project options it says "No compiler selected! Please select a directory that contains the compiler for the 'ARM' device-family."

Thanks!

PedroGelabert over 9 years ago

TI__Expert 6995 points

I am not able to get Mac CCS to communicate with XDS200. It enumerates on the Mac, but when I test the connection, it replies with the following. This is the same error I got when using XDS200 with Windows 7 under Parallels. My XDS200 is a Spectrum Digital and the green light turns on.

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

/Users/pedro/.ti/ti/2/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
Failed to open i/o connection (xds2xxu:0)

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the debug probe via USCIF ECOM has failed.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

pixbroker over 9 years ago in reply to PedroGelabert

Genius 5820 points

Pedro, what version of OS X do you have installed?

PedroGelabert over 9 years ago in reply to pixbroker

TI__Expert 6995 points

I am currently running 10.11.1.

I also had the same problem under CCS in Windows 7 in Parallels with 10.10.5. This was also problem with several Mac users under Yosemite and CCS running in Windows 7 under Parallels or Virtual Box. I do not know of a Mac user that was able to use XDS200 under VM. XDS100 and XDS560 worked fine.

pixbroker over 9 years ago in reply to PedroGelabert

Genius 5820 points

As reported earlier, XDS200 works fine for me with OS X 10.11.1 both in CCS on OS X as well as in Parallels. The best speed i have noticed is achieved by connecting the XDS200 directly to one of the Mac's USB ports rather than via a hub or monitor hub.

PedroGelabert over 9 years ago in reply to pixbroker

TI__Expert 6995 points

How exactly did you get XDS200 to work on a Mac? We have tried on numerous Macs under Yosemte and El Capitán with Parallels and VIrtual Box.

You are the first I have heard that got an XDS2000 to work on a Mac.

pixbroker over 9 years ago in reply to PedroGelabert

Genius 5820 points

I wish i could offer a magic recipe, but i just started working once i had updated to 10.11.1 and the latest parallels. If you look at my previous postings in this thread, you can see that prior to that, i had it working using an old USB 1.0 hub. After the recent updates i decided to try without that hub and it just worked.

Martin Imrisek over 9 years ago in reply to PedroGelabert

TI__Intellectual 1710 points

Pedro,

Do you by chance have a device with an XDS110 emulator plugged in simultaneously?

run ioreg -p IOUSB to see what devices you have enumerated.

Apparently with an XDS110 and XDS200 emulator connected you need to add the enumerated USB port number as the port address in the CCS configuration file.

Let me know if this provides some insight into your issue.

Martin

PedroGelabert over 9 years ago in reply to Martin Imrisek

TI__Expert 6995 points

Martin,

I only have XDS200 connected. As I stated in the past and several other Mac users have submitted posts on this (myself included), XDS200 has not worked under Parallels or Fusion on Windows 98 or Windows 7 with Windows CCS. We have not had problems with XDS100 nor XDS560v2USB.

On Windows, it shows up in COM10 (Emulator CDC Serial Port) and COM12 (User CDC Serial Port). In the past I have had issues with COM port higher than 10 been able to be used by Windows drivers.

I am not sure where to change enumerated USB port number on the port address in CCS. If I go to the advance tab, there is a Debug Port I/O port Number. Is that what you are referring? If so which I/O port from the Mac?

On the Mac, XDS200 enumerates as:

USB 3.0 Bus:

Host Controller Driver: AppleUSBXHCIPPT
PCI Device ID: 0x1e31
PCI Revision ID: 0x0004
PCI Vendor ID: 0x8086

XDS2xx USB Emulator - Composit:

Product ID: 0xbef0
Vendor ID: 0x0451 (Texas Instruments)
Version: 1.00
Serial Number: S200-000E99039000
Speed: Up to 480 Mb/sec
Manufacturer: Spectrum Digital
Location ID: 0x14200000 / 3
Current Available (mA): 1000
Current Required (mA): 500
Extra Operating Current (mA): 0

USB Bus Prober (Developer Tools), it shows:

High Speed device @ 3 (0x14200000): ............................................. Miscellaneous/Common Class device: "XDS2xx USB Emulator - Composit"
Port Information: 0x001a
Not Captive
Attached to Root Hub
External Device
Connected
Enabled
Number Of Endpoints (includes EP0):
Total Endpoints for Configuration 1 (current): 7
Device Descriptor
Descriptor Version Number: 0x0110
Device Class: 239 (Miscellaneous)
Device Subclass: 2 (Common Class)
Device Protocol: 1 (Interface Association)
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x0451/0xBEF0 (Texas Instruments)
Device Version Number: 0x0100
Number of Configurations: 1
Manufacturer String: 1 "Spectrum Digital"
Product String: 2 "XDS2xx USB Emulator - Composit"
Serial Number String: 3 "S200-000E99039000"
Configuration Descriptor (current config)
Length (and contents): 141
Number of Interfaces: 4
Configuration Value: 1
Attributes: 0x80 (bus-powered)
MaxPower: 500 mA
Interface Association Communications-Control
Interface #0 - Communications-Control
Interface #1 - Communications-Data/Unknown Comm Class Model
Interface Association Communications-Control
Interface #2 - Communications-Control
Interface #3 - Communications-Data/Unknown Comm Class Model

Leo Oxvox over 9 years ago in reply to desouza

Intellectual 460 points

I'm confused. I haven't used CCS on my Mac for about a month. When I launched it today, it told me there were updates available -- are these updates the "Beta 2" release for OS X? I doubt it because (1) they bombed and (2) no opportunity for me to specify a directory.

Now that I look at this thread, I see there is a separate download link, but there are no explicit directions on what to do with it. When installations are so simple that the procedure isn't even described, I have a knack for getting them wrong similarly to what happened to Moritz.

Currently, my "Beta 1" installation is in /Applications/Texas-Instruments which looks like below. Would you mind describing what a good choice would be when the installer asks me where I want to put "it"?

Thanks,

Leo

JohnS over 9 years ago in reply to PedroGelabert

TI__Guru**** 162255 points

Pedro,

Can you try updating the firmware on your XDS200 on Windows and then try using it on Mac again.

http://processors.wiki.ti.com/index.php/XDS200#Updating_the_XDS200_firmware

The version should be 1006.

Regards,

John

processors.wiki.ti.com/.../XDS200

JohnS over 9 years ago in reply to Leo Oxvox

TI__Guru**** 162255 points

Leo,

Updates in general do not let you specify where to install them, they just update the existing installation.

When doing a new install I always install in a versioned directory as I typically have multiple installations. So on my Mac that would be something like Applicatons/Texas Instruments/ccs611beta2

John

JohnS over 9 years ago in reply to JohnS

TI__Guru**** 162255 points

Guys I am going to lock this thread. It is getting hard for us to track the different issues discussed on this one. If you run into an issue please start a new thread and we will respond there.

Thanks,
John

Code Composer Studio™︎

Code Composer Studio forum

Code Composer Studio v6.1.1 for OS X Beta 2 Is Available