IAR Embedded Workbench

IAR Embedded Workbench

User's Guide

SLAU574G – March 2015 – Revised May 2017

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

This manual describes the use of IAR Embedded Workbench

® for ARM

®

(EWARM) version 7.80.3+ with the SimpleLink™ MSP432™ low-power microcontrollers.

Most descriptions in this guide are valid for EWARM versions below 7.80.3, but the SimpleLink MSP432 software development kit (SDK) requires EWARM 7.80.3 and higher. This guide also describes CMSIS device pack support available in EWARM 8.10 and higher.

6

7

8

9

10

11

12

3

4

5

1

2

Contents

Installing Embedded Workbench for ARM

................................................................................

4

Creating a Project Using the SimpleLink MSP432 Example Projects

Creating a SimpleLink MSP432 Project From Scratch

................................................

4

.................................................................

6

Importing Examples From the SimpleLink MSP432 SDK

.............................................................

14

Creating a SimpleLink Project From MSP432 CMSIS Device Family Pack (DFP)

Debugging the Application

................................

16

................................................................................................

19

Using Serial Wire Output (SWO) Hardware Trace Analyzer

.........................................................

35

Erasing the Bootloader (BSL)

EnergyTrace™ Technology

............................................................................................

38

...............................................................................................

40

Frequently Asked Questions

..............................................................................................

46

Additional IAR EWARM Information

References

.....................................................................................

47

..................................................................................................................

47

18

19

20

21

13

14

15

16

17

8

9

10

11

12

3

4

5

1

2

6

7

List of Figures

IAR Information Center for ARM

...........................................................................................

4

MSP432P4xx Standalone Examples

......................................................................................

4

MSP432 Blink LED Example Workspace

.................................................................................

5

Create New Project

..........................................................................................................

6

Select Project Template

....................................................................................................

7

Enter Project Name

..........................................................................................................

7

MSP432_BlinkLED Project

.................................................................................................

8

Select Project Options

......................................................................................................

8

Select an MSP432 Microcontroller

........................................................................................

9

Recommended Preprocessor Options

..................................................................................

10

Adding Code to Your Project

Save Workspace

.............................................................................................

11

...........................................................................................................

11

Successful Compilation

....................................................................................................

12

Add Interrupt Definition File

...............................................................................................

12

Adding the Interrupt Definition File

.......................................................................................

13

Interrupt Definition File

....................................................................................................

13

SDK Quick Start Guide

....................................................................................................

14

Examples HTML Page

.....................................................................................................

15

New CMSIS Project

........................................................................................................

16

Select Device From DFP

..................................................................................................

17

CMSIS Component Manager

.............................................................................................

18

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

1

www.ti.com

56

57

58

59

60

51

52

53

54

55

46

47

48

49

50

41

42

43

44

45

36

37

38

39

40

31

32

33

34

35

26

27

28

29

30

22

23

24

25

Newly Created DFP Example

............................................................................................

19

Select Project Options

.....................................................................................................

20

Selecting the TI XDS Debug Probe

......................................................................................

21

Debug Download Options

.................................................................................................

22

Dialog Box Asking to Perform a Factory Reset

........................................................................

23

Selecting MSP-FET as Debug Probe

....................................................................................

23

Securing Device With MSP-FET

.........................................................................................

24

MSP-FET Release JTAG on Go

.........................................................................................

25

Select the Segger J-Link Debug Probe

.................................................................................

26

Enabling Usage of Flash Loaders

........................................................................................

27

Using J-Link Commander to Enable Power Output to Target System

..............................................

27

Launch J-Link Control Panel

..............................................................................................

28

J-Link Control Panel

.......................................................................................................

29

J-Link Script Detecting That the Device Has Been Secured

.........................................................

29

Device Has Been Unlocked and Erased

................................................................................

29

Selecting the IAR I-jet Debug Probe

.....................................................................................

30

Enabling Use of Flash Loaders

...........................................................................................

31

Debug Probe Setup

........................................................................................................

32

Dialog Box Asking to Perform a Factory Reset

........................................................................

32

Adding Driver Library to a Project

........................................................................................

33

Adding ROM Symbol to Debugger

.......................................................................................

34

Stepping Through ROM DriverLib Source Code

.......................................................................

35

Trace Settings Configured From Running Debug Session Using Debugger Menu

...............................

36

SWO Trace Window Settings

.............................................................................................

36

SWO Configuration

........................................................................................................

36

Edit Flash Loader Settings

................................................................................................

38

Edit Info Memory Settings

.................................................................................................

38

Add --bsl_erase Option

....................................................................................................

39

Pulse Density and Current Flow

..........................................................................................

40

Debug Session With EnergyTrace+ Windows

..........................................................................

41

TI MSP-FET Emulator Pulldown Menu With EnergyTrace+ Related Functions

...................................

42

Enabling the State Log Window

..........................................................................................

42

State Log Window With EnergyTrace+ Data

...........................................................................

43

State Log Summary With EnergyTrace+ Data

.........................................................................

43

Power Log Setup Window

................................................................................................

44

Power Log Window With EnergyTrace+ Data

..........................................................................

44

Timeline With Power Log and State Graphs Disabled

................................................................

45

Timeline With EnergyTrace+ Data

.......................................................................................

45

Choosing SWD in Debugger Settings

