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.

CCS/MSP-EXP430FR6989: Newbie question about Driverlib

Part Number: MSP-EXP430FR6989
Other Parts Discussed in Thread: MSPDRIVERLIB, MSP430WARE,

Tool/software: Code Composer Studio

Good evening, I was going through the MSP_Design_Workshop and in chapter 3 I need to use the Driverlib to start the lab. I downloaded this "MSPDRIVERLIB: DriverLib for MSP430 devices". When I tried to import the MSP430ware DriverLib library to my project I couldn't find the series for my Launchboard (EXP430FR6989). I only found the the following:

MSP

5xx_6xx

2xx_4xx

57xx

5xx_6xx

30i2xx

is any of the previous series compatible with mine? If not can someone suggest me a solution please? I would greatly appreciate it. 

  • Hello Giorgio,

    You listed 5xx_6xx twice but one of these should be FR5xx_6xx (the same applies for 57xx and 2xx_4xx, they should have a FR prefix) and this is the DriverLib version you need to use for your MSP-EXP430FR6989 LaunchPad.

    Regards,
    Ryan
  • Hey Ryan thanks for your response, I figured that driver had to be the one because I saw it in an example in the manual for my msp430. For some reason after importing it to my project and pressed build, the console would show me 3 errors. I'm pretty sure they are simple location errors because when I did Empty project with Driverlib source instead of Empty project with main.c my code worked fine. Maybe is due to my Driverlib is located in my desktop instead of disk C as my CCS7 ? I'm guessing I would encounter problems in the future if I'd like to use other libraries?
  • You need to make sure that the driverlib folder is located in one of the MSP430 Compiler Include Options search paths. You can do this by moving the driverlib folder to a proper directory or add the current directory to the include path. By creating an Empty project with DriverLib you can avoid this issue altogether since the Project Options will pre-include the library.

    Regards,
    Ryan

**Attention** This is a public forum