With Driver Library, Texas Instruments and the MSP430 team wanted to provide developers with an easy way to talk to the MSP430’s hardware. Typically, customers program microcontrollers using traditional C code. While traditional C code is abstracted and easier to use than low level assembly, C code can still require a steep learning curve, especially when devices are integrated with many peripheral modules. Each peripheral module inside of the microcontroller is defined and controlled through 1s and 0s inside of many registers. Traditional C code helps to populate those registers, but still requires a learning curve – especially for new microcontroller developers. So the MSP430 team has developed a new way of talking to the MSP430 devices, called the MSP430 Driver Library. This driver library is even more abstracted than traditional C code, allowing developers to communicate with their MSP430 microcontrollers using easy to understand and fully documented function calls. This Abstracted programming interface, or API allows customers to quickly grow beyond “Hello World” and get to real application development on MSP430 much more quickly. Also, the MSP430 Driver Library API was built to be fully open source – this enables developers to understand what is happening beneath the abstraction layer. More importantly, being open source enables developers to add, change, and even improve the library. In this example, a PWM signal is being generated. As shown here, traditional C code requires developers to populate specific registers on multiple peripheral modules. With Driver Library however, the user can do the same exact thing with just two lines of code. The Driver Library supports all peripherals integrated into the MSP430F5xx and 6xx devices, which are the most integrated devices in the Texas Instruments portfolio. The high level function calls within the Driver Library API makes it easy for customers to leverage multiple peripherals to enable various applications.