MSP430FR2512: CapTIvate Touch library and MSP Peripheral Driver library

Hi Ralph,

For the most part, yes, you are correct. All of the CapTIvate HAL and some higher level functions, such as sensor processing, are in ROM. For the MSPDriverLib, there are a few functions to support UART and I2C, principally for communication with the CapTIvate Design Center, but can be re-used by the application for communication with a host MCU.

Regarding your question (1) - Those CapTIvate functions that are not in ROM are available as source and only those functions called in your program are pulled into the build by the compiler. This does not apply to the ROM functions since they reside in separate memory from FRAM.

Regarding question (2), no. The software development team follows standard practices and performs regression testing but outside of TI does not provide testcases, test procedures or verification results. For MSPDriverLib, the entire driverlib source is available as part of the download if one wanted to test or qualify the source. CapTIvate library is a different story, due to the proprietary nature of the IP and the supporting HAL functions. This is part of the reason these functions are in ROM and made available only through an API call.

Hello Dennis,

Thanks a lot for your immediate and very detailed response.

This means that not all, but most of the Captivate functions are available in ROM.
What about the pre-compiled library? As stated in library documentation, you can choose between pre-compiled library and ROM library by using a special function call technique (foo(), ROM_foo(), MAP_foo(),...).
Does the pre-compiled library contain all of the Capitvate functions, i.e. could I build an application without calling any of the ROM functions and just use the pre-compiled ones?