Get error when building project

This should work out of the box. I was able to build with no problem. The errors are stating that you have those symbols defined multiple times. Is that the full error message?

You can also do a "Ctrl-H" and search for "lcd_font" and check the results to see all the references of that symbol.

ki

Yes it is the full error message, and I have just installed from the CD and done nothing with the code

regards

Ib

Could you post your entire link command line as seen in the build console, (ie) everything that comes after:

'Building target: ez430_chronos_433MHz.out'
'Invoking: Linker'

This will help us understand what object files and libraries are being passed to the linker and what might possibly be causing the duplicate symbol errors.

Also which version of CCS are you using?

Hello,

I have the same problem here. Just got my TI Chronos and wanted to see how the firmware works. I'm using CCS 4.2.4.00033

Any idea whats wrong?

'Invoking: Linker'
"C:/Program Files (x86)/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -vmspx -g -O4 --opt_for_speed=0 --define=__CCE__ --define=ISM_EU --diag_warning=225 --call_assumptions=0 --auto_inline=0 --gen_opt_info=2 --printf_support=minimal -z -m"ez430_chronos_868MHz.map" --stack_size=80 --heap_size=80 --use_hw_mpy=F5 --warn_sections -i"C:/Program Files (x86)/Texas Instruments/ccsv4/msp430/include" -i"C:/Program Files (x86)/Texas Instruments/ccsv4/tools/compiler/msp430/lib" -i"C:/Program Files (x86)/Texas Instruments/ccsv4/tools/compiler/msp430/include" -i"C:/Program Files (x86)/Texas Instruments/ccsv4/msp430/include" --reread_libs --rom_model -o "ez430_chronos_868MHz.out"  "./driver/display1.obj" "./logic/user.obj" "./logic/test.obj" "./logic/temperature.obj" "./logic/stopwatch.obj" "./logic/rfsimpliciti.obj" "./logic/rfbsl.obj" "./logic/menu.obj" "./logic/date.obj" "./logic/clock.obj" "./logic/bluerobin.obj" "./logic/battery.obj" "./logic/altitude.obj" "./logic/alarm.obj" "./logic/acceleration.obj" "./main.obj" -l"rts430x.lib" "../simpliciti/CC430_End_Device_868MHz.lib" "../lnk_cc430f6137.cmd" "../driver/ez430_chronos_drivers.lib" "../bluerobin/BlueRobin_RX_868MHz.lib"
<Linking>
error: symbol "lcd_font" has already been defined
error: symbol "segments_lcdmem" has already been defined
error: symbol "segments_bitmask" has already been defined

>> Compilation failure

>> Compilation failure
fatal error: Failed linktime optimization

>> Compilation failure
gmake: *** [ez430_chronos_868MHz.out] Error 1
gmake: Target `all' not remade because of errors.
Build complete for project ez430_chronos

EDIT:

Ok, I'm new to all this programming stuff, but I've discovered that these three symbols are defined in display.c and display1.c wheras display.c is excluded from the build but display1.c not. on the other hand there is a display.h but no display1.h

I think I remember from school that both *.h and *.c need to be named the same, is that correct?

If that's the case I don't understand why nobdy else has encountered this?

regards,

Leo

Leo,

That project should build out of the box and I just verified that it does. It sounds like the project you are building may be a modified version of the original. Is that possible? I say this because there is no display1.c in the original Chronos software package.

Also if what you have pasted above is the complete link command as seen in your build console, then it looks like it is missing some .obj files as compared to my build.

I would suggest re-downloading and reinstalling the Chronos software package and importing it into a new workspace and testing it again. Also when you import the project into CCS, do not check the box for "Copy project into workspace".

Hello AartiG,

I chose "Copy project into workspace" because I encountered massive problems with file permissions when not choosing this option like following:

C:\Program Files (x86)\Texas Instruments\ccsv4\utils\gmake\gmake -k all
Das System kann den angegebenen Pfad nicht finden.

"C:/Program Files (x86)/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -@"main_ccsCompiler.opt"
Das aktuelle Verzeichnis ist ung?ltig.
gmake: *** [main.obj] Error 1
Das System kann den angegebenen Pfad nicht finden.

"C:/Program Files (x86)/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -@"simpliciti/Components/nwk_applications/nwk_freq_ccsCompiler.opt"
Das aktuelle Verzeichnis ist ung?ltig.
gmake: *** [simpliciti/Components/nwk_applications/nwk_freq.obj] Error 1
Das System kann den angegebenen Pfad nicht finden.

[...]

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

btw: I'm using Win7 64bit - if that matters.

thanks for your help,

leo

The problem is solved. I've reinstalled the CCS4 and the Chronos software package in a folder with sufficient rights. Now the project is compiling. Too bad I can't compile the full version due to code size limit restriction.

I have the same problem just downloaded the software, I did not edit any code yet.
But if I look at the directory permissions then everything is possible R/W/M/X/D.
The software is located at the flooring point.
C:\Program Files\Texas Instruments\eZ430-Chronos\Software Projects\Chronos Watch\CCS\Sports Watch

System information Windows 7  UK - 32 Bit Sp1

What did you do to the setup to make it work ?

I reinstalled CCS4 and the slac341b package in a folder outside \Program Files - nothing else.

Hope that helps.

@AartiG:

In the eZ430-Chronos Development Tool User's Guide (Rev. C) it says "Select Copy projects into workspace to create a new copy of
the projects" under 3.6.4.1 Using Code Composer Studio™ v4.2

markus leonhardt said:

In the eZ430-Chronos Development Tool User's Guide (Rev. C) it says "Select Copy projects into workspace to create a new copy of
the projects" under 3.6.4.1 Using Code Composer Studio™ v4.2

You are right. This was an oversight on my part. This project should work whether you check the box to copy project to workspace or not. Some other example projects have not been set up to allow being copied to workspace. I assumed this was one of them, but I just verified that it does build properly even if copied to workspace. Thanks for catching that.