CC3200 Compiling issue

Hi,

   As mentioned at the CC3200 Getting Started Guide, when importing wlan_station,

   "do not check the 'Copy projects into workspace' option."

   Did you do that?

-kel

Thanks a millions, commenting the Cygwin in the path solved the problem

I had the same linker problem with the Yagarto toolchain in the PATH. Temporarily changing the path from ...;C:\Yagarto\... to ... C:\XYagarto temporarily fixed the linker issue.  

Be nice if the CCS build config paths came from a CCS xml config file rather than the global "DOS environment" (since compiler is shelled, it could receive its "environment" from CCS-specific environment, rather than the environment in which CCS was launched).  I'm just sayin'...

Hello,

I have exactly the same problem but i don't understand where you are commented Cygwin??

Thank you in advance

warning #10366-D: automatic library build: using library "C:\Program Files\Texas Instruments\ccsv6\tools\compiler\arm_5.1.5\lib\rtsv7M4_T_le_eabi.lib" for the first time, so it must be built. This may take a few minutes.
cygwin warning:
MS-DOS style path detected: C:\TI\CC3200SDK\cc3200-sdk\example\getting_started_with_wlan_station\ccs\Release
Preferred POSIX equivalent is: /cygdrive/c/TI/CC3200SDK/cc3200-sdk/example/getting_started_with_wlan_station/ccs/Release
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
cygwin warning:
MS-DOS style path detected: C:\TI\CC3200SDK\cc3200-sdk\example\getting_started_with_wlan_station\ccs\Release
Preferred POSIX equivalent is: /cygdrive/c/TI/CC3200SDK/cc3200-sdk/example/getting_started_with_wlan_station/ccs/Release
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
cygwin warning:
MS-DOS style path detected: C:\TI\CC3200SDK\cc3200-sdk\example\getting_started_with_wlan_station\ccs\Release
Preferred POSIX equivalent is: /cygdrive/c/TI/CC3200SDK/cc3200-sdk/example/getting_started_with_wlan_station/ccs/Release
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
--> error: '*.obj
' not found
gmake.exe[1]: *** [library] Error 1
>> ERROR: mklib: gmake error during rtsv7M4_T_le_eabi.lib build

I was commenting on the apparent source of the linker error, which isn't specific to Cygwin. I couldn't update http://processors.wiki.ti.com/index.php/Mklib#MKS_or_Cygwin_tools_in_your_path to note that the same problem exists when Yagarto is present in the CCS build machine PATH - but TI can.

It's a real conundrum - how does one do a Cygwin (or MKS, or Yagarto) build from CCS when you are being told to change your build environment PATH to **not** use one or more Cygwin tool(s)?  

CCS setup doesn't make changes in the build machine's PATH environment variable, so it would seem that CCS doesn't "require" anything CCS-specific from the PATH inherited from Windows. That being the case, and based on the symptoms, CCS may be appending path-to-tools etc., rather than prepending path-to-tools etc.,  to the path when launching those tools. Don't know for a fact, but that is something TI could also consider looking at... if stepping-on "path to Cygwin" etc. is the only solution.

An end  user could also write a command script/PowerShell script/console app to strip "offending" paths from the PATH used by CCS, leaving the Windows environment unchanged (and thereby maintaining the integrity of any non-CCS build environment) until a "fix" is found. I tried that "for grins" with Yagarto (after restoring it in the path), restarted everything, launched CCS "the new way" (command script that alters the PATH variable and launches CCS) and rebuild the project that I had tested with previously, and it now builds successfully with Yagarto in the inherited PATH. CCS builds. Yagarto builds. Life is good.

Good luck!

Thank you for your quick response.

I modify the Environnement Variable in  Advanced System Settings/Environment Variables and clear the PATH Environnement variable.

And then when I compile it's work !

A new problem is when i want to use debug i have this message : Error connecting to the target

May-be you have also this message? Jumper configuration is correct and driver also.

I have another question about 'Android Sources' : http://www.ti.com/tool/WIFISTARTER#supportandcommunity

What is the software to use to modify the Android application sources and send it on his phone?

Thank you in advance.

I hope you meant you cleared the Cygwin paths from the PATH environment variable - clearing the entire PATH environment variable would wreak havoc with other Windows applications already installed on your machine that depend upon values in the system PATH.

It sounds to me like you might not have your debug communications configured correctly, but I don't use a Cygwin build.  For TI-RTOS, you get that message for something as simple as not having the USB cable plugged into the CC3200, but if your debug device (Control Panel/Devices) is disabled in Windows, you get the same error. You can search the forum for existing posts for your 'Error Connecting to Target" issue, or start a new thread for that issue so that it gets some attention from the TI ops.

The Android Software Development Kit is the tool typically used to build and deploy Android apps - you should be able to use it to modify and install the wifi starter app for Android to your device.

Thank you for the tip!

I cleared the Cygwin path and I managed to compile the CC3200 OOB example successfully.

I hope the CCS team can investigate and fix this issue.

Hello guys, I'm trying to debug my CC3200 launchpad with "wlan_station" example, but I'm getting these errors: 

Cortex_M4_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x200125ba: Debug Port error occurred.
Cortex_M4_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_M4_0: Breakpoint Manager: Error enabling this function: Address exceeds the allowed range
Cortex_M4_0: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x20008720: Debug Port error occurred.
Cortex_M4_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_M4_0: Breakpoint Manager: Error enabling this function: Address exceeds the allowed range
Cortex_M4_0: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x20012ea0: Debug Port error occurred.
Cortex_M4_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_M4_0: Breakpoint Manager: Error enabling this function: Address exceeds the allowed range

I already reinstalled my CC3200 board drivers and nothing happened. Does anybody know what is happening?

Thank you guys.

Hi Saurez, I am also facing same problem, have you got solution? if yess please tell me. 

Cortex_M4_0: GEL Output:
Memory Map Initialization Complete
Cortex_M4_0: Error connecting to the target
Cortex_M4_0: GEL Output:
Target Reset
Cortex_M4_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x2000d76e: Debug Port error occurred.
Cortex_M4_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_M4_0: Breakpoint Manager: Error enabling this function: Address exceeds the allowed range
Cortex_M4_0: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x2000e3b8: Debug Port error occurred.
Cortex_M4_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_M4_0: Breakpoint Manager: Error enabling this function: Address exceeds the allowed range
Cortex_M4_0: Error: Debug Port error occurred.
Cortex_M4_0: Error: Debug Port error occurred.
Cortex_M4_0: Error: Debug Port error occurred.
Cortex_M4_0: Error: Debug Port error occurred.
Cortex_M4_0: Error: Debug Port error occurred.
Cortex_M4_0: Trouble Reading Memory Block at 0x2000e3be on Page 0 of Length 0xd: Debug Port error occurred.
Cortex_M4_0: Error: Debug Port error occurred.
Cortex_M4_0: Error: Debug Port error occurred.

I had the same problem and had to comment out all WinAVR and Yagarto entries in my system Path variable.

Same for me.

The CC3200 driver on Mac OS X was updated to comply with signed drivers required by Mac OS X .10 Yosemite.

Since then, I can't debug.

I posted this issue at ticket 500 CC3200 FDTI extension needs to be signed to work on OS X Yosemite on the GitHub repository for Energia.