Introducing MSP430Ware and the Brand New Driver Library!

Good - this answers a couple of questions:

http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/t/136385.aspx

http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/t/135410.aspx

If you go to
http://www.ti.com/tool/msp430ware?HQS=mcu_msp430_ware_111218&DCMP=mytinwsltr_12_17_2011&sp_rid_pod3=LTg5MDA1NDUzNgS2&sp_mid_pod3=4968551

it says:

--To get MSP430Ware and GUI-based front end, simply install the latest version of Code Composer Studio version 5.1. Get the latest version of CCS! (Recommended)
--Alternatively, MSP430Ware is available as a standalone package. However, this will only provide the folder structure of the MSP430Ware package,
and will not have a GUI-based front end. Click here to get MSP430Ware as a standalone package.

Now if you read this thread: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/135961.aspx
it says that ONE installation of CCS v5 will support all platforms.

So you can't get the new MSP430 GUI without installing CCS v5.1....again.
Does this mean you end up with TWO CCS installs...one for Stellarisware and one for MSP430Ware? These aren't exactly small windows applications...

Jon

Could I use it with MSP430G2553? 

Thanks!

Leonardo Mart��nez said:

Could I use it with MSP430G2553? 

"As of today, MSP430 Driver Library supports 5 and 6 series devices."

The MSP430G2553 is a 2 series device. Does this answer your question?

Has the 2xx and Value Line been incorporated into the Driver Library as of today?

The documentation is, unfortunately, not as up-to-date as the library itself.

I copied the following from RTC_C into my code only to find out that the macros aren't defined:

//Enable interrupt for RTC_C Ready Status, which asserts when the RTC_C
//Calendar registers are ready to read.
//Also, enable interrupts for the Calendar alarm and Calendar event.
RTC_C_enableInterrupt(RTC_C_BASE, RTC_CRDYIE + RTC_CTEVIE + RTC_CAIE);

The correct function should be something like this:

//Enable interrupt for RTC Ready Status, which asserts when the RTC
//Calendar registers are ready to read.
//Also, enable interrupts for the Calendar alarm and Calendar event.
RTC_C_enableInterrupt(RTC_C_BASE, RTC_C_TIME_EVENT_INTERRUPT + RTC_C_CLOCK_ALARM_INTERRUPT +                                                                     RTC_C_CLOCK_READ_READY_INTERRUPT);

Is there an update to the documentation?

Thanks,

Mechi