...................................................................................

46

Trademarks

SimpleLink, MSP432, E2E, EnergyTrace are trademarks of Texas Instruments.

CoreSight is a trademark of ARM Ltd.

ARM is a registered trademark of ARM Ltd.

IAR Embedded Workbench is a registered trademark of IAR Systems.

All other trademarks are the property of their respective owners.

2

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Preface: Read This First

How to Use This User's Guide

This manual describes only EWARM features specific to the MSP432 low-power microcontrollers. It does not fully describe the MSP432 microcontrollers or the complete development software and hardware systems. For details on these items, see the appropriate TI documents listed in

Important MSP432

Documents on the Web .

Important MSP432 Documents on the Web

The primary sources of information about MSP432 MCUs are the device-specific data sheets and user's guides. The SimpleLink MSP432 website contains the most recent version of these documents.

Documents that describe the IAR Embedded Workbench for ARM can be found at www.iar.com

. The TI

E2E™ Community support forums can provide additional help.

Information about the TI XDS100 and XDS200 debug probes is not included in this document and can be found at www.ti.com/tool/xds100 and www.ti.com/tool/xds200 .

Documentation for third-party tools, such as the SEGGER J-Link debug probe, can usually be found on the respective third-party website.

If You Need Assistance

Support for the MSP432 devices and the hardware development tools is provided by the TI Product

Information Center (PIC). Contact information for the PIC can be found on the TI website at www.ti.com/support . The TI E2E Community support forums for the MSP432 MCUs provide open interaction with peer engineers, TI engineers, and other experts. Additional device-specific information can be found on the MSP432 website .

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

3

Installing Embedded Workbench for ARM

1 Installing Embedded Workbench for ARM

www.ti.com

IAR Embedded Workbench for ARM (EWARM) IDE is available from the IAR website . MSP432 low-power microcontrollers require EWARM 7.40.2 or higher. The SimpleLink MSP432 SDK requires EWARM 7.80.3

or higher. The TI MSP432 CMSIS device family packs require EWARM 8.10 or higher.

2 Creating a Project Using the SimpleLink MSP432 Example Projects

First download and extract the Texas Instruments examples in the IAR Information Center for ARM (see

Figure 1

).

Figure 1. IAR Information Center for ARM

For MSP432 devices, a good starting point is the basic Blink LED example in the stand-alone examples

(see

Figure 2 ).

Figure 2. MSP432P4xx Standalone Examples

4

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Creating a Project Using the SimpleLink MSP432 Example Projects

After you select the example, you are prompted to select a destination folder. The project and a workspace are created. You can change the device variant of your example, and all system and start-up files will be replaced (see

Figure 3 ).

Before you program the compiled examples, be sure to select the correct debugger in the project options

(for example, the TI XDS110).

Figure 3. MSP432 Blink LED Example Workspace

To create a project from scratch, follow the instructions in

Section 3

.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

5

Creating a SimpleLink MSP432 Project From Scratch

3 Creating a SimpleLink MSP432 Project From Scratch

Click the Project menu, and then click Create New Project. www.ti.com

Figure 4. Create New Project

6

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Creating a SimpleLink MSP432 Project From Scratch

Now EWARM prompt you to select a project template. For embedded code, a C-style main is usually a good starting point.

Figure 5. Select Project Template

Next you will be asked for the name of the project, and the location where EWARM stores the project files.

Figure 6. Enter Project Name

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

7

Creating a SimpleLink MSP432 Project From Scratch

www.ti.com

EWARM creates the required project files. An empty main.c is also copied into the project directory (see

Figure 7

).

Figure 7. MSP432_BlinkLED Project

3.1

Setting MSP432 Project Options

Next, apply a number of project settings to specify the target device and the debug probe to use.

Right click on the project name, and select Options (see

Figure 8 ).

8

Figure 8. Select Project Options

Now select the correct MSP432 microcontroller from the list of available microcontrollers (see

Figure 9

). If you cannot find the MSP432 family in the list, check the installation.

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Creating a SimpleLink MSP432 Project From Scratch

Figure 9. Select an MSP432 Microcontroller

Next set up include directories and preprocessor definitions, so that the correct set of header files can be accessed. Go to C/C++ Compiler Options and chose the Preprocessor tab (see

Figure 10 ).

Now add $TOOLKIT_DIR$\inc\TexasInstruments and $TOOLKIT_DIR$\CMSIS\Include to the list of directories that should be searched for include files during compilation, and add __MSP432P401R__ (or the define that matches your device) and ewarm to the preprocessor definitions.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

9

Creating a SimpleLink MSP432 Project From Scratch

www.ti.com

Figure 10. Recommended Preprocessor Options

Next we go back to the main program and add a generic header file include statement #include "msp.h".

The preprocessor define __MSP432P401R__ is evaluated in the msp.h header file and selects the correct header file for the specified device.

The statement WDT_A->CTL = WDT_A_CTL_PW | WDT_A_CTL_HOLD; makes the watchdog timer halt

(see

Figure 11

). If this statement is left out, the watchdog timer will reset after a while.

10

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Creating a SimpleLink MSP432 Project From Scratch

Figure 11. Adding Code to Your Project

Compile the program by pressing the F7 key or by right clicking on the project and selecting Rebuild All.

