• Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 2932 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Linking driverlib to a MSP430 project

Otto Hunt
Expert 1475 points
Other Parts Discussed in Thread: MSP430WARE

Hi Lisa,

I have a similar issue in that I get the following error:

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "plant sensor.out" not built

It started happening when I inserted a function from driverlib:

UCS_clockSignalInit(UCS_MCLK, UCS_XT2CLK_SELECT, UCS_CLOCK_DIVIDER_8);

Adding 

#include <driverlib.h>

got my code to compile, but now the linker appears to be complaining. MSP430ware_1_90_00_30 seems to only provide driverlib.h, not driverlib.c. But, on my system, if I go to C:\ti\msp430\MSP430ware_1_90_00_30\driverlib\packages\ti\mcu\msp430\driverlib\product I find driverlib.xml and driverlib.xs. So I pointed the linker (via the little "add path" window that pops up) to that. No dice.

Please advise.

  • TI__Guru**** 173310 points

    With the newer driverlid packages you don't actually link to a library but rather add the necessary source files (or all source files) to your project. For example to resolve a reference to UCS_clockSignalInit, you would need the source file usc.c. However, rather than have to find the one or more source files you may need, it is suggested to simply add the entire driverlib folder to your project so all the sources are pulled in. This is what is done in the examples inside MSP430Ware as well. Please see the Driverlib Users Guide within the msp430\MSP430ware_1_90_00_30\driverlib\doc folder for more details for how to use them with new projects.