Instructions

User Experience Software

www.ti.com

Sometimes CCS finds the project, but does not have a checkmark; this might mean that your workspace

already has a project by that name. You can resolve this by renaming or deleting the existing project. (If

you do not see the existing project in the CCS workspace, check the workspace's directory on the file

system.)

Finally, click Finish. Note that even if you check the "Copy projects into workspace" checkbox, most of the

resources are linked and remain in their original location.

If using CCS v5.4, you may see a "#303-D typedef" warning. This warning should not cause problems, but

see Section 5 for more information and instructions to resolve it.

3.2.2 IAR

IAR v5.50 or higher is required. To open the demo in IAR, click File, then click Open, then click

Workspace…, and browse to the *.eww workspace file inside the \IAR directory of the desired demo. All

workspace information is contained within this file.

The directory also has an *.ewp project file. To open this file into an existing workspace, click Project, and

then click Add-Existing-Project….

Although the software examples have all of the code required to run them, IAR users may want to

download and install MSP430Ware, which contains the full USB Developers Package, driverlib, and the TI

Resource Explorer. These are already included in a CCS installation (unless the user selected otherwise).

3.3 Example Project Software Organization

The simpleUsbBackchannel example and the emulStorageKeyboard example share a similar project

organization. Figure 26 shows the CCS version of emulStorageKeyboard.

Figure 26. F5529 LaunchPad Demo Software Organization

Table 6 describes the functions of these files and directories.

Table 6. Demo Project File and Directory Descriptions

Name Description

main.c The main() function

hal.c, hal.h Hardware abstraction layer for the MSP430F5529 LaunchPad

MSP430 foundational software library, for accessing core MSP430 functions and peripherals. The USB API and

driverlib

examples use it to manage clocks, power, and the DMA module. driverlib is part of MSP430Ware.

USB_API The MSP430 USB API, part of the MSP430 USB Developers Package.

Contains three files that configure the USB API for the application's needs. In particular, they define the USB

USB_config interfaces that are used for the respective demo application. These files were generated by the USB Descriptor

Tool, located in the MSP430 USB Developers Package.

MSP430F5529 LaunchPad™ Development Tool (MSP

‑

EXP430F5529LP) SLAU533A–September 2013–Revised January 2014

Submit Documentation Feedback