If you have not saved the Workspace yet, EWARM prompts for a save. Chose a unique name, and save the Workspace (see

Figure 12

). Compile automatically starts after the Workspace has been saved.

Figure 12. Save Workspace

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

11

Creating a SimpleLink MSP432 Project From Scratch

When compilation is complete, the Build window reports details of the process (see

Figure 13

).

www.ti.com

Figure 13. Successful Compilation

3.2

Adding Interrupt Vector Table

Add the source code file that defines the MSP432-specific interrupt table, as EWARM only defines the

Cortex-M system interrupts.

The interrupt source code file msp432_start-up_ewarm.c is located in

\arm\examples\TexasInstruments\MSP432. Copy it to the project directory, and include it in the project, by right clicking on the project, and selecting Add Files (see

Figure 14

through

Figure 16

).

Figure 14. Add Interrupt Definition File

12

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Creating a SimpleLink MSP432 Project From Scratch

Figure 15. Adding the Interrupt Definition File

Figure 16. Interrupt Definition File

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

13

Importing Examples From the SimpleLink MSP432 SDK

4 Importing Examples From the SimpleLink MSP432 SDK

www.ti.com

The SimpleLink MSP432 software development kit (SDK) contains software examples, projects, documentation, application notes, and training for all MSP432 devices. This includes example projects for

IAR EWARM that work with MSP432 MCUs. For more information, visit SimpleLink MSP432 SDK .

The SDK examples require IAR EWARM version 7.80.3 or higher. All documentation for the SDK can be found inside the SDK installation path in the docs folder. Open Documention_Overview.html from that folder and then navigate to the Quick Start Guide for your IDE (see

Figure 17 ). Follow the instructions in

this guide for required configuration before importing SDK examples.

Figure 17. SDK Quick Start Guide

In particular, make sure to execute the following steps:

• Configuring custom argument variables

• RTOS configuration, if you intend to use an RTOS

A list of examples for IAR can be found under <SDK installation path>/ tools/iar/Examples.html. In the

EWARM IDE, select FileOpenFile and open the Examples.html file (select HTML as file type) (see

Figure 18 ).

14

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Importing Examples From the SimpleLink MSP432 SDK

Figure 18. Examples HTML Page

Follow the instructions in the quick start guide on how to import these examples to the EWARM IDE.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

15

Creating a SimpleLink Project From MSP432 CMSIS Device Family Pack (DFP)

5 Creating a SimpleLink Project From MSP432 CMSIS Device Family Pack (DFP)

www.ti.com

IAR EWARM 8.10 and higher supports CMSIS packs (see the CMSIS Pack Documentation for a description of CMSIS packs). The Texas Instruments MSP432P4xx Device Family Pack version 3.0.0 and higher is supported by this version of the IAR EWARM IDE. This pack can be downloaded with the pack manager in the IDE or directly from the MSP432P4xx CMSIS device family pack page .

A device family pack adds device support to the IDE and features some basic examples. To create an example from the device family pack:

1. In the IDE, select ProjectNew Project and then CMSISPack example or Empty CMSISPack

project (see

Figure 19

).

Figure 19. New CMSIS Project

16

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Creating a SimpleLink Project From MSP432 CMSIS Device Family Pack (DFP)

2.

Select the correct device from the pack (see

Figure 20

).

Figure 20. Select Device From DFP

3. If you selected the empty CMSIS project, make sure to add the startup files in the Project CMSIS

Component Manager (see

Figure 21 ). In the CMSIS pack examples, the startup files are already

included.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

17

Creating a SimpleLink Project From MSP432 CMSIS Device Family Pack (DFP)

www.ti.com

Figure 21. CMSIS Component Manager

The CMSIS Project CMSIS Pack Configuration can be reached any time by selecting the button.

4. Save the new project to its destination folder.

For example, if you have chosen the BlinkLED example from the pack, it should look like

Figure 22 .

18

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

Figure 22. Newly Created DFP Example

6 Debugging the Application

The following debug probes can be used with MSP432 MCUs and EWARM.

• Texas Instruments XDS100v2, XDS100v3, XDS200, XDS110 (including the XDS110 stand-alone probe )

• TI MSP-FET

• IAR I-jet

• Segger J-Link

To use a debug probe that is not listed here, check with the vendor of the debug probe or with IAR if you experience problems.

Be aware that for some debug probes power has to be supplied externally to the device. Check the probes user guides for details. For the TI XDS110 stand-alone probe this guide can be found here .

6.1

Using TI XDS100, XDS110, and XDS200 Debug Probes

TI offers a range of debug probes for ARM-based devices, including the XDS100v2, XDS100v3, XDS110, and XDS200 debug probes.

To use them with EWARM, installation of the XDS emulation package is required. A copy of the emulation package is located in the EWARM installation under \arm\drivers\ti-xds. See the Readme.txt document that is also located in this folder. TI recommends installing the emulation package in

c:\ti\xds\ewarm_version. Do not use XDS emulation packages from other EWARM versions, as they might not be compatible and can result in errors when debugging.

When the emulation package has been installed, XDS debug probes can be selected in the Project

Options menu. Right click on the active project, then select Options (see

Figure 23 ).

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

19

Debugging the Application

www.ti.com

Figure 23. Select Project Options

20

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

