I am trying out CCSv5 for the first time, after unsuccessfully trying to install it to an existing Eclipse Juno installation, I finally succeeded installing it as standalone.
Now I'm trying out the first demo to see how everything works, following the video "Getting Started with the MSP430 LaunchPad Workshop - Part 2" from here: http://focus.ti.com/general/docs/video/Portal.tsp?lang=en&entryid=0_yrd0la9n .
I have created a new CCS project.
When prompted about the device, I see a dropdown entitled "Family" with only one option "MSP430", then another dropdown entitled "Variant" with only one option "Custom MSP430 Device". So I can't change anything there or type in any specific models. (I'm using the MPS-EXP430G2.)
I created the project and I edited main.c replacing the contents with the text from "\Labs\Lab2\Files\Temperature_Sense_Demo.txt".
The "debug" button doesn't do anything. So I tried the hammer icon instead, which says "Build debug".
At first I got an error about a non-existing include path. It couldn't find the first included file "msp430g2553.h". It was looking for it in "C:\ti\ccsv5\ccs_base\msp430\include", which actually did not exist. "C:\ti\ccsv5\ccs_base\msp430" existed, but no sub-directory "include".
So I researched my computer for any file named "msp430g2553.h", and I found it in a few places:"C:\ti\xdctools_3_23_03_53\packages\ti\mcu\msp430\include", "C:\ti\grace_1_10_04_36\packages\ti\mcu\msp430\include", "C:\Program Files (x86)\IAR Systems\Embedded Workbench 6.0 Evaluation\430\inc".
So I created a new directory "C:\ti\ccsv5\ccs_base\msp430\include" and copied the contents from "C:\ti\xdctools_3_23_03_53\packages\ti\mcu\msp430\include" to this new directory.
I push "Build debug" again (hammer icon), and it spits out 2 errors, 7 warnings, and 8 "others":
errors encountered during linking; "Temperature_Sense_Demo_1.out" not built Temperature_Sense_Demo_1 C/C++ Problemunresolved symbols remain Temperature_Sense_Demo_1 C/C++ Problem
-------------------------
#10210-D creating ".stack" section with default size of 0x80; use the -stack option to change the default size Temperature_Sense_Demo_1 C/C++ Problem#10247-D creating output section ".int02" without a SECTIONS specification Temperature_Sense_Demo_1 C/C++ Problem#10247-D creating output section ".int05" without a SECTIONS specification Temperature_Sense_Demo_1 C/C++ Problem#10247-D creating output section ".int08" without a SECTIONS specification Temperature_Sense_Demo_1 C/C++ Problem#10247-D creating output section ".int09" without a SECTIONS specification Temperature_Sense_Demo_1 C/C++ Problem#10247-D creating output section ".int10" without a SECTIONS specification Temperature_Sense_Demo_1 C/C++ Problem#10247-D creating output section ".stack" without a SECTIONS specification Temperature_Sense_Demo_1 C/C++ Problem
------------------------
#10372-D (ULP 4.1) Detected uninitialized Port 2 in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins. Temperature_Sense_Demo_1 C/C++ Problem#10372-D (ULP 4.1) Detected uninitialized Port 3 in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins. Temperature_Sense_Demo_1 C/C++ Problem#1527-D (ULP 2.1) Detected SW delay loop using __delay_cycles. Recommend using a timer module instead main.c /Temperature_Sense_Demo_1 line 198 C/C++ Problem#1527-D (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead main.c /Temperature_Sense_Demo_1 line 239 C/C++ Problem#1530-D (ULP 5.1) Detected divide operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive main.c /Temperature_Sense_Demo_1 line 137 C/C++ Problem#1533-D (ULP 6.1) Detected use of multiplication on a device that has no hardware multiplier main.c /Temperature_Sense_Demo_1 line 137 C/C++ Problem#1544-D (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier main.c /Temperature_Sense_Demo_1 line 124 C/C++ Problem#1544-D (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier main.c /Temperature_Sense_Demo_1 line 202 C/C++ Problem
What is going on? How come things don't work as of the workshop tutorial? I must say this really does make use of the MSP430 a bit daunting. The Arduino is much more straightforward. I didn't encounter a single error with the Arduino.
Hi John,
can you please detail a bit further information.
- are you in general having problems with MSP projects? Did you have any installation problems when you went to stand alone? Did you have your antivirus turned off?
- how are you importing the example? Can you please provide further detail.
What OS are you on?
The errors look like a broken library/file search path. Check this wiki as it should help.
http://processors.wiki.ti.com/index.php/Include_paths_and_options
Best Regards,Lisa
My OS is Windows 7 Pro x64.
I can't really say I'm having difficulty with other projects because I haven't done any projects. I'm following the tutorials for the first demo project, the "Temperature Sense Demo".
I'm "importing" the example exactly as described in the workshop video, I'm creating a new project, then opening the file "\Labs\Lab2\Files\Temperature_Sense_Demo.txt", and copying its contents and pasting the to main.c (deleting the default contents of main.c). I then close "\Labs\Lab2\Files\Temperature_Sense_Demo.txt", and try to compile with the "bug" icon.
I was also getting a "missing Target configuration file" error when pressing the bug icon button.
As regards the include path errors, are the contents of "C:\ti\xdctools_3_23_03_53\packages\ti\mcu\msp430\include" supposed to be the same as the ones being looked for in the non-existing path "C:\ti\ccsv5\ccs_base\msp430\include"? Would it be enough to just copy the contents over?
ok a couple things here, first I would try one of the example built into CCS. If you create a new CCS project for the MSP430, there is a hello world and/or blink LED example available from the create project wizard,
Each project needs a target configuration file in order for debugging. This tells CCS how to connect to your target in order to debug. Under file->new you will be able to create a target configuration file to add to the project.
If you do not have that msp430 path in your CCS installation this could be a /the problem. Did you select MSP430 support when installing? Did you have the antivirus turned off?
Please keep us informed.
Best Regards,
Lisa
Yes I chose MSP430 when installing, and yes my antivirus was turned off.
When I choose file->new->target configuration file, it opens a form with three tabs, Basic, Advanced and Source.
Under Basic, General Setup, there is a dropdown entitled connection, the only option in the dropdown in "Data Snapshot Viewer". Is this supposed to be correct?
Then there is a text field "board or device" and below that there is an empty select list. So I can't choose the MSP430 here... I also get an error message in the console:
Description Resource Path Location TypeThere are no debuggable cpus NewTargetConfiguration.ccxml /Blink Unknown Problem
My MSP430 is connected to the computer and recognized by Windows 7 Pro.
I am able to upload programs to it with Energia.
it is not normal not to access the list of devices like that. What OS are you on? Is this a fresh installation?
Could you please send the contents of your installjammer registry directory? Would you be willing to try a fresh installation?
Ok I again deleted everything and again reinstalled everything, and it seems to be working better now, I can now select the specific MSP430 in the target configuration.
However, if I turn my Avast antivirus back on again, it blocks the compiler when compiling a program, specifically it doesn't like:
C:\ti\ccsv5\tools\compiler\msp430_4.1.1\bin\opt430.exe
C:\ti\ccsv5\tools\compiler\msp430_4.1.1\bin\acpia430.exe
I would recommend contacting Avast to have your software whitelisted... It makes compiling a more complicated process.
yes, unfortunately this is a known item that antivirus programs are interfering with CCS installation/compilers. We are of course trying to do our best going forward.
Glad to hear you are now up and running and all the best with development.