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.
Hello,
I'm using MSP430G2432 microcontroller with MSP430 LaunchPad development tool. My CCS version is 4.2.3.00004 with evaluation license. Recently I wrote a code for "Digital Clock" project, and there were no problems with it. Soon after that I tried to recreate the code using "IBM Rational Rhapsody". Auto-generated code by this program seemed ok, so i opened it with CCS, but it turned out that I can't build it because of rts430.lib<boot.obj> error. I've tried different approaches. I even tried to use only fragments of the generated code, pasted in one file, but I'm still receiving this error when I try to build it. Actually code looks the same as my hand written version...
I'll appreciate any help and give any additional information about the problem if requested.
Hi Ivo,
unfortunately we only support CCS, which you do not seem to be having problems with, and IAR (www.iar.com). The only thing I can suggest is to see if there are other people who may post to this or other forums who have experience using IBM Rational Rhapsody for MSP430 code.
Typically library files are not compatible across tools. Eg an IAR library file will mean the code is not going to work in CCS.
I hope this at least clarifies.
All the best,
Lisa
Actually after searching the forum, I found out that rts430.lib is CCS library having errors, when compiling assembly projects. This exact error was encountered a few times when assembly only project was mistakenly defined as a C/C++ project. That's not my case because my project is C only. I'll be glad if somebody could provide more information about CCS library structure and that exact library. Also if you have information about possible reasons for this error.
That's the console log:
**** Build of configuration Debug for project Try4 ****
D:\Texas Instruments\ccsv4\utils\gmake\gmake -k all
'Building target: Try4.out'
'Invoking: Linker'
"D:/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -vmsp -g --define=__MSP430G2432__ --diag_warning=225 --printf_support=minimal -z -m"Try4.map" --stack_size=80 --heap_size=80 --warn_sections -i"D:/Texas Instruments/ccsv4/msp430/include" -i"D:/Texas Instruments/ccsv4/tools/compiler/msp430/lib" -i"D:/Texas Instruments/ccsv4/tools/compiler/msp430/include" --reread_libs --rom_model -o "Try4.out" "./Proba.obj" -l"libc.a" "../lnk_msp430g2432.cmd"
<Linking>
undefined first referenced
symbol in file
--------- ----------------
main D:\Texas Instruments\ccsv4\tools\compiler\msp430\lib\rts430.lib<boot.obj>
error: unresolved symbols remain
error: errors encountered during linking; "Try4.out" not built
>> Compilation failure
gmake: *** [Try4.out] Error 1
gmake: Target `all' not remade because of errors.
Build complete for project Try4
I don't think this is a compatibility issue. A lot more possible is that this is my mistake, but I can't figure out what I am doing wrong. My next step is to try to create simplest possible projects, and if there is no problem with their files, I'll start complicating them until cause the error. I'll report if i found out something.
If it turned to be a compatibility issue, serious attention should be payed, because Automotive industries require using code generation tools, instead of manually writing the script. That's the reason I'm studying IBM Rational Rhapsody now.
Thanks in advance for any opinion related to this issue.
OK - I succeeded with building auto-generated Rhapsody code with simple CCS project. Now it's sure I have mistaken something in the complicated one. I'll report when I correct it.
OK - complicated project is finally build and debugged. No problems now. I had some with object includes. The error I reported was due to my own stupidity - I named function "main()" as "Main()". Thanks for the attention.
Hi Ivo,
ok I am glad you were able to work the issue out and that it was not some incompatibility with Rhapsody for you.
Cheers,
Lisa