MSP430FR2311: driverlib issue

Hi Jan,

Thanks for your detailed post! I don't see anything wrong with your setup. I duplicated the error on my side after importing a DriverLib example project from MSP430Ware in CCS by excluding the "driverlib" folder and building the project. Then, I added the paths manually like you did but that didn't help. I even tried to "Apply Project Template" and then "Point to Installed DriverLib" which also adds paths but that didn't work either.

The quickest way for you to get started would be to import the EmptyProject DriverLib project.

Regards,

James

thanks for your response James.

It is my habit to generate my source files with a preferred text editor (Notepad ++) and to link the file to CCS for the build process. If were to use the driverlib empty project is it feasible to copy it elsewhere, edit as needed, and then link to CCS to build it?

It seems to me that not being able to use all of the resources available in driverlib by dowloading MSP430ware to an appropriate location such as the same parent folder containing CCS, and then include the driverlib header in the source code kind of defeats the purpose of having tried and true routines to use to develop solutions faster.

I was able to do just that using CCS maybe a year ago with a MSP430FR2433.  Something has broken since then.

Regards,

Jan

Jan Hofland98 said:

The build fails with unresolved references to routines in the driverlib.  The path to the driverlib has been included under the linker.

Looking at msp430ware_3_80_09_03 driverlib isn't supplied as a pre-compiled static library. Instead, when driverlib examples are imported into CCS, the entire list of driverlib source files are copied into the project, in a driverlib sub-directory. This is not ideal since:

• It means all projects have a copy of the driverlib source files.
• If you want to update the project to update to a different version of msp430ware you have to copy the source files into the project, rather than just changing project properties.

One way to avoid having to copy the driverlib source files into the CCS project is:

1. Create an empty CCS project for your device.

2. Under Resource -> Linked Resources add two Path Variables:

Where:

• MSP430WARE_ROOT is the root directory of the msp430ware version you want to use for driverlib. In the above example msp430ware was installed in the TI_PRODUCTS_DIR, which is C:\ti under Windows and $HOME/ti under Linux.
• MSP430WARE_DRIVERLIB is the directory containing the driverlib source files for your device family.

3. In the CCS Project Explorer select to create a new driverlib folder, and select Advanced "Link to alternative location (Linked Folder)" specifying the linked folder as ${MSP430WARE_DRIVERLIB} :

This adds a link to the driverlib source files, without actually copying them into the project.

4. Under CCS Build -> MSP430 Compiler -> Include Options add ${MSP430WARE_DRIVERLIB} as an include project:

I have attached a CCS10 example of the above, for a MSP430FR4133.

MSP430FR4133_lcd_driverlib_linked_folder.zip