Click Debugger in the left pane and select TI XDS. Then click XDS debuggers in the left pane and select the correct XDS debug probe from the list. (see

Figure 24

).

Figure 24. Selecting the TI XDS Debug Probe

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

21

Debugging the Application

Make sure that the Use flash loader(s) option is selected in the Download tab (see

Figure 25

).

www.ti.com

Figure 25. Debug Download Options

22

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

6.1.1

Working With Device Security

If you have disabled JTAG access on the device or are working on an application where you need to unlock a secure IP zone, IAR Embedded Workbench automatically runs a check on the device before downloading code. If IAR finds that the device has been secured, a dialog box opens as shown in

Figure 26 .

Figure 26. Dialog Box Asking to Perform a Factory Reset

Click Yes to perform a factory reset and unlock the device so that code can be downloaded. Click No to end the debug session and leave the device locked. After the code has been downloaded, the debug session starts.

6.2

Using TI MSP-FET

To use the MSP-FET for debugging MSP432x devices, IAR 7.60 or higher is required. No additional driver installation is required.

TI MSP-FET debug probes can be selected in the Project Options menu. Right-click on the active project, then select Options (see

Figure 23

).

Click Debugger in the left pane, and select TI MSP-FET (see

Figure 27 ).

Figure 27. Selecting MSP-FET as Debug Probe

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

23

Debugging the Application

www.ti.com

6.2.1

Working With Device Security

Similar to the process when using TI XDS debug probes, you can unlock a protected device. If you have disabled JTAG access on the device or are working on an application where you need to unlock a secure

IP zone, IAR Embedded Workbench automatically runs a check on the device before downloading code. If

IAR finds that the device has been secured, a dialog box opens as shown in

Figure 26

.

Click Yes to perform a factory reset and unlock the device so that code can be downloaded. Click No to end the debug session and leave the device locked. After the code has been downloaded, the debug session starts.

The easy-to-use TI MSP-FET offers to secure the device by disabling JTAG access. Click Secure Device in the TI MSP-FET menu when a debugging session is running (see

Figure 28 ).

Figure 28. Securing Device With MSP-FET

If only parts of the device are IP protected, MSP-FET displays a console message during connect:

"IP protection is enabled on the device. Not all flash memory locations may be readable or writable".

See the online documentation on www.ti.com/msp432 for details and tools for handling device security.

24

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

6.2.2

Release JTAG on Go Option

When debugging low-power modes the Release JTAG on Go option for the MSP-FET (see

Figure 29 )

should be used to make sure that the debugger does not lose communication with the device. However, with this option selected, the debugger cannot identify breakpoints.

Figure 29. MSP-FET Release JTAG on Go

After enabling the Release JTAG on Go option, execute the RUN command.

6.2.3

Further Advice for MSP-FET in IAR EWARM

If the V

CC voltage is not high enough when trying to erase or write flash memory, the following message is displayed in the console:

"Target device supply voltage is too low for Flash erase/programming".

Raise the supply voltage to correct this error.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

25

Debugging the Application

www.ti.com

6.3

Using Segger J-Link Debug Probe

To use the Segger J-Link debug probe, right click on the active project, then select Options. From the pulldown menu select J-Link/J-Trace (see

Figure 30 ).

Figure 30. Select the Segger J-Link Debug Probe

26

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

Next, switch to the Download pane and enable the Use flash loader(s) option (see

Figure 31

).

Figure 31. Enabling Usage of Flash Loaders

When using a target socket board for the MSP432 MCUs, you can benefit from the 5-V voltage output the

J-Link provides on pin 19 of its Cortex-M debug connector. This option needs to be enabled through the J-

Link Commander, a console application available from Segger. When enabled, the debug probe provide

5 V to the target system. See the

MSP432™ SimpleLink™ Microcontrollers Hardware Tools User's Guide

how to configure the target socket board to use the 5-V power supply to generate 3.3-V device voltage and to Segger's documentation how to enable the voltage output.

Figure 32

shows the effect of the power on command, when applied in the J-Link Commander. Before executing the command, the measured target voltage is 0 V, and right after applying target power, 3.3 V is available as target voltage.

Figure 32. Using J-Link Commander to Enable Power Output to Target System

Now you can download the program and debug using the Segger J-Link debug probe with EWARM.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

27

Debugging the Application

www.ti.com

6.3.1

Working With Device Security

If you have disabled JTAG access on the device or are working on an application where you need to unlock a secure IP zone, a J-Link Script needs to be added to the debug session to enable a factory reset.

During a debug session, launch the J-Link control panel by clicking on the J-Link icon in the status bar

(see

Figure 33

).

Figure 33. Launch J-Link Control Panel

After launching the J-Link control panel, add the MSP432 J-Link script provided in IAR.

Figure 34

shows the location of the script file.

28

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

Figure 34. J-Link Control Panel

The J-Link script now runs at the launch of very debug session and every time code is downloaded to the device. If the device has been secured when trying to download code, a dialog box reports that the device is secured and can be erased (see

Figure 35

).

Figure 35. J-Link Script Detecting That the Device Has Been Secured

Click OK on the dialog box to issue a factory reset, which erases any code present on the device and then starts to download the compiled code. When the factory reset is a complete, a confirmation dialog box reports that the process is complete (see

Figure 36 ).

Figure 36. Device Has Been Unlocked and Erased

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

29

Debugging the Application

www.ti.com

6.4

Using IAR I-jet Debug Probe

To use the IAR I-jet debug probe, right click on the active project, then click Options. From the pulldown

Driver menu, select I-jet / JTAGjet (see

Figure 37 ).

Figure 37. Selecting the IAR I-jet Debug Probe

30

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

Next, switch to the Download pane and enable the Use flash loader(s) option (see

Figure 38

).

Figure 38. Enabling Use of Flash Loaders

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

31

Debugging the Application

www.ti.com

When using a target socket board for the MSP432 MCUs, you can benefit from the 5-V voltage output the

I-jet provides on pin 19 of its Cortex-M debug connector. Go to the I-jet/JTAGjet specific menu and enable the Target Power option (see

Figure 39 ). See the

MSP432™ SimpleLink™ Microcontrollers Hardware

Tools User's Guide

how to configure the target socket board to use the 5-V power supply to generate 3.3-

V device voltage.

Figure 39. Debug Probe Setup

Now you can download the program and debug using the IAR I-jet debug probe with EWARM.

6.4.1

Working With Device Security

If you have disabled JTAG access on the device or are working on an application where you need to unlock a secure IP zone, IAR Embedded Workbench automatically runs a check on the device before downloading code if you are using an IAR I-Jet. If IAR finds that the device has been secured, a dialog box opens as shown in

Figure 40

.

Figure 40. Dialog Box Asking to Perform a Factory Reset

Click Yes to perform a factory reset and unlock the device so that code can be downloaded. Click No to end the debug session and leave the device locked. After the code has been downloaded, the debug session starts.

32

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Debugging the Application

6.5

Debugging Driver Lib in ROM

The MSP432P4xx family includes a complete peripheral driver library (DriverLib) that is fully integrated into the ROM memory. Developers can leverage the ROM DriverLib for multiple benefits including access to highly robust and tested APIs, single-cycle ROM execution speed at lower power consumption, and freeing up memory space for additional application code. Developers can gain access to ROM APIs by adding DriverLib header file to projects and linking to a prebuilt library.

For more information on MSP432P4xx Driver Library and what is provided in ROM DriverLib, see the

MSP432P4xx Driver Library, which is available in the SimpleLink MSP432 SDK.

6.5.1

Enable Use of Software in ROM in MSP432 Project

If the path to the driver library headers and sources is not yet included in the project, add it. Click Project

Options (Alt+F7), then select C/C++ Compiler, and select the Preproccessor tab. Add the include path to the MSP432P4xx driver library source folder in the Additional include directories field (see

Figure 41 ). For example, add C:\ti\MSP432_DriverLib_2_20_00_08\driverlib\MSP432P4xx, assuming that

the driver library was extracted to C:\ti\MSP432_DriverLib_2_20_00_08.

Then in the Defined Symbols field, add TARGET_IS_MSP432P4XX to enable the Software in ROM use.

(see Figure 41 ).

Figure 41. Adding Driver Library to a Project

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

33

Debugging the Application

www.ti.com

6.5.2

Load ROM Symbol Into Debugger

To enable debug of the software in ROM, the corresponding symbol should be loaded. Click Project

Options (ALT+F7) and select Debugger. Then select the Images tab and proceed as follows (see

Figure 42 ):

1. Check the box Download extra image

2. In the Path field, click the browse button and locate the ROM debugging symbols (*.out). The

MSP432P4xx Driver Library provides this file msp432_driverlib_rom_image.out available on

C:\ti\MSP432_DriverLib_2_20_00_08\rom\MSP432P4xx\msp432_driverlib_rom_image.out. It is important to keep the driverlib.c file on the same path as the symbol file in the same directory.

3. In the Offset field, type 0x0.

4. Click OK and start debugging.

Figure 42. Adding ROM Symbol to Debugger

When the next debug session is started, you can step through the ROM API. The IDE automatically opens the corresponding source file (see

Figure 43

). MSPWare also provides the software in ROM symbol available on C:\ti\MSPWare_2_20_00_19\driverlib\rom\MSP432P4xx.

34

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Using Serial Wire Output (SWO) Hardware Trace Analyzer

Figure 43. Stepping Through ROM DriverLib Source Code

7 Using Serial Wire Output (SWO) Hardware Trace Analyzer

The SWO Trace tools for MSP432 MCUs are implemented using the features of the ARM CoreSight™ components, especially the Instrumentation Trace Macrocell (ITM) and Data Watchpoint and Trace Unit

(DWT) (ETM is not present in MSP432 MCUs).

To use SWO trace, an SWO-enabled debug probe must be used. In IAR EWARM, this is currently possible with IAR I-JET, Segger J-Link, TI XDS200, and TI XDS110 debug probes. Change the interface of the debug probe to "SWD" and start a debug session. Trace itself is configured from a running debug session.

Adjust the trace settings to the project settings and frequencies, and start with a lightweight setting. For example, to enable SWO trace for a bare metal blinky example, use SWO trace settings as shown in the following figures.

Figure 44

shows the menu to open the configuration dialogs.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

35

Using Serial Wire Output (SWO) Hardware Trace Analyzer

www.ti.com

Figure 44. Trace Settings Configured From Running Debug Session Using Debugger Menu

Force "Time Stamps" and "PC Samples" in SWO Trace Settings Window Settings (see

Figure 45 ).

Figure 45. SWO Trace Window Settings

Override "Clock Setup" and set the sample rate to a low value in SWO Configuration (see

Figure 46

).

Figure 46. SWO Configuration

36

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Using Serial Wire Output (SWO) Hardware Trace Analyzer

After that, open the trace windows of interest (for example, function profiling and interrupt profiling) and make sure that all the traces are enabled in the corresponding windows. Optionally, instruct the code to output custom events through the Terminal I/O window by adding the following lines:

#include "arm_itm.h"

ITM_EVENT8(1, 'a');

The prerequisite for this is to have the corresponding ITM stimulus ports enabled in the SWO configuration

(see

Figure 46

).

For more information on SWO trace in IAR EWARM, see the user guides on IAR.com.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

37

Erasing the Bootloader (BSL)

8 Erasing the Bootloader (BSL)

www.ti.com

The BSL is a program built into an MSP432 Microcontroller designed to communicate with the device, primarily for the purpose of reading and writing to memory. The BSL can be erased and rewritten but by default the IAR Embedded Workbench tools protect it from accidental deletion.

To erase the BSL right click on the active project, then select Options. Click the Debugger category on the left side and the Download tab. In the Download tab make sure "Use flash loaders(s)" and "Override default .board file" are checked. Then click the Edit button as show in

Figure 47 .

Figure 47. Edit Flash Loader Settings

After you click the edit button, a dialog window pops up that allows to change the flash loader settings.

Select the section of memory where the BSL resides (0x200000 - 0x203fff), and then click Edit

(

Figure 48 ).

Figure 48. Edit Info Memory Settings

38

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Erasing the Bootloader (BSL)

You can now specify extra parameters to pass to the RAM loader. There is also a list of parameters in the

Parameter descriptions info group. To erase the BSL enter "--bsl_erase" in the Extra parameters field as shown in

Figure 49 .

Figure 49. Add --bsl_erase Option

Now the BSL memory will be unprotected during code download and allow the user to erase and overwrite the current BSL. For more information regarding the BSL, see the

MSP432™ SimpleLink™

Microcontrollers Bootloader (BSL) User's Guide

.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

39

EnergyTrace™ Technology

9 EnergyTrace™ Technology

www.ti.com

EnergyTrace™ Technology is an energy-based code analysis tool that measures and displays the application's energy profile and helps to optimize the application for ultra-low power consumption.

MSP432 MCUs with built-in EnergyTrace+[CPU State] (or in short EnergyTrace+) technology allow realtime monitoring of many internal device states while user program code executes. EnergyTrace+ technology is supported on selected MSP432 devices and debuggers.

EnergyTrace mode (without the "+") is the base of EnergyTrace Technology and enables analog energy measurement to determine the energy consumption of an application but does not correlate it to internal device information. The EnergyTrace mode is available for all MSP432 devices with selected debuggers, including IAR EWARM.

9.1

Energy Measurement

Debuggers with EnergyTrace technology support include a new and unique way of continuously measuring the energy supplied to a target microcontroller that differs considerably from the well-known method of amplifying and sampling the voltage drop over a shunt resistor at discrete times. A software controlled DC-DC converter is used to generate the target power supply. The time density of the DC-DC converter charge pulses equals the energy consumption of the target microcontroller. A built-in on-the-fly calibration circuit defines the energy equivalent of a single DC-DC charge pulse.

Figure 50

shows the energy measurement principle. Periods with a small number of charge pulses per time unit indicate low energy consumption and thus low current flow. Periods with a high number of charge pulses per time unit indicate high energy consumption and also a high current consumption. Each charge pulse leads to a rise of the output voltage VOUT, which results in an unavoidable voltage ripple common to all DC-DC converters.

Figure 50. Pulse Density and Current Flow

The benefit of sampling continuously is evident: even the shortest device activity that consumes energy contributes to the overall recorded energy. No shunt-based measurement system can achieve this.

9.2

IAR Embedded Workbench for ARM Integration

EnergyTrace Technology is available as part of IAR Embedded Workbench for ARM microcontrollers version 7.80 or higher exclusively for MSP432 MCUs. During debugging of an application, additional windows are available if the debug probe and the target device support EnergyTrace Technology.

The EnergyTrace+ Technology is available only when using the TI MSP-FET debug probe.

Devices that support EnergyTrace+ Technology allow sampling of internal device states while an application is executing (see

Figure 51 ).

40

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

EnergyTrace™ Technology

Figure 51. Debug Session With EnergyTrace+ Windows

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

41

EnergyTrace™ Technology

Click the TI MSP-FET Emulator menu for EnergyTrace+ related entries (see

Figure 52

).

• State Log

• Power Log

• Timeline www.ti.com

Figure 52. TI MSP-FET Emulator Pulldown Menu With EnergyTrace+ Related Functions

All EnergyTrace-related functions must be enabled first by right-clicking in the respective window and selecting "Enable" (see

Figure 53 ).

Figure 53. Enabling the State Log Window

42

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

EnergyTrace™ Technology

9.2.1

State Log

CPU activity is grouped under States. When a program executes, digital data is collected from the target device and displayed in list format (see

Figure 54 ). The State Log shows at what point in time the CPU

has been activated or deactivated and gives a reference to the program counter location where this happened.

Figure 54. State Log Window With EnergyTrace+ Data

9.2.2

State Log Summary

The State Log Summary window shows a condensed view of the CPU activity of a profiled program (see

Figure 55 ). Click on the column headers to sort the data.

Figure 55. State Log Summary With EnergyTrace+ Data

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

43

EnergyTrace™ Technology

www.ti.com

9.2.3

Power Log Setup

The Power Log Setup can be used to control the analog measurement (see

Figure 56

). Check each parameter to enable data collection.

Figure 56. Power Log Setup Window

9.2.4

Power Log Summary

Similar to the State Log window, the Power Log window shows the current, voltage, and energy profile over time, with reference to the program counter that was sampled at the given time stamp (see

Figure 57 ).

Figure 57. Power Log Window With EnergyTrace+ Data

44

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

EnergyTrace™ Technology

9.2.5

Timeline

When invoking the Timeline for the first time, both Power Log and State graphs are disabled. Right click on each section to enable it, and use the mouse wheel to zoom in and out (see

Figure 58

and

Figure 59 ).

Figure 58. Timeline With Power Log and State Graphs Disabled

Figure 59. Timeline With EnergyTrace+ Data

9.3

Measuring Low-Power Currents

During the capture of the internal states or even when simply executing until breakpoint halt, the target microcontroller is constantly accessed by the JTAG or SWD debug logic. These debug accesses consume energy that is included in the numbers shown in the Power Log window and graph. To measure the absolute power consumption of the application, TI recommends using the EnergyTrace mode in combination with the Release JTAG on Go option. This combination makes sure that the debug logic of the target microcontroller is not accessed while measuring energy consumption.

See

Section 6.2.2

for more details.

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

45

Frequently Asked Questions

www.ti.com

10 Frequently Asked Questions

Q: I cannot program my LaunchPad development kit; the IDE cannot connect to target. What's wrong?

A: Check the following:

• Is the JTAG switch (S101) in the correct orientation?

Switch to left for XDS110-ET onboard debugger

Switch to the right for external debugger connection

• Check the debugger settings and change to Serial Wire Debug (SWD) without SWO. When the settings of Port J (PJSEL0 and PJSEL1 bits) are changed, full JTAG access is prevented on these pins. Changing to use SWD allows access through the dedicated debug pins only.

Figure 60

shows how to configure the debugger to use SWD instead of JTAG by opening the debugger settings window.

Figure 60. Choosing SWD in Debugger Settings

• If even this cannot connect, reset the device to factory settings. Review the Device Security section of the

Code Composer Studio™ IDE 7.1+ for SimpleLink™ MSP432™ Microcontrollers User's Guide

for information on how to perform a factory reset on the device.

Q: Why doesn't the backchannel UART on the MSP432 LaunchPad development kit work with my serial terminal program at speeds faster than 56000 baud?

A: Certain serial terminal programs such as HTerm or the CCS built-in terminal might not work with the

MSP432 LaunchPad development kit at specific baud rates, resulting in the software not being able to open the virtual COM port or in the baud rate being configured incorrectly. An issue with the LaunchPad emulator firmware has been identified and will be fixed in the next release. Until the update is available, use Tera Term, ClearConnex, or HyperTerminal instead, or reduce the baud rate to speeds of 38400 baud or lower.

46

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

www.ti.com

Additional IAR EWARM Information

Q: Problems plugging the MSP432 LaunchPad development kit into a USB3.0 Port

A: When the MSP432 LaunchPad development kit is connected to USB3.0 ports provided by a certain combination of USB3.0 host controller hardware and device drivers, the IDE cannot establish a debug session with the LaunchPad development kit, resulting in an error message similar to "CS_DAP_0: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed" in the case of

Code Composer Studio. In this case, the CCS-provided low-level command line utility xdsdfu also cannot establish a connection with the LaunchPad development kit.

This issue has been observed on PCs running Windows 7 that show the "Renesas Electronics USB 3.0

Host Controller" and the associated "Renesas Electronics USB 3.0 Root Hub" in the device manager.

After updating the associated Windows USB drivers to more recent versions obtained from the hardware vendor, the issue was resolved. Other USB3.0 hardware and device driver combinations might lead to the same issue. If you might be affected, contact the PC vendor or locate and install more recent versions of the USB3.0 device drivers. Alternatively, connect the LaunchPad development kit to an USB2.0 port on the PC, if one is available.

Q: I cannot get the backchannel UART to connect. What's wrong?

A: Check the following:

• Do the baud rate in the host terminal application and the eUSCI settings match?

• Are the appropriate jumpers in place on the isolation jumper block?

• Probe on RXD and send data from the host. If you don't see data, it might be a problem on the host side.

• Probe on TXD while sending data from the MSP432 MCU. If you don't see data, it might be a configuration problem with the eUSCI module.

• Consider the use of the hardware flow control lines (especially for higher baud rates).

11 Additional IAR EWARM Information

For more information about IAR Embedded Workbench, visit the following links:

• IAR Support

• IAR User's Guides for IAR Embedded Workbench for ARM

• IAR Embedded Workbench

• IAR Embedded Workbench Product News

12 References

1.

MSP432™ SimpleLink™ Microcontrollers Bootloader (BSL) User's Guide

2.

SimpleLink MSP432 SDK

3.

Debuggers for MSP432 Microcontrollers

4.

Migration Guide for SimpleLink MSP432 SDK

5.

CMSIS Pack Documentation

6.

MSP432P4xx CMSIS Device Family Pack

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IAR Embedded Workbench

® for ARM

®

7.80.3+ for SimpleLink™ MSP432™ Microcontrollers

Copyright © 2015–2017, Texas Instruments Incorporated

47

Revision History

www.ti.com

Revision History

NOTE: Page numbers for previous revisions may differ from page numbers in the current version.

Changes from March 7, 2017 to May 26, 2017

.................................................................................................................

Page

• Updated

Section 6 , Debugging the Application

.....................................................................................

19

• Added the paragraph that starts "If only parts of the device are IP protected..." in

Section 6.2.1

, Working With Device

Security

...................................................................................................................................

24

• Added

Section 6.2.3

, Further Advice for MSP-FET in IAR EWARM

.............................................................

25

• Added

Section 7 , Using Serial Wire Output (SWO) Hardware Trace Analyzer

.................................................

35

48

Revision History

Copyright © 2015–2017, Texas Instruments Incorporated

SLAU574G – March 2015 – Revised May 2017

Submit Documentation Feedback

IMPORTANT NOTICE FOR TI DESIGN INFORMATION AND RESOURCES

Texas Instruments Incorporated (‘TI”) technical, application or other design advice, services or information, including, but not limited to, reference designs and materials relating to evaluation modules, (collectively, “TI Resources”) are intended to assist designers who are developing applications that incorporate TI products; by downloading, accessing or using any particular TI Resource in any way, you

(individually or, if you are acting on behalf of a company, your company) agree to use it solely for this purpose and subject to the terms of this Notice.

TI’s provision of TI Resources does not expand or otherwise alter TI’s applicable published warranties or warranty disclaimers for TI products, and no additional obligations or liabilities arise from TI providing such TI Resources. TI reserves the right to make corrections, enhancements, improvements and other changes to its TI Resources.

You understand and agree that you remain responsible for using your independent analysis, evaluation and judgment in designing your applications and that you have full and exclusive responsibility to assure the safety of your applications and compliance of your applications

(and of all TI products used in or for your applications) with all applicable regulations, laws and other applicable requirements. You represent that, with respect to your applications, you have all the necessary expertise to create and implement safeguards that (1) anticipate dangerous consequences of failures, (2) monitor failures and their consequences, and (3) lessen the likelihood of failures that might cause harm and take appropriate actions. You agree that prior to using or distributing any applications that include TI products, you will thoroughly test such applications and the functionality of such TI products as used in such applications. TI has not conducted any testing other than that specifically described in the published documentation for a particular TI Resource.

You are authorized to use, copy and modify any individual TI Resource only in connection with the development of applications that include the TI product(s) identified in such TI Resource. NO OTHER LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE TO

ANY OTHER TI INTELLECTUAL PROPERTY RIGHT, AND NO LICENSE TO ANY TECHNOLOGY OR INTELLECTUAL PROPERTY

RIGHT OF TI OR ANY THIRD PARTY IS GRANTED HEREIN, including but not limited to any patent right, copyright, mask work right, or other intellectual property right relating to any combination, machine, or process in which TI products or services are used. Information regarding or referencing third-party products or services does not constitute a license to use such products or services, or a warranty or endorsement thereof. Use of TI Resources may require a license from a third party under the patents or other intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI.

TI RESOURCES ARE PROVIDED “AS IS” AND WITH ALL FAULTS. TI DISCLAIMS ALL OTHER WARRANTIES OR

REPRESENTATIONS, EXPRESS OR IMPLIED, REGARDING TI RESOURCES OR USE THEREOF, INCLUDING BUT NOT LIMITED TO

ACCURACY OR COMPLETENESS, TITLE, ANY EPIDEMIC FAILURE WARRANTY AND ANY IMPLIED WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL

PROPERTY RIGHTS.

TI SHALL NOT BE LIABLE FOR AND SHALL NOT DEFEND OR INDEMNIFY YOU AGAINST ANY CLAIM, INCLUDING BUT NOT

LIMITED TO ANY INFRINGEMENT CLAIM THAT RELATES TO OR IS BASED ON ANY COMBINATION OF PRODUCTS EVEN IF

DESCRIBED IN TI RESOURCES OR OTHERWISE. IN NO EVENT SHALL TI BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL,

COLLATERAL, INDIRECT, PUNITIVE, INCIDENTAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES IN CONNECTION WITH OR

ARISING OUT OF TI RESOURCES OR USE THEREOF, AND REGARDLESS OF WHETHER TI HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES.

You agree to fully indemnify TI and its representatives against any damages, costs, losses, and/or liabilities arising out of your noncompliance with the terms and provisions of this Notice.

This Notice applies to TI Resources. Additional terms apply to the use and purchase of certain types of materials, TI products and services.

These include; without limitation, TI’s standard terms for semiconductor products http://www.ti.com/sc/docs/stdterms.htm

), evaluation modules , and samples ( http://www.ti.com/sc/docs/sampterms.htm

).

Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265

Copyright © 2017, Texas Instruments Incorporated

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement