This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3200.ccxml - cannot set as default

Other Parts Discussed in Thread: CC3200, UNIFLASH, CC3200-LAUNCHXL

PROBLEM

  1. Unable to set CC3200.ccxml as default configuration file.
  2. Unable to launch CCS debug session because CCS cannot find CC3200.ccxml.

ENVIRONMENT

  • Windows Vista
  • All software is installed in C:\ti
  • CCS ver 6.0.1.00040
  • Uniflash ver 3.2.0.00065
  • CC3200 SDK ver 1.0.0
  • CC31xx/CC32xx Service Pack 1.0.0.1.1
  • Board: CC3200-LAUNCHXL Rev 4.1
  • Virus detection sofware is off
  • Device manager shows "CC3200LP Dual Port (COM19)" under port devices

SYNOPSIS

I'm trying to run the wlan_station project as described by SWRU376A, "CC3200 SimpleLink Getting Started Guide." I've performed all the instructions as described by the guide.

When I arrived at Steps 13, 14, and 15,  I imported a copy of CC3200.ccxml and failed to set it as the default target configuration. When I right-mouse button clicked on the file, and selected Set as Default, the command failed. The file name was suposed to become bolded and appended with the string [Default], as so: CC3200.ccxml [Default].

When I logged into the Windows administrator's account, started CCS, and imported the file, I was able to set it as default. But it didn't stick.

Now, back in my regular Windows account, when I attempted to build the project, it failed, and CCS presented this message.

"Unable to launch CCS debug-session based on current selection. The specified file "C:\ti\ccsv6\ti\CCSTargetConfigurations\CC3200.ccxml" does not exist in the file system."

This is true. There is no ...\ti\CCSTargetConfigurations\ directory, nor is there such a directory installed anywhere in C:\ti\ccsv6. I have resinstalled CCS and assured that the CC32xx device support package is installed, but with no affect.

It seems to me that there was an installation problem, but it wasn't corrected by performing another installation. Seems like both problems are related.

  • SOLUTION

    In my synopsis I didn't mention that at Step 12, "building the wlan_station project," the build finished with a couple errors. Despite the errors, I continued with the next steps to  import the configuration file and attempt to make it the default config file, but failing at the attempt.

    Since I didn't know what to do next, I decided to fix the build errors. I didn't have any clue on where to start with those errors, I remembered that back at Step 10, the common.h header file had to be edited. The guide was not clear about how to make the edits, meaning, should the quotaton marks remain as part of the macro definitions or not. So I put the quotation marks back into the definitions, and that solved the problem.

    Remarkably, the fix didn't create a c:\ti\ccsv6\ti\CCSTargetConfigurations directory, so that was simply an anomoly. And one other thing, the build was clear of errors, but one warning appeared. This is what it said:

    #10366-D automatic library build: using library "c:\ti\ccsv6\tools\compiler\arm_5.1.6\lib\rtsv7M4_T_le_eabi.lib" for the first time, so it must be built.  This may take a few minutes.

    The following builds were void of errors and warnings.

    One more matter. Once I had a problem with CCS loading the firmware (when going to debug mode), but pressing the RESET button on the board cleared that problem.

  • Hi, I also met that problem when I start to use Tiva TM4C123G . After a lot of stupid fixes, I regconized that when I had created New Project I had forgotten to select [ Connection: Stellaris In-Circuit Debug Interface ] in New CCS Project window. Maybe you should try this :D
  • Thank u my friend.

    I got same problem and The problem was solved thanks to you.