This is 2.40.00.37 of MSPWare. MSPWare will allow you to develop your applications faster by providing all MSP430 and MSP432 related examples, documentation and software libraries in one package.
There is now a MSPWare Beta (3.10.00.xx) released for customers who want to try the latest MSP432 content featuring CMSIS improvements. The 2.xx line of MSPWare will be merged into the beta version in March 2016. Go to https://www.ti.com/MSP432CMSIS to learn more.
In the previous MSP430ware driverlib releases, the function ADC12_B_memoryConfigure for the MSP430FR9xx devices did not enable the window comparator bit ADC12WINC and differential mode bit ADC12DIF even if the correct parameter is passed to the function. This has been fixed in this release.[Bug 3930]
There were minor comments/document update for driverlib APIs
In the previous MSP430ware driverlib releases, GPIO_interruptEdgeSelect() [MSP430F5xx_6xx family] function for Port2 sets P1IES not P2IES. This has been fixed in this release. [Bug 3357]
In the earlier versions of driverlib, the enableInterrupt API cleared the corresponding interrupt flag first and then enabled the interrupt. This behavior is changed from this release onwards. The flag is no longer cleared with the enableInterrupt APIs in the different peripherals. The user application is expected to invoke the clearInterrupt/clearInterruptFlag to clear the interrupt flags explicitely.
EUSCI API have been split into EUSCI_A and EUSCI_B. The current EUSCI based peripherals available are
EUSCI_B_I2C
EUSCI_A_SPI
EUSCI_B_SPI
EUSCI_A_UART
USCI API have been split into USCI_A and USCI_B. The current USCI-based peripherals available are
USCI_B_I2C
USCI_A_SPI
USCI_B_SPI
USCI_A_UART
The APIs in MSP430FR5xx_6xx, MSP430F5xx_6xx, MSP430FR57xx families have been updated to use C99 types
Assert stmts are disabled by default. To enable them comment out the #define NDEBUG statement in the inc/hw_types.h or inc/regaccess.h (depending on which file is available for your family)
Support for FR59xx has been added as well as separation of DriverLib by device family in order to make the library easier to use.
ASSERT statements in the driverlib source files do not work. This will be fixed in the future releases.
Comp_E examples in examplesxx_6xx_e will fail to build due to a bug in the existing device header file for versions of CCS less than CCS 5.3. To workaround this, please upgrade CCS or replace the msp430fr5969.h from the CCS5.3 release in your CCS install.
Comp_E examples in examplesxx_6xx_e will fail to build due to a bug in the existing device header file for versions of IAR5.5. To workaround this, please replace the msp430fr5969.h from deprecated430fr5xx_6xx_header_filesfrom the in your IAR5.5 install.
Update to MSP430ware and drverLib 1.20 with support for CCS 5.2.1
Installation and Usage instructions for CCS 5.2 and below when upgrading via update site
Comp_E examples will fail to build due to a bug in the existing device header file for versions of CCS less than CCS 5.3. To workaround this, please upgrade CCS or replace the msp430fr5969.h from the CCS5.3 release in your CCS install.
Update to MSP430ware and drverLib 1.20 with support for CCS 5.2.1
MSPWare 2.40.00.37 may be installed along any previous version of MSPWare. It will place a new directory in “C:\ti\msp\MSPWare_2.40.00.37” on Windows and a similar location on Linux and Mac OS X. The older version will stil be avilable on disk but CCS will discover and use the latest for TI Resource Explorer.
Some components are not supported on all platforms. Check out the Known Issues part of the release notes for more information about what is not supported in each operating system.
MSPWare is a collection of different packages from Texas Instruments. Some packages have not been updated to support Linux or Mac OS X Yosemite. A list of known packages that are not updated can be seen below. Please check the release notes of the individual packages for more information.
This product’s version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and b is an unrestricted set of digits used as an incrementing build counter.
To support multiple side-by-side installations of the product, the product version is encoded in the top level directory, ex. MSPWare_2_10_00_15.