MPS430用户手册

来源：爱go旅游网

IAREmbeddedWorkbench™Version3+forMSP430™

User'sGuide

LiteratureNumber:SLAU138AFJune2004–RevisedJune2014

Contents

Preface........................................................................................................................................61

GetStartedNow!..................................................................................................................8

1.11.21.3

SoftwareInstallation.........................................................................................................9FlashingtheLED............................................................................................................9ImportantMSP430DocumentsontheCD-ROMandWeb...........................................................10Overview.....................................................................................................................UsingKickStart.............................................................................................................2.2.1ProjectSettings....................................................................................................2.2.2UsingMathLibraryforMSP430(MSPMathlib)inIAREW4305.60.1andNewer........................2.2.3AdditionalProjectSettingsforMSP430L092andMSP430C092...........................................2.2.4CreatingaProjectFromScratch................................................................................2.2.5AdditionalProjectSettingsforUltra-Low-PowerMode(LPMx.5)Debugging.............................2.2.6PasswordProtectionforMSP430Devices....................................................................2.2.7UsinganExistingIARV1.x,V2.x,orV3.xProject............................................................2.2.8StackManagementand.xclFiles...............................................................................2.2.9HowtoGenerateTexasInstruments.TXT(andOtherFormat)Files......................................2.2.10OverviewofExamplePrograms................................................................................UsingC-SPY................................................................................................................2.3.1BreakpointTypes..................................................................................................2.3.2UsingBreakpoints.................................................................................................2.3.3UsingSingleStep.................................................................................................2.3.4UsingWatchWindows............................................................................................Introduction..................................................................................................................EnergyMeasurement......................................................................................................IAREmbeddedWorkbench®forMSP430Integration.................................................................3.3.1DebuggingDevicesWithEnergyTrace++TechnologySupport.............................................3.3.2DebuggingDevicesWithoutEnergyTrace++TechnologySupport.........................................MeasuringLow-PowerCurrents..........................................................................................EnergyTraceTechnologyFAQs..........................................................................................

121213141416171818191919191922222324242424313435

DevelopmentFlow..............................................................................................................11

2.12.2

2.3

EnergyTrace™Technology..................................................................................................24

3.13.23.3

3.43.5

MemoryProtectionUnit(MPU)andIntellectualPropertyEncapsulation(IPE)............................37FrequentlyAskedQuestions................................................................................................38

A.1A.2A.3

Hardware....................................................................................................................39ProgramDevelopment(Assembler,C-Compiler,Linker).............................................................39Debugging(C-SPY)........................................................................................................41Menus........................................................................................................................B.1.1Emulator→DeviceInformation.................................................................................B.1.2Emulator→ReleaseJTAGonGo..............................................................................B.1.3Emulator→ResynchronizeJTAG..............................................................................B.1.4Emulator→InitNewDevice.....................................................................................B.1.5Emulator→Secure-BlowJTAGFuse........................................................................B.1.6Emulator→BreakpointUsage..................................................................................

FET-SpecificMenus............................................................................................................45

B.1

2Contents

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

B.1.7B.1.8B.1.9B.1.10B.1.11B.1.12B.1.13B.1.14B.1.15B.1.16B.1.17

Emulator→Advanced→ClockControl.......................................................................Emulator→Advanced→EmulationMode....................................................................Emulator→Advanced→MemoryDump......................................................................Emulator→Advanced→BreakpointCombiner.............................................................Emulator→StateStorageControl............................................................................Emulator→StateStorageWindow...........................................................................Emulator→SequencerControl................................................................................Emulator→\"Poweron\"Reset.................................................................................Emulator→GIEon/off..........................................................................................Emulator→LeaveTargetRunning...........................................................................Emulator→ForceSingleStepping............................................................................

474747474747474747

RevisionHistory..........................................................................................................................48

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

Contents3

www.ti.com

ListofFigures

1-1.1-2.2-1.2-2.2-3.2-4.2-5.2-6.3-1.3-2.3-3.3-4.3-5.3-6.3-7.3-8.3-9.3-10.3-11.3-12.3-13.3-14.3-15.3-16.3-17.3-18.3-19.3-20.3-21.4-1.

..............................................................................................................9

ActivateProjectinWorkspaceOverview................................................................................10L092Mode..................................................................................................................14C092EmulationMode.....................................................................................................15C092Password.............................................................................................................15EnableUltra-Low-PowerDebugMode..................................................................................17LPMx.5Notifications.......................................................................................................18JTAGPassword............................................................................................................18PulseDensityandCurrentFlow..........................................................................................24DebugSessionWithEnergyTrace++Windows........................................................................25DebugOptions..............................................................................................................26EmulatorPulldownMenuWithEnergyTrace++-RelatedFunctions.................................................27EnablingtheStateLogWindow..........................................................................................27StateLogWindowWithEnergyTrace++Data..........................................................................28StateLogSummaryWithEnergyTrace++Data........................................................................28PowerLogSetupWindow.................................................................................................28PowerLogWindowWithEnergyTrace++Data........................................................................29TimelineWithPowerLogandStateGraphsDisabled................................................................29TimelineWithEnergyTrace++Data.....................................................................................30FunctionProfilerWithEnergyTrace++Data............................................................................30DebugSessionWithEnergyTraceWindows...........................................................................31EmulatorPulldownMenuWithEnergyTrace-RelatedFunctions.....................................................32PowerLogSetupWindow.................................................................................................32PowerLogWindowWithEnergyTraceData...........................................................................33TimelineWithPowerLogGraphDisabled..............................................................................33TimelineWithEnergyTraceData.........................................................................................34LPM3CurrentWhenExecutingUnderDebugControl................................................................34ReleaseJTAGonGoOptioninEmulatorPulldownMenu...........................................................35LPM3CurrentWhenExecutingwithJTAGSignalsReleased.......................................................35MPUConfigurationDialog................................................................................................37

ActivateProject

4ListofFigures

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

ListofTables

2-1.

DeviceArchitecture,Breakpoints,andOtherEmulationFeatures...................................................20

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

ListofTables5

Preface

SLAU138AF–June2004–RevisedJune2014

ReadThisFirst

AboutThisManual

ThismanualdescribestheuseofIAREmbeddedWorkbench®(EW430)withtheMSP430™ultra-low-powermicrocontrollers.

HowtoUseThisManual

ReadandfollowtheinstructionsintheGetStartedNow!chapter.Thischapterprovidesinstructionsoninstallingthesoftware,anddescribeshowtorunthedemonstrationprograms.Afteryouseehowquickandeasyitistousethedevelopmenttools,TIrecommendsthatyoureadallofthismanual.

Thismanualdescribesonlythesetupandbasicoperationofthesoftwaredevelopmentenvironment,butitdoesnotfullydescribetheMSP430microcontrollersorthecompletedevelopmentsoftwareandhardwaresystems.Fordetailsoftheseitems,seetheappropriateTIandIAR™documentslistedinRelatedDocumentationFromTexasInstruments,ImportantMSP430DocumentsontheCD-ROMandWeb.ThismanualappliestotheusewithTexasInstruments'MSP-FET430UIF,MSP-FET430PIF,andeZ430developmenttoolsseries.

Thesetoolscontainthemostup-to-datematerialsavailableatthetimeofpackaging.Forthelatest

materials(includingdatasheets,user'sguides,software,andapplicationinformation),visittheTIMSP430websiteatwww.ti.com/msp430orcontactyourlocalTIsalesoffice.

InformationAboutCautionsandWarnings

Thisbookmaycontaincautionsandwarnings.

CAUTION

Thisisanexampleofacautionstatement.

Acautionstatementdescribesasituationthatcouldpotentiallydamageyoursoftwareorequipment.

WARNINGThisisanexampleofawarningstatement.Awarningstatementdescribesasituationthatcouldpotentiallycauseharmtoyou.Theinformationinacautionorawarningisprovidedforyourprotection.Readeachcautionandwarningcarefully.

MSP430,EnergyTracearetrademarksofTexasInstruments.6ReadThisFirstIAREmbeddedWorkbenchisaregisteredtrademarkofIARSystemsAB.Allothertrademarksarethepropertyoftheirrespectiveowners.

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comRelatedDocumentationFromTexasInstruments

RelatedDocumentationFromTexasInstruments

MSP430developmenttoolsdocumentation

MSP430HardwareToolsUser'sGuide,literaturenumberSLAU278

eZ430-F2013DevelopmentToolUser'sGuide,literaturenumberSLAU176eZ430-RF2480User'sGuide,literaturenumberSWRA176

eZ430-RF2500DevelopmentToolUser'sGuide,literaturenumberSLAU227

eZ430-RF2500-SEHDevelopmentToolUser'sGuide,literaturenumberSLAU273eZ430-ChronosDevelopmentToolUser'sGuide,literaturenumberSLAU292MSP430devicedatasheets

MSP430x1xxFamilyUser'sGuide,literaturenumberSLAU049MSP430x2xxFamilyUser'sGuide,literaturenumberSLAU144MSP430x3xxFamilyUser'sGuide,literaturenumberSLAU012MSP430x4xxFamilyUser'sGuide,literaturenumberSLAU056

MSP430x5xxandMSP430x6xxFamilyUser'sGuide,literaturenumberSLAU208MSP430FR57xxFamilyUser'sGuide,literaturenumberSLAU272

MSP430FR58xx,MSP430FR59xx,MSP430FR68xx,andMSP430FR69xxFamilyUser'sGuide,literaturenumberSLAU367CC430devicedatasheets

CC430FamilyUser'sGuide,literaturenumberSLAU259

IfYouNeedAssistance

SupportfortheMSP430devicesandtheFETdevelopmenttoolsisprovidedbytheTexasInstrumentsProductInformationCenter(PIC).ContactinformationforthePICcanbefoundontheTIwebsiteat

www.ti.com/support.TheTexasInstrumentsE2ECommunitysupportforumsfortheMSP430isavailabletoprovideopeninteractionwithpeerengineers,TIengineers,andotherexperts.Additionaldevice-specificinformationcanbefoundontheMSP430website.

NOTE:

TheKickStartkitissupportedbyTexasInstruments.

AlthoughtheKickStartkitisaproductofIAR,TexasInstrumentsprovidesthesupportforit.Therefore,pleasedonotrequestsupportforKickStartfromIAR.ConsulttheextensivedocumentationprovidedwithKickStartbeforerequestingassistance.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

ReadThisFirst7

Chapter1

SLAU138AF–June2004–RevisedJune2014

GetStartedNow!

Thischapterprovidesinstructiononinstallingthesoftware,andshowshowtorunthedemonstrationprograms.

Topic

Page

1.11.21.3

SoftwareInstallation.............................................................................................9FlashingtheLED.................................................................................................9ImportantMSP430DocumentsontheCD-ROMandWeb........................................10

8GetStartedNow!

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comSoftwareInstallation

1.1SoftwareInstallation

FollowtheinstructionsonthesuppliedREADMEFIRSTdocumenttoinstalltheIAREmbeddedWorkbench™KickStartkit.Readthefile\\EmbeddedWorkbench

x.x\\430\\doc\\readme.htmfromIARforthelatestinformationabouttheWorkbench.ThetermKickStart

referstothefunction-limitedversionofEmbeddedWorkbench(includingC-SPY™debugger).KickStartissuppliedontheCD-ROMincludedwitheachFET,andthelatestversionisavailablefromtheMSP430website.

Thedocumentsmentionedinthepreviousparagraph(andthisdocument)canbeaccessedusing:Start→Programs→IARSystems→IAREmbeddedWorkbenchKickStartforMSP430V3.

KickStartiscompatiblewithWindows2000(SP4),WindowsXP(32bitandbit),WindowsVista(32bitandbit),andWindows7(32bitandbit).However,theUSBFETinterfaceworkswithonlyWindowsXP(32bitandbit),WindowsVista(32bitandbit),andWindows7(32bitandbit).

1.2FlashingtheLED

ThissectiondemonstratesontheFETtheequivalentoftheC-language\"HelloWorld!\"introductoryprogram.AnapplicationthatflashestheLEDisdevelopedanddownloadedtotheFET,andthenrun.1.StarttheWorkbench(Start→Programs→IARSystems→IAREmbeddedWorkbenchKickStartforMSP430V3→IAREmbeddedWorkbench).

2.ClickFile→OpenWorkspacetoopenthefileat:\\EmbeddedWorkbenchx.x\\430\\FET_examples\\FlashingtheLED.eww.Theworkspacewindowopens.

3.ClickonthetabatthebottomoftheworkspacewindowthatcorrespondstotheMSP430device(MSP430xxxx)anddesiredlanguage(assemblerorC)tosetaprojectactive(seeFigure1-1).

Figure1-1.ActivateProject

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

GetStartedNow!9

ImportantMSP430DocumentsontheCD-ROMandWebwww.ti.com

Alternatively,rightclicktoactivateaprojectintheWorkspaceOverviewtab(seeFigure1-2).

Figure1-2.ActivateProjectinWorkspaceOverview

4.ClickProject→Options→FETDebugger→Setup→Connectiontoselecttheappropriateport:

TexasInstrumentsLPT-IFfortheparallelFETInterface(MSP-FET430PIF)orTexasInstrumentsUSB-IFfortheUSBInterface(MSP-FET430UIF)orfortheeZ430.

5.ClickProject→RebuildAlltobuildandlinkthesourcecode.Youcanviewthesourcecodebydouble-clickingontheproject,andthendouble-clickingonthedisplayedsourcefile.

6.ClickProject→DebugtostarttheC-SPYdebugger.C-SPYerasesthedeviceflashandthendownloadstheapplicationobjectfiletothedeviceflash.

SeeFAQDebugging#1ifC-SPYisunabletocommunicatewiththedevice.7.ClickDebug→Gotostarttheapplication.TheLEDshouldflash.

8.ClickDebug→StopDebuggingtostopdebugging,toexitC-SPY,andtoreturntotheWorkbench.9.ClickFile→ExittoexittheWorkbench.

Congratulations,youhavejustbuiltandtestedanMSP430application!

1.3ImportantMSP430DocumentsontheCD-ROMandWeb

TheprimarysourcesofMSP430informationarethedevice-specificdatasheetanduser'sguide.Themostup-to-dateversionsofthesedocumentsthatareavailableatthetimeofproductionareprovidedontheCD-ROMincludedwiththistool.TheMSP430website(www.ti.com/msp430)containsthemostrecentversionofthesedocuments.

PDFdocumentsdescribingtheIARtools(WorkbenchandC-SPY,theassembler,theCcompiler,thelinker,andthelibrarian)areinthecommon\\docand430\\docfolders.Supplementstothedocuments(thatis,thelatestinformation)areavailableinHTMLformatinthesamedirectories.430\\doc\\readme_start.htmprovidesaconvenientstartingpointfornavigatingtheIARdocumentation.

10GetStartedNow!

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

Chapter2

SLAU138AF–June2004–RevisedJune2014

DevelopmentFlow

ThischapterdescribeshowtouseKickStarttodevelopapplicationsoftwareandhowtouseC-SPYtodebugit.

Topic

Page

2.12.22.3

Overview...........................................................................................................12UsingKickStart..................................................................................................12UsingC-SPY......................................................................................................19

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow11

Overviewwww.ti.com

2.1Overview

ApplicationsaredevelopedinassemblerorCusingtheWorkbench,andtheyaredebuggedusingC-SPY.C-SPYisseamlesslyintegratedintotheWorkbench.However,itismoreconvenienttomakethe

distinctionbetweenthecodedevelopmentenvironment(Workbench)andthedebugger(C-SPY).C-SPYcanbeconfiguredtooperatewiththeFET(thatis,anactualMSP430device)orwithasoftwaresimulatorofthedevice.KickStartreferstotheWorkbenchandC-SPYcollectively.TheKickStartsoftwaretoolsareaproductofIAR.

DocumentationfortheMSP430familyandKickStartisextensive.TheCD-ROMsuppliedwiththistoolcontainsalargeamountofdocumentationdescribingtheMSP430.TheMSP430homepage

(www.ti.com/msp430)isanothersourceofMSP430information.ThecomponentsofKickStart(workbenchanddebugger,assembler,compiler,linker)arefullydocumentedin\\Embedded

Workbenchx.x\\common\\docand\\EmbeddedWorkbench\\430\\doc..htmfileslocatedthroughouttheKickStartdirectorytreecontainthemostup-to-dateinformationandsupplementthePDFfiles.Inaddition,KickStartdocumentationisavailableonlineviaHelp.

ReadMeFirstfilesfromIARandTIandthisdocumentcanbeaccessedusingStart→Programs→IARSystems→IAREmbeddedWorkbenchKickStartforMSP430V3.

Tool

Workbench,C-SPYAssemblerCompilerClibrary

LinkerandLibrarian

xlink.pdf

User'sGuide

EW430_UsersGuide.pdf

EW430_AssemblerReference.pdfEW430_CompilerReference.pdf

MostUp-To-DateInformation

readme.htm,ew430.htm,cs430.htm,cs430f.htma430.htm,a430_msg.htmicc430.htm,icc430_msg.htmCLibrary.htm

xlink.htm,xman.htm,xar.htm

2.2UsingKickStart

TheKickStarteditionisaspecialstarterkitorevaluationversionofIAREmbeddedWorkbenchwithlimitationsbothincodesizeandintheserviceandsupportthatisprovided.Limitations:•TheCcompilerdoesnotgenerateanassemblycodelistfile.

•ThecodesizelimitoftheMSP430IARKickStartC/C++Compilerissetto4KbytesfortraditionalMSP430devicesand8KbytesforMSP430Xdevices(seeTable2-1fordetailedinformationaboutwhichMSP430deviceisbasedonwhicharchitecture).

•TheIARAssemblerdeliveredisthefullversionwithoutanyrestrictions.

•TheIARXLINKLinkerlinksamaximumof4KbytesoriginatingfromCsourcecodefortraditionalMSP430devicesand8KbytesforMSP430Xdevices(seeTable2-1fordetailedinformationaboutwhichMSP430deviceisbasedonwhicharchitecture),butanunlimitedamountofcodeoriginatingfromassemblycode.

•TheIARKickStartC-SPYSimulatorreadsamaximumof4KbytesoriginatingfromCcodefortraditionalMSP430devicesand8KbytesforMSP430Xdevicesbutisunlimitedintheamountof

assemblycoderead(seeTable2-1fordetailedinformationaboutwhichMSP430deviceisbasedonwhicharchitecture).

•MISRACisnotavailable.

•Theruntimelibrarysourcecodeisnotincluded.

Afull(thatis,unrestricted)versionofthesoftwaretoolscanbepurchasedfromIAR.Amid-featuredtoolset–calledBaseline,witha12KbyteC-codesizelimitationandbasicfloating-pointoperations–isalsoavailablefromIAR.SeetheIARwebsite(www.iar.se)formoreinformation.

12DevelopmentFlow

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comUsingKickStart

2.2.1ProjectSettings

ThesettingsrequiredtoconfiguretheWorkbenchandC-SPYarenumerousanddetailed.Readand

thoroughlyunderstandthedocumentationsuppliedbyIARwhendealingwithprojectsettings.ReviewtheprojectsettingsofthesuppliedassemblerandCexamples(theprojectsettingsareaccessedusingProject→Optionswiththeprojectnameselected).Usetheseprojectsettingsastemplateswhen

developingyourownprojects.Notethatiftheprojectnameisnotselectedwhensettingsaremade,thesettingsareappliedtotheselectedfile(nottotheproject).

Thefollowingprojectsettingsarerecommendedorrequired:

•Specifythetargetdevice(GeneralOptions→Target→Device).

•EnableanassemblerprojectoraCorassemblerproject(GeneralOptions→Target→Assembler-onlyproject).

•Enablethegenerationofanexecutableoutputfile(GeneralOptions→Output→Outputfile→Executable).

•TomosteasilydebugaCproject,disableoptimization[C/C++Compiler→Optimizations→Size→None(Bestdebugsupport)].

•Enablethegenerationofdebuginformationinthecompileroutput(C/C++Compiler→Output→Generatedebuginformation).

•SpecifythesearchpathfortheCpreprocessor(C/C++Compiler→Preprocessor→IncludePaths).•Enablethegenerationofdebuginformationintheassembleroutput(Assembler→Output→GenerateDebugInfo).

•Specifythesearchpathfortheassemblerpreprocessor(Assembler→Preprocessor→IncludePaths).

•TodebugtheprojectusingC-SPY,specifyacompatibleformat[Linker→Output→Format→DebuginformationforC-SPY(withruntimecontrolmodulesorwithI/Oemulationmodules)].•Specifythesearchpathforanyusedlibraries(Linker→Config→Searchpaths).

•SpecifytheC-SPYdriver.SelectProject→Options→Debugger→Setup→Driver→FETDebuggertodebugontheFET(thatis,MSP430device).SelectSimulatortodebugonthesimulator.IfFETDebuggerisselected,useProject→Options→FETDebugger→Setup→Connectiontoselecttheappropriateport:TexasInstrumentsLPT-IFfortheparallelFETInterface(MSP-FET430PIF)orTexasInstrumentsUSB-IFfortheUSBInterface(MSP-FET430UIF)orfortheeZ430.

•EnabletheDeviceDescriptionfile.ThisfilemakesC-SPY\"aware\"ofthespecificsofthedeviceitisdebugging.Thisfilecorrespondstothespecifiedtargetdevice(Debugger→Setup→Devicedescriptionfile→Overridedefault).

•EnabletheerasureoftheMainandInformationmemoriesbeforeobjectcodedownload(FETDebugger→Download→ErasemainandInformationmemory).

•Tomaximizesystemperformanceduringdebug,disableVirtualBreakpoints(FETDebugger→Breakpoints→Usevirtualbreakpoints)anddisableallSystemBreakpoints(FETDebugger→Breakpoints→Systembreakpointson).

NOTE:

UseFactorySettingstoquicklyconfigureaproject.

UsetheFactorySettingsbuttontoquicklyconfigureaprojecttoausablestate.

Thefollowingstepscanbeusedtoquicklyconfigureaproject.NotethattheGeneralOptionstabdoesnothaveaFactorySettingsbutton.

1.Specifythetargetdevice(GeneralOptions→Target→Device).

2.EnableanassemblerprojectoraCorassemblerproject(GeneralOptions→Target→Assembler-onlyproject).

3.Enablethegenerationofanexecutableoutputfile(GeneralOptions→Output→Outputfile→Executable).

4.Acceptthefactorysettingsforthecompiler(C/C++Compiler→FactorySettings).5.Acceptthefactorysettingsfortheassembler(Assembler→FactorySettings).

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow

UsingKickStartwww.ti.com

6.7.8.9.

Acceptthefactorysettingsforthelinker(Linker→FactorySettings).AcceptthefactorysettingsforC-SPY(Debugger→FactorySettings).Debugonthehardware(Debugger→Setup→Driver→FETDebugger).

SpecifytheactiveparallelportusedtointerfacetotheFETifnotLPT1(FETDebugger→Setup→Connection→TexasInstrumentsLPT-IF)orspecifytheUSBport(FETDebugger→Setup→Connection→TexasInstrumentsUSB-IF).

NOTE:

Avoidtheuseofabsolutepathnameswhenreferencingfiles.

Instead,usetherelativepathnamekeywords$TOOLKIT_DIR$and$PROJ_DIR$.SeetheIARdocumentationforadescriptionofthesekeywords.Theuseofrelativepathnamespermitsprojectstobemovedeasily,andprojectsdonotrequiremodificationwhenIARsystemsareupgraded(forexample,fromKickStartorBaselinetoFull).

2.2.2UsingMathLibraryforMSP430(MSPMathlib)inIAREW4305.60.1andNewer

TI'sMSPMathlibispartofEW4305.60.1andnewerreleases.Thisoptimizedlibraryprovidesupto26xbetterperformanceinapplicationsthatusefloatingpointscalarmath.Fordetails,seetheMSPMathlibwebpage(http://www.ti.com/tool/mspmathlib).

MSPMathlibmaybeenabledfornewandexistingprojectsonallsupporteddevices.EnableordisableMSPMathlibintheprojectoptions(GeneralOptions→LibraryConfiguration→MathLib).

2.2.3AdditionalProjectSettingsforMSP430L092andMSP430C092

TheMSP430L092canoperateintwodifferentmodes:L092modeandC092emulationmode.ThepurposeoftheC092emulationmodeistobehavelikeaC092withupto1920bytesofcodeatitsfinaldestinationformaskgeneration.

TheoperationmodeisdeterminedbyEW430beforestartingthedebugger.Tworadiobuttonsare

availableforthemodeselection.BydefaulttheL092modeisselected(seeFigure2-1andFigure2-2).

Figure2-1.L092Mode

14DevelopmentFlow

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comUsingKickStart

Figure2-2.C092EmulationMode

2.2.3.1

MSP430L092LoaderCode

TheLoaderCodeintheMSP430L092isaROM-codefromTIthatprovidesaseriesofservices.ItenablescustomerstobuildautonomousapplicationswithoutneedingtodevelopaROMmask.SuchanapplicationconsistsofanMSP430devicecontainingtheloader(forexample,MSP430L092)andanSPImemorydevice(forexample,'95512or'25AA40);theseandsimilardevicesareavailablefromvariousmanufacturers.

ThemajorityofusecasesforanapplicationwithaloaderdeviceandexternalSPImemoryfornative0.9-Vsupplyvoltagearelatedevelopment,prototyping,andsmallseriesproduction.Figure2-1showstheselectionforloadingtheapplicationintotheexternalSPImemory.2.2.3.2

PasswordProtectionofMSP430C092

TheMSP430C092isacustomer-specificROMdevicethatisprotectedbyapassword.Tostartadebugsession,thepasswordmustbeprovidedtoEW430.Figure2-3showshowtoprovideaHEXpasswordinEW430.

Figure2-3.C092Password

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow15

UsingKickStartwww.ti.com

2.2.4CreatingaProjectFromScratch

Thissectionpresentsstep-by-stepinstructionstocreateanassemblerorCprojectfromscratch,andtodownloadandruntheapplicationontheMSP430(seealsoSection2.2.1,ProjectSettings).TheMSP430IAREmbeddedWorkbenchIDEUser'sGuidepresentsamorecomprehensiveoverviewoftheprocess.1.StarttheWorkbench(Start→Programs→IARSystems→IAREmbeddedWorkbenchKickStartforMSP430V3→IAREmbeddedWorkbench).2.Createanewtextfile(File→New→File).3.Entertheprogramtextintothefile.

NOTE:

Use.hfilestosimplifyyourcodedevelopment.

KickStartissuppliedwithfilesthatdefinethedeviceregistersandthebitnamesforeachdevice.Thesefilescangreatlysimplifythetaskofdevelopingyourprogram.Thefilesarelocatedin\\EmbeddedWorkbenchx.x\\430\\inc.Includethe.hfile

correspondingtoyourtargetdeviceinyourtextfile(#include\"msp430xyyy.h\").Additionally,filesio430xxxx.hareprovidedandareoptimizedtobeincludedbyCsourcefiles.

4.Savetheprogramtextfile(File→Save).

Itisrecommendedthatassemblertextfilesbesavedwithafile-typesuffixof\".s43\"andthatCtextfilesbesavedwithafile-typesuffixof\".c\".

5.Createanewworkspace(File→New→Workspace).

6.Createanewproject(Project→CreateNewProject).SelectToolchain:MSP430,ProjectTemplates:EmptyprojectandclickOK.SpecifyaprojectnameandclickSave.

7.Addtheprogramtextfiletotheproject(Project→AddFiles).SelecttheprogramtextfileandclickOpen.Alternatively,double-clickonthefiletoaddittotheproject.

NOTE:

Howtoaddassemblersourcefilestoyourproject

ThedefaultfiletypepresentedintheAddFileswindowis\"C/C++Files\".Toviewassemblerfiles(.s43),select\"AssemblerFiles\"inthe\"Filesoftype\"drop-downmenu.

8.Savetheworkspace(File→SaveWorkspace).SpecifyaworkspacenameandclickSave.

9.Configuretheprojectoptions(Project→Options).Foreachofthesubcategories(GeneralOptions,C/C++Compiler,Assembler,Linker,Debugger),acceptthedefaultFactorySettingswiththefollowingexceptions:

•Specifythetargetdevice(GeneralOptions→Target→Device).

•EnableanassemblerprojectoraCorassemblerproject(GeneralOptions→Target→

Assembler-onlyproject).

•Enablethegenerationofanexecutableoutputfile(GeneralOptions→Output→Outputfile→

Executable).

•TodebugontheFET(thatis,theMSP430),clickDebugger→Setup→Driver→FETDebugger.•SpecifytheactiveportusedtointerfacetotheFET(FETDebugger→Setup→Connection).10.Buildtheproject(Project→RebuildAll).

11.DebugtheapplicationusingC-SPY(Project→Debug).ThisstartsC-SPY,andC-SPYtakescontrolofthetarget,erasesthetargetmemory,programsthetargetmemorywiththeapplication,andresetsthetarget.

SeeFAQDebugging#1ifC-SPYisunabletocommunicatewiththedevice.12.ClickDebug→Gotostarttheapplication.

13.ClickDebug→StopDebuggingtostoptheapplication,toexitC-SPY,andtoreturntotheWorkbench.14.ClickFile→ExittoexittheWorkbench.

16DevelopmentFlow

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comUsingKickStart

2.2.5AdditionalProjectSettingsforUltra-Low-PowerMode(LPMx.5)Debugging

2.2.5.1

WhatisLPMx.5

LPMx.5isanultra-low-powermodeinwhichtheentryandexitishandleddifferentlythantheotherlow-powermodes.

LPMx.5givesthelowestpowerconsumptionavailableonadevice.Toachievethis,entrytoLPMx.5disablestheLDOofthePMMmodule,whichremovesthesupplyvoltagefromthecoreandtheJTAGmoduleofthedevice.Becausethesupplyvoltageisremovedfromthecore,allregistercontentsandSRAMcontentsarelost.ExitfromLPMx.5causesaBORevent,whichforcesacompleteresetofthesystem.

NOTE:Theoption\"RELEASEJTAGONGO\"iscurrentlynotsupportedintheEmbedded

WorkbenchwhenLPMx.5debuggingisactive.SeetheMSP430devicefamilyuser'sguideforadditionalLPMx.5andultra-low-powerdebugmodedetails.

2.2.5.2EnableUltra-Low-PowerDebugMode

Toenabletheultra-lowpowerdebugmodefeaturethe“EnableULP/LPMx.5debug”checkboxmustbeenabledbyclickingFETDebugger->Setup->EnableULP/LPMx.5debug(seeFigure2-4).Whentheultra-lowpowerdebugmodeisenabledanotificationisdisplayedintheDebuggerlogeverytimethetargetdeviceentersandleavesLPMx.5mode(seeFigure2-5).

PresstheHaltorResetbuttoninEmbeddedWorkbenchtowakeupthetargetdevicefromLPMx.5.Executionofthecodeishaltedatthestartoftheprogram.AllbreakpointsthathadbeenactivebeforeLPMx.5arerestoredandreactivatedautomatically.

Figure2-4.EnableUltra-Low-PowerDebugMode

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow

UsingKickStartwww.ti.com

Figure2-5.LPMx.5Notifications

2.2.6PasswordProtectionforMSP430Devices

WhendebugginganMSP430devicethatsupportsprotectionbyauserpassword,thehexadecimalJTAGpasswordmustbeprovidedtostartadebugsession.

SetJTAGpasswordbyclickingFETDebugger→Download→JTAGpassword(seeFigure2-6).

Figure2-6.JTAGPassword

2.2.7UsinganExistingIARV1.x,V2.x,orV3.xProject

ItispossibletouseanexistingprojectfromanIARV1.x,V2.x,orV3.xsystemwiththenewIARV4.xsystem;seetheIARdocumentStepbyStepMigrationforEW430x.xx.Thisdocumentisin\\EmbeddedWorkbenchx.x\\430\\doc\\migration.htm.

18DevelopmentFlow

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comUsingKickStart

2.2.8StackManagementand.xclFiles

Thereservedstacksizecanbeconfiguredthrougheithertheprojectoptionsdialog(GeneralOptions→Stack/Heap)orthroughdirectmodificationofthe.xcllinkercontrolfiles.Thesefilesareinputtothelinkerandcontainstatementsthatcontroltheallocationofdevicememory(RAM,flash).SeetheIARXLINKdocumentationforacompletedescriptionofthesefiles.The.xclfilesprovidedwiththeFET(\\EmbeddedWorkbenchx.x\\430\\config\\lnk430xxxx.xcl)definearelocatablesegment(RSEG)calledCSTACK.CSTACKisusedtodefinetheregionofRAMthatisusedforthesystemstackwithinCprograms.CSTACKcanalsobeusedinassemblerprograms(MOV.W#SFE(CSTACK),

SP).CSTACKisdefinedtoextendfromthelastlocationofRAMfor50bytes(thatis,the

stackextendsdownwardthroughRAMfor50bytes).

Otherstatementsinthe.xclfiledefineotherrelocatableregionsthatareallocatedfromthefirstlocationofRAMtothebottomofthestack.Itiscriticaltonotethat:

•Thesupplied.xclfilesreserve50bytesofRAMforthestack,whetherornotthisamountofstackisactuallyrequired(orifitissufficient).

•Thereisnoruntimecheckingofthestack.Thestackcanoverflowthe50reservedbytesandpossiblyoverwritetheothersegments.Noerrorisoutput.Thesupplied.xclfilescanbemodifiedtotunethesizeofthestacktotheneedsoftheapplication;edit-D_STACK_SIZE=xxtoallocatexxbytesforthestack.Notethatthe.xclfilealsoreserves50byesfortheheapifrequired(forexample,bymalloc()).

2.2.9HowtoGenerateTexasInstruments.TXT(andOtherFormat)Files

TheKickStartlinkercanbeconfiguredtooutputobjectsinTI.TXTformatforusewiththeGANG430andPRGS430programmers.ClickProject→Options→Linker→Output→Format→Other→msp430-txt.Intel™andMotorola™formatsalsocanbeselected.

Formoreinformation,seeFAQProgramDevelopment#6inAppendixA.

2.2.10OverviewofExamplePrograms

ExampleprogramsforMSP430devicesareprovidedin\\EmbeddedWorkbenchx.x\\430\\FET_examples.EachtoolfoldercontainsfoldersthatcontaintheassemblerandCsources.\\EmbeddedWorkbench\\x.x\\430\\FET_examples\\FlashingtheLED.ewwconvenientlyorganizestheFET_1demonstrationcodeintoaworkspace.TheworkspacecontainsassemblerandCprojectsofthecodeforeachoftheMSP430devicefamilies.DebugandReleaseversionsareprovidedforeachoftheprojects.

\\EmbeddedWorkbenchx.x\\430\\FET_examples\\contents.htmconvenientlyorganizesanddocumentstheexamples.

AdditionalcodeexamplescanbefoundontheMSP430homepageunderCodeExamples.Notethatsomeexampleprogramsrequirea32-kHzcrystalonLFXT1,andnotallFETsaresuppliedwitha32-kHzcrystal.

2.3UsingC-SPY

SeeAppendixBforadescriptionofFET-specificmenuswithinC-SPY.

2.3.1BreakpointTypes

TheC-SPYbreakpointmechanismusesalimitednumberofon-chipdebuggingresources(specifically,Nbreakpointregisters,seeTable2-1).WhenNorfewerbreakpointsareset,theapplicationrunsatfulldevicespeed(orrealtime).WhengreaterthanNbreakpointsaresetandUseVirtualBreakpointsis

enabled(FETDebugger→Breakpoints→Usevirtualbreakpoints),theapplicationrunsunderthecontrolofthehostPC;thesystemoperatesatamuchslowerspeedbutoffersunlimitedsoftwarebreakpoints(ornon-realtime).Duringnon-realtimemode,thePC,ineffect,repeatedlysinglestepsthedeviceandinterrogatesthedeviceaftereachoperationtodetermineifabreakpointhasbeenhit.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow19

UsingC-SPYwww.ti.com

Both(code)addressanddata(value)breakpointsaresupported.DatabreakpointsandrangebreakpointseachrequiretwoMSP430hardwarebreakpoints.

Table2-1.DeviceArchitecture,Breakpoints,andOtherEmulationFeatures

DeviceCC430F512xCC430F513xCC430F514xCC430F612xCC430F613xCC430F614xMSP430AFE2xxMSP430BT5190MSP430F11x1MSP430F11x2MSP430F12xMSP430F12x2MSP430F13xMSP430F14xMSP430F15xMSP430F16xMSP430F161xMSP430F20xxMSP430F21x1MSP430F21x2MSP430F22x2MSP430F22x4MSP430F23xMSP430F23x0MSP430F24xMSP430F241xMSP430F2410MSP430F261xMSP430G2xxxMSP430G22xxMSP430F41xMSP430F41x2MSP430F42xMSP430FE42xMSP430FE42x2MSP430FW42xMSP430F42x0MSP430FG42x0MSP430F43xMSP430FG43xMSP430F43x1MSP430F44x

(1)

MSP430ArchitectureMSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430MSP430Xv2MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430XMSP430MSP430XMSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430MSP430

4-WireJTAGXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

2-WireJTAG(1)

XXXXXXXX

Break-points(N)22222228222233888

RangeBreak-pointsXXXXXXX

ClockControlXXXXXXXX

StateSequencerTraceBuffer

LPMx.5DebuggingSupport

XXXXX

XXXXXXXX

XXXXX

XXXXXXXXXXXXXXXX

XXX

XXXX

22222323838

XXX

22222222228228

The2-wireJTAGdebuginterfaceisalsoreferredtoasSpy-Bi-Wire(SBW)interface.NotethatthisinterfaceissupportedonlybytheUSBemulators(eZ430-xxxxandMSP-FET430UIFUSBJTAGemulator)andtheMSP-GANG430productionprogrammingtool.TheMSP-FET430PIFparallelportJTAGemulatordoesnotsupportcommunicationin2-wireJTAGmode.

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

20DevelopmentFlow

www.ti.comUsingC-SPY

Table2-1.DeviceArchitecture,Breakpoints,andOtherEmulationFeatures(continued)

DeviceMSP430F44x1MSP430F461xMSP430FG461xMSP430F461x1MSP430F47xMSP430FG47xMSP430F47x3MSP430F47x4MSP430F471xxMSP430F51x1MSP430F51x2MSP430F52xxMSP430F530xMSP430F5310MSP430F532xMSP430F534xMSP430FxxMSP430FxxAMSP430SL38AMSP430F3xMSP430F550xMSP430F5510MSP430F552xMSP430F535xMSP430F563xMSP430F565xMSP430FR57xxMSP430FR59xxMSP430F3xMSP430F5xMSP430F663xMSP430F665xMSP430F67xxMSP430FG662xMSP430FR41xxMSP430FR58xxMSP430FR69xxMSP430i20xxMSP430L092MSP430TCH5E

MSP430ArchitectureMSP430MSP430XMSP430XMSP430XMSP430MSP430MSP430MSP430MSP430XMSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430Xv2MSP430MSP430Xv2MSP430

4-WireJTAGXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX2-WireJTAG(1)

Break-points(N)8888222283333388888833888833888838333222

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXRangeBreak-pointsXXXX

ClockControlXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

XXX

XXXX

XXXXXX

StateSequencer

XXXX

TraceBufferXXXX

LPMx.5DebuggingSupport

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow21

UsingC-SPYwww.ti.com

2.3.2UsingBreakpoints

IfC-SPYisstartedwithgreaterthanNbreakpointssetandvirtualbreakpointsaredisabled,amessageisoutputtoinformtheuserthatonlyN(realtime)breakpointsareenabled(andoneormorebreakpointsaredisabled).Notethattheworkbenchpermitsanynumberofbreakpointstobeset,regardlessoftheUseVirtualBreakpointssettingofC-SPY.Ifvirtualbreakpointsaredisabled,amaximumofNbreakpointscanbesetwithinC-SPY.

ResettingaprogramtemporarilyrequiresabreakpointifProject→Options→Debugger→Setup→RunToisenabled(seeFAQDebugging#32).

TheRunToCursoroperationtemporarilyrequiresabreakpoint.Consequently,onlyN–1breakpointscanbeactivewhenRunToCursorisusedifvirtualbreakpointsaredisabled(seeFAQDebugging#33).If,whileprocessingabreakpoint,aninterruptbecomesactive,C-SPYstopsatthefirstinstructionoftheinterruptserviceroutine(seeFAQDebugging#26).

2.3.3UsingSingleStep

Whendebugginganassemblerfile,StepOver,StepOut,andNextStatementoperatelikeStepInto;thatis,thecurrentinstructionisexecutedatfullspeed.

Whendebugginganassemblerfile,astepoperationofaCALLinstructionstopsatthefirstinstructionofthecalledfunction.

Whendebugginganassemblerfile,a(true)StepOveraCALLinstructionthatexecutesthecalledfunctionatfulldevicespeedcanbesynthesizedbyplacingabreakpointaftertheCALLandusingGO(tothebreakpointinrealtimemode).

WhendebuggingaCfile,asinglestep(Step)operationexecutesthenextCstatement.Thus,itis

possibletostepoverafunctionreference.Ifpossible,ahardwarebreakpointisplacedafterthefunctionreference,andaGOisimplicitlyexecuted.Thiscausesthefunctiontobeexecutedatfullspeed.Ifnohardwarebreakpointsareavailable,thefunctionisexecutedinnon-realtimemode.StepIntoissupported.StepOutissupported.

WithinDisassemblymode(View→Disassembly),astepoperationofanon-CALLinstructionexecutestheinstructionatfulldevicespeed.

WithinDisassemblymode(View→Disassembly),astepoperationofaCALLinstructionplaces,ifpossible,ahardwarebreakpointaftertheCALLinstruction,andthenexecutesGo.Thecalledfunctionexecutesatfulldevicespeed.IfnohardwarebreakpointisavailablepriortotheGo,thecalledfunctionisexecutedinnon-realtimemode.Ineithercase,executionstopsattheinstructionfollowingtheCALL.Itispossibletosinglesteponlywhensourcestatementsarepresent.Breakpointsmustbeusedwhenrunningcodeforwhichthereisnosourcecode(thatis,placethebreakpointaftertheCALLtothefunctionforwhichthereisnosource,andthenGotothebreakpointinrealtimemode).

If,duringasinglestepoperation,aninterruptbecomesactive,thecurrentinstructioniscompletedandC-SPYstopsatthefirstinstructionoftheinterruptserviceroutine(seeFAQDebugging#26).

22DevelopmentFlow

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comUsingC-SPY

2.3.4UsingWatchWindows

TheC-SPYWatchWindowmechanismpermitsCvariablestobemonitoredduringthedebuggingsession.Althoughnotoriginallydesignedtodoso,theWatchWindowmechanismcanbeextendedtomonitorassemblervariables.

AssumethatthevariablestowatcharedefinedinRAM,forexample:

RSEGDATA16_Ivarwordds2;twobytesperwordvarchards1;onebytepercharacter

In1.2.3.C-SPY:

OpentheWatchWindow(View→Watch).ClickDebug→QuickWatch.

Towatchvarword,enterintheExpressionbox:

(__data16unsignedint*)varword(__data16unsignedchar*)varchar

4.Towatchvarchar,enterintheExpressionbox:

5.ClicktheAddWatchbutton.6.ClosetheQuickWatchwindow.

7.ForthecreatedentryintheWatchWindow,clickonthe+symboltodisplaythecontents(orvalue)ofthewatchedvariable.Tochangetheformatofthedisplayedvariable(default,binary,octal,decimal,hex,char),selectthetype,clicktherightmousebutton,andthenselectthedesiredformat.Thevalueofthedisplayedvariablecanbechangedbyselectingit,andthenenteringthenewvalue.

InC,variablescanbewatchedbyselectingthemandthendragginganddroppingthemintotheWatchWindow.

BecausetheMSP430peripheralsarememorymapped,itispossibletoextendtheconceptofwatchingvariablestowatchingperipherals.BeawarethattheremaybesideeffectswhenperipheralsarereadandwrittenbyC-SPY(seeFAQDebugging#24).

CPUcoreregisterscanbespecifiedforwatchingbyprecedingtheirnamewith'#'(thatis,#PC,#SR,#SP,#R5,etc.).

VariableswatchedwithintheWatchWindowareupdatedonlywhenC-SPYgetscontrolofthedevice(forexample,followingabreakpointhit,asinglestep,orastoporescape).

AlthoughregisterscanbemonitoredintheWatchWindow,View→Registeristhepreferredmethod.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

DevelopmentFlow23

Chapter3

SLAU138AF–June2004–RevisedJune2014

EnergyTrace™Technology

3.1

Introduction

EnergyTrace™Technologyisanenergy-basedcodeanalysistoolthatmeasuresanddisplaystheapplication’senergyprofileandhelpstooptimizeitforultra-low-powerconsumption.

MSP430deviceswithbuilt-inEnergyTrace+[CPUState]+[PeripheralStates](orinshort

EnergyTrace++™)supportallowreal-timemonitoringofmanyinternaldevicestateswhileuserprogramcodeexecutes.EnergyTrace++technologyissupportedonselectedMSP430devicesanddebuggers.EnergyTracemode(withoutthe\"++\")isthebaseofEnergyTraceTechnologyandenablesanalogenergymeasurementtodeterminetheenergyconsumptionofanapplicationbutdoesnotcorrelateittointernaldeviceinformation.TheEnergyTracemodeisavailableforallMSP430deviceswithselecteddebuggers,includeCCS.

3.2EnergyMeasurement

DebuggerswithEnergyTraceTechnologysupportincludeanewanduniquewayofcontinuously

measuringtheenergysuppliedtoatargetmicrocontrollerthatdiffersconsiderablyfromthewell-knownmethodofamplifyingandsamplingthevoltagedropoverashuntresistoratdiscretetimes.Asoftware-controlleddc-dcconverterisusedtogeneratethetargetpowersupply.Thetimedensityofthedc-dcconverterchargepulsesequalstheenergyconsumptionofthetargetmicrocontroller.Abuilt-inon-the-flycalibrationcircuitdefinestheenergyequivalentofasingledc-dcchargepulse.

Figure3-1showstheenergymeasurementprinciple.Periodswithasmallnumberofchargepulsespertimeunitindicatelowenergyconsumptionandthuslowcurrentflow.Periodswithahighnumberofchargepulsespertimeunitindicatehighenergyconsumptionandalsoahighcurrentconsumption.EachchargepulseleadstoariseoftheoutputvoltageVOUT,whichresultsinanunavoidablevoltageripplecommontoalldc-dcconverters.

Figure3-1.PulseDensityandCurrentFlow

Thebenefitofsamplingcontinuouslyisevident:eventheshortestdeviceactivitythatconsumesenergycontributestotheoverallrecordedenergy.Noshunt-basedmeasurementsystemcanachievethis.

3.3IAREmbeddedWorkbench®forMSP430Integration

EnergyTraceTechnologyisavailableaspartofIAREmbeddedWorkbenchforMSP430microcontrollersVersion6.10.0orhigher.Duringdebuggingofanapplication,additionalwindowsareavailableifthedebugprobeandthetargetdevicesupportEnergyTraceTechnology.

3.3.1DebuggingDevicesWithEnergyTrace++TechnologySupport

DevicesthatsupportEnergyTrace++™Technologyallowsamplingofinternaldevicestateswhileanapplicationisexecuting(seeFigure3-2).

24EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

IAREmbeddedWorkbench®forMSP430Integration

Figure3-2.DebugSessionWithEnergyTrace++Windows

Beforedownloadinganddebuggingaprogram,enablethe\"EnableULP/LPMx.5debug\"option:rightclickontheproject,selecttheFETDebuggertab,andcheckthe\"EnableULP/LPMx.5debug\"option(seeFigure3-3).Ifthisoptionisnotchecked,nodigitaldatacanbecollectedfromthedevice.Analogmeasurements,however,arestillpossible.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

EnergyTrace™Technology25

IAREmbeddedWorkbench®forMSP430Integration

www.ti.com

Figure3-3.DebugOptions

ClicktheEmulatormenuforEnergyTrace++-relatedentries(seeFigure3-4).•StateLog•PowerLog•Timeline

•FunctionProfiler

26EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

IAREmbeddedWorkbench®forMSP430Integration

Figure3-4.EmulatorPulldownMenuWithEnergyTrace++-RelatedFunctions

AllEnergyTrace-relatedfunctionsneedtobeenabledfirstbyright-clickingintotherespectivewindowandselecting\"Enable\"(seeFigure3-5).

Figure3-5.EnablingtheStateLogWindow

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

EnergyTrace™Technology27

IAREmbeddedWorkbench®forMSP430Integration

www.ti.com

3.3.1.1StateLog

AllperipheralandclockactivityisgroupedunderStates.Whenaprogramexecutes,digitaldataiscollectedfromthetargetdeviceanddisplayedinlistformat(seeFigure3-6).

TheStateLogshowsatwhatpointintimeaspecificperipheralorclockhasbeenactivatedandgivesareferencetotheprogramcounterlocationwherethishappened.

Figure3-6.StateLogWindowWithEnergyTrace++Data

3.3.1.2

StateLogSummary

TheStateLogSummarywindowshowsacondensedviewoftheperipheralandclockactivityofaprofiledprogram(seeFigure3-7).Clickonthecolumnheaderstosortthedata.

Figure3-7.StateLogSummaryWithEnergyTrace++Data

3.3.1.3

PowerLogSetup

ThePowerLogSetupcanbeusedtocontroltheanalogmeasurement(seeFigure3-8).Checkeachparametertoenabledatacollection.

Figure3-8.PowerLogSetupWindow

EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

IAREmbeddedWorkbench®forMSP430Integration

3.3.1.4PowerLogWindow

SimilartotheStateLogwindow,thePowerLogwindowshowsthecurrent,voltage,andenergyprofileovertime,withreferencetotheprogramcounterthatwassampledatthegiventimestamp(seeFigure3-9).

Figure3-9.PowerLogWindowWithEnergyTrace++Data

3.3.1.5

Timeline

WheninvokingtheTimelineforthefirsttime,bothPowerLogandStategraphsaredisabled.Rightclickoneachsectiontoenableit,andusethemousewheeltozoominandout(seeFigure3-10andFigure3-11).

Figure3-10.TimelineWithPowerLogandStateGraphsDisabled

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

EnergyTrace™Technology29

IAREmbeddedWorkbench®forMSP430Integration

www.ti.com

Figure3-11.TimelineWithEnergyTrace++Data

3.3.1.6

FunctionProfiler

TheFunctionProfilergivesacondensedoverviewofthefunctionsandtheircontributiontototalruntimeandenergyconsumption(seeFigure3-12).

Figure3-12.FunctionProfilerWithEnergyTrace++Data

30EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

IAREmbeddedWorkbench®forMSP430Integration

3.3.2DebuggingDevicesWithoutEnergyTrace++TechnologySupport

DeviceswithoutEnergyTrace++TechnologysupportstillcantakeadvantageofthebaseEnergyTracetechnologyanalogmeasurements(seeFigure3-13).

Figure3-13.DebugSessionWithEnergyTraceWindows

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

EnergyTrace™Technology31

IAREmbeddedWorkbench®forMSP430Integration

www.ti.com

ClicktheEmulatormenuforEnergyTrace-relatedentries(seeFigure3-14).•PowerLog•Timeline

Figure3-14.EmulatorPulldownMenuWithEnergyTrace-RelatedFunctions

3.3.2.1

PowerLogSetup

ThePowerLogSetupcanbeusedtocontroltheanalogmeasurement(seeFigure3-15).Checkeachparametertoenabledatacollection.

Figure3-15.PowerLogSetupWindow

32EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.com

IAREmbeddedWorkbench®forMSP430Integration

3.3.2.2PowerLogWindow

SimilartotheStateLogwindow,thePowerLogwindowshowsthecurrent,voltage,andenergyprofileovertime(seeFigure3-16).

Figure3-16.PowerLogWindowWithEnergyTraceData

3.3.2.3

Timeline

WheninvokingtheTimelineforthefirsttime,thePowerLoggraphisdisabled.Rightclicktoenableit,andusethemousewheeltozoominandout(seeFigure3-17andFigure3-18).

Figure3-17.TimelineWithPowerLogGraphDisabled

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

EnergyTrace™Technology33

MeasuringLow-PowerCurrentswww.ti.com

Figure3-18.TimelineWithEnergyTraceData

3.4MeasuringLow-PowerCurrents

Duringthecaptureoftheinternalstatesorevenwhensimplyexecutinguntilbreakpointhalt,thetargetmicrocontrollerisconstantlyaccessedbytheJTAGorSpy-Bi-Wiredebuglogic.ThesedebugaccessesconsumeenergythatisincludedinthenumbersshowninthePowerLogwindowandgraph.Tomeasuretheabsolutepowerconsumptionoftheapplication,itisrecommendedtousetheEnergyTracemodeincombinationwiththeReleaseJTAGonGooption.Thiscombinationmakessurethatthedebuglogicofthetargetmicrocontrollerisnotaccessedwhilemeasuringenergyconsumption.

Figure3-19showsthecurrentconsumptionofanapplicationsleepinginLPM3,measuredwhenthedeviceisunderdebugcontrol.Thecurrentcolumnindicatesapproximately152µAcurrentconsumption,whichissignificantlyhigherthanthevaluestatedinthedevicedatasheetandismostlycausedbythecurrentconsumptionofthedevicedebuglogicforbreakpointpolling.

Figure3-19.LPM3CurrentWhenExecutingUnderDebugControl

AftercheckingtheReleaseJTAGonGooptionintheEmulatorpulldownmenu(seeFigure3-20),thedebuggerputstheJTAGorSpy-Bi-WirelinesinHi-Zstateafterlettingtheapplicationgo.

34EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comEnergyTraceTechnologyFAQs

Figure3-20.ReleaseJTAGonGoOptioninEmulatorPulldownMenu

AsshowninFigure3-21,thecurrentconsumptionforthesamecodehasreducedsignificantlytolessthan4µA.Ifthisvaluestilldeviatesconsiderablyfromthedatasheetvalue,considercheckingGPIOterminationorperipheralactivity.

Figure3-21.LPM3CurrentWhenExecutingwithJTAGSignalsReleased

3.5EnergyTraceTechnologyFAQs

Q:WhatisthesamplingfrequencyofEnergyTrace++technology?

A:Thesamplingfrequencydependsonthedebuggerandtheselecteddebugprotocolanditsspeed

setting.Ittypicallyrangesfrom1kHz(forexample,whenusingtheSpy-Bi-WireinterfacesettoSLOW)upto5kHz(forexample,whenusingtheJTAGinterfacesettoFAST).Q:MyPowergraphseemstoincludenoise.Ismyboarddefective?

A:ThepowervaluesshowninthePowergrapharederived(thatis,calculated)fromtheaccumulatedenergycountedbythemeasurementsystem.Whenthetargetisconsuminglittleenergy,asmallnumberofenergypacketsovertimearesuppliedtothetarget,andthesoftwareneedstoaccumulatethedc-dcchargepulsesovertimebeforeanewcurrentvaluecanbecalculated.Forcurrentsunder1µA,thiscantakeuptoonesecond,whileforcurrentsinthemilliamprange,acurrentcanbecalculatedeverymillisecond.Additionalfilteringisnotappliedsothatdetailinformationisnotlost.Anotherfactorthataffectstheenergy(andwithit,thecurrent)thatisconsumedbythetargetisperiodicbackgrounddebugaccessduringnormalcodeexecution,eitherthroughcapturingofStatesinformationorthroughbreakpointpolling.TryrecordinginFreeRunmodetoseeamuchsmootherPowergraph.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

EnergyTrace™Technology35

EnergyTraceTechnologyFAQswww.ti.com

Q:Ihaveacodethatrepeatedlycallsfunctionsthathavethesamesize.Iwouldexpectthefunctionprofiletoshowanequaldistributionoftheruntime.Inreality,Iseesomefunctionshavingslightlymoreruntimethanexpected,andsomefunctionsslightlyless.

A:Duringprogramcountertrace,variousfactorsaffectthenumberoftimesafunctionisdetectedbytheprofilerovertime.Themicrocontrollercodecouldbenefitfromtheinternalcache,thusexecutingsomefunctionsfasterthanothers.AnotherinfluencingfactorismemorywaitstatesandCPUpipelinestalls,whichaddtimevariancetothecodeexecution.Anoutsidefactoristhesamplingfrequencyofthe

debuggeritself,whichnormallyrunsasynchronoustothemicrocontroller'scodeexecutionspeed,butinsomecasesshowsoverlappingbehavior,whichalsoresultsinanunequalfunctionruntimedistribution.Q:MypowermodeprofilesometimesshowsshortperiodsofpowermodesthatIhaven'tusedanywhereinmycode.Forexample,I'mexpectingatransitionfromactivemodetoLPM3,butIseeaLPM2duringthetransition.

A:WhencapturinginEnergyTrace++mode,digitalinformationiscontinuouslycollectedfromthetargetdevice.Onepieceofthisinformationisthepowermodecontrolsignals.Activationoflow-powermodesrequiressteppingthroughanumberofintermediatestates.Usuallythishappenstooquicklytobe

capturedbythetracefunction,butsometimesintermediatestatescanbecapturedandaredisplayedforashortperiodoftimeasvalidlow-powermodes.

Q:Myprofilesometimesincludesanlow-powermode,andtherearegapsintheStatesgraphPowerModesection.Wheredoesthelow-powermodeoriginatefrom?

A:Duringtransitionsfromactivemodetolow-powermode,internaldeviceclocksareswitchedoff,andoccasionallythestateinformationisnotupdatedcompletely.ThisstateisdisplayedasintheProfilewindow,andtheStatesgraphshowsagapduringthetimethatthelow-powermodepersists.Thestateisanindicationthatyourapplicationhasenteredalow-powermode,butwhichmodecannotbeaccuratelydetermined.Ifyourapplicationisfrequentlyenteringlow-powermodes,thestatewillprobablybeshownmoreoftenthanifyourapplicationonlyrarelyuseslow-powermodes.

Q:Whataretheinfluencingfactorsfortheaccuracyoftheenergymeasurement?

A:TheenergymeasurementcircuitisdirectlysuppliedfromtheUSBbusvoltage,andthusitissensitivetoUSBbusvoltagevariations.Duringcalibration,theenergyequivalentofasingledc-dcchargepulseisdefined,andthisenergyequivalentdependsontheUSBvoltagelevel.Toensureagoodrepeatabilityandaccuracy,powerthedebuggerdirectlyfromanactiveUSBport,andavoidusingbus-poweredhubsandlongUSBcablesthatcanleadtovoltagedrops,especiallywhenotherconsumersareconnectedtotheUSBhub.FurthermoretheLDOandresistorsusedforreferencevoltagegenerationandthoseinthecalibrationcircuitcomewithacertaintoleranceandppmrateovertemperature,whichalsoinfluencesaccuracyoftheenergymeasurement.

Q:IamtryingtocaptureinEnergyTrace++modeorEnergyTracemodewithaMSP430devicethatisexternallypowered,butthereisnodatashownintheProfile,Energy,PowerandStateswindow.A:BothEnergyTrace++modeandEnergyTracemoderequirethetargettobesuppliedfromthedebugger.Nodatacanbecapturedwhenthetargetmicrocontrollerisexternallypowered.

Q:IcannotmeasureLPMcurrentswhenIamcapturinginEnergyTrace++mode.Iamexpectingafewmicroampsbutmeasuremorethan150µA.

A:ReadingdigitaldatafromthetargetmicrocontrollerconsumesenergyintheJTAGdomainofthemicrocontroller.Hence,anaveragecurrentofapproximately150µAismeasuredwhenconnectinganamperemetertothedevicepowersupplypins.Ifyouwanttoeliminateenergyconsumptionthroughdebugcommunication,switchtoEnergyTracemode,andletthetargetmicrocontrollerexecutewith\"ReleaseJTAGonGo\"optionchecked.

Q:MyLPMcurrentsseemtobewrong.Iamexpectingafewmicroampsbutmeasuremore,eveninFreeRunmodeorwhenlettingthedeviceexecutewithoutdebugcontrolfromanindependentpowersupply.A:ThemostlikelycauseofthisextracurrentisimproperGPIOtermination,asfloatingpinscanleadtoextracurrentflow.AlsochecktheJTAGpinsagain,especiallywhenthedebuggerisstillconnected(butidle),asthedebuggeroutputsignallevelsinidlestatemightnotmatchhowtheJTAGpinshavebeenconfiguredbytheapplicationcode.Thiscouldalsoleadtoextracurrentflow.

36EnergyTrace™Technology

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

Chapter4

SLAU138AF–June2004–RevisedJune2014

MemoryProtectionUnit(MPU)andIntellectualProperty

Encapsulation(IPE)

TheavailablememoryofanFRAM-basedmicrocontrollercanbeseenasunifiedmemory,whichmeansthememorycanbearbitrarilydividedbetweencodeanddatasections.Asaconsequence,asingleFRAM-basedmicrocontrollercanbecustomizedforawiderangeofapplicationusecases.Topreventaccidentaloverwritesoftheprogrambyapplicationdataorotherformsofdatacorruption,theMPUcanpartitiontheavailablememoryanddefineaccessrightsforeachofthepartitions.Thus,itispossibletopreventaccidentalwritestomemorysectionsthatcontainapplicationcodeortopreventthemicrocontrollerfromexecutinginstructionsthatarelocatedinthedatasectionoftheapplication.

Figure4-1.MPUConfigurationDialog

Figure4-1showstheMPUandIPEConfigurationDialogofIAREmbeddedWorkbenchthatisavailableforFRAMdevicesthathavetheMPUfeature.ItcanbeaccessedbyselectingthemenuProject→Options→GeneralOptions→MPU/IPE.AdetaileddescriptionofthepossibleconfigurationsthatareprovidedbythedialogcanbefoundintheIARC/C++CompilerUserGuide(Tenthedition:April2014).

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

MemoryProtectionUnit(MPU)andIntellectualPropertyEncapsulation(IPE)

AppendixA

SLAU138AF–June2004–RevisedJune2014

FrequentlyAskedQuestions

Thisappendixpresentssolutionstofrequentlyaskedquestionsregardingprogramhardwaredevelopmentanddebuggingtools.

Topic

Page

A.1A.2A.3

Hardware...........................................................................................................39ProgramDevelopment(Assembler,C-Compiler,Linker).........................................39Debugging(C-SPY).............................................................................................41

38FrequentlyAskedQuestions

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comHardware

A.1Hardware

Foracompletelistofhardware-relatedFAQs,seetheMSP430HardwareToolsUser'sGuide(SLAU278).

A.2ProgramDevelopment(Assembler,C-Compiler,Linker)

1.Thefilessuppliedinthe430\utorfolderworkonlywiththesimulator.DonotusethefileswiththeFET(seeFAQProgramDevelopment#11).

2.AcommonMSP430\"mistake\"istofailtodisabletheWatchdogmechanism;theWatchdogisenabledbydefault,anditresetsthedeviceifnotdisabledorproperlyhandledbytheapplication(seeFAQProgramDevelopment#14).

3.Whenaddingsourcefilestoaproject,donotaddfilesthatareincludedbysourcefilesthathavealreadybeenaddedtotheproject(forexample,an.hfilewithina.cor.s43file).Thesefilesareaddedtotheprojectfilehierarchyautomatically.

4.Inassembler,enclosingastringindoublequotes(\"string\")automaticallyappendsazerobytetothestring(asanend-of-stringmarker).Enclosingastringinsingle-quotes('string')doesnot.

5.Whenusingthecompilerortheassembler,ifthelastcharacterofasourcelineisbackslash(\\),thesubsequentcarriagereturnorlinefeedisignored(thatis,itisasifthecurrentlineandthenextlineareasingleline).Whenusedinthisway,thebackslashcharacterisa\"linecontinuation\"character.

6.Thelinkeroutputformatmustbe\"DebuginformationforC-SPY\"(.d43)forusewithC-SPY.C-SPYdoesnotstartotherwise,andanerrormessageisoutput.C-SPYcannotinputa.TXTfile.7.Position-independentcodecanbegeneratedusingProject→Options→GeneralOptions→Target→Position-IndependentCode.

8.WithintheClibraries,GIE(GlobalInterruptEnable)isdisabledbefore(andrestoredafter)thehardwaremultiplierisused.Todisablethisbehavior,contactTIforthesourcecodefortheselibraries.

9.ItispossibletomixassemblerandCprogramswithintheWorkbench.SeetheAssemblerLanguageInterfacechapteroftheC/C++CompilerReferenceGuidefromIAR.

10.TheWorkbenchcanproduceanobjectfileinTI.TXTformat.C-SPYcannotinputanobjectfileinTI.TXTformat.Anerrormessageisoutputinthiscase.

11.TheexampleprogramsgivenintheKickStartdocumentation(thatis,Demo,Tutor,etc.)arenotcorrect.Theprogramsworkonlyinthesimulator.Theprogramsdonotfunctioncorrectlyonanactualdevice,becausetheWatchdogmechanismisactive.TheprogramsneedtobemodifiedtodisabletheWatchdogmechanism.DisabletheWatchdogmechanismwiththisC-statement:

WDTCTL=WDTPW+WDTHOLD;

orwiththisassemblerstatement:

mov.w#WDTPW+WDTHOLD,&WDTCTL

12.AccesstoMPYusingan8-bitoperationisflaggedasanerror.Withinthe.hfiles,16-bitregistersaredefinedinsuchawaythat8-bitoperationsuponthemareflaggedasanerror.Thisfeatureisnormallybeneficialandcancatchregisteraccessviolations.However,inthecaseofMPY,itisalsovalidtoaccessthisregisterusing8-bitoperators.If8-bitoperatorsareusedtoaccessMPY,theaccessviolationcheckmechanismcanbedefeatedbyusing\"MPY_\"toreferencetheregister.Similarly,16-bitoperationson8-bitregistersareflagged.

13.Constantdefinitions(#define)usedwithinthe.hfilesareeffectivelyreservedandinclude,forexample,C,Z,N,andV.Donotcreateprogramvariableswiththesenames.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

FrequentlyAskedQuestions39

ProgramDevelopment(Assembler,C-Compiler,Linker)www.ti.com

14.TheCSTARTUPthatisimplicitlylinkedwithallCapplicationsdoesnotdisabletheWatchdogtimer.UseWDTCL=WDTPW+WDTHOLD;toexplicitlydisabletheWatchdog.Thisstatementisbestplacedinthe__low_level_init()functionthatgetsexecutedbeforemain().

IftheWatchdogtimerisnotdisabled,andtheWatchdogtriggersandresetsthedeviceduringCSTARTUP,thesourcescreengoesblank,asC-SPYisnotabletolocatethesourcecodeforCSTARTUP.BeawarethatCSTARTUPcantakeasignificantamountoftimetoexecuteifalargenumberofinitializedglobalvariablesareused.

int__low_level_init(void){

/*Insertyourlow-levelinitializationshere*/

WDTCTL=WDTPW+WDTHOLD;//StopWatchdogtimer/*==================================*//*Chooseifsegmentinitialization*//*shouldbedoneornot.*//*Return:0toomitseg_init*//*1torunseg_init*/

/*==================================*/return(1);}

15.Compileroptimizationcanremoveunusedvariablesandstatementsthathavenoeffectandcanaffectdebugging.Optimization:NONEissupportedwithinProject→Options→C/C++Compiler→Code→Optimizations.Alternatively,variablescanbedeclaredvolatile.

16.TheIARtutorialassumesaFullorBaselineversionoftheWorkbench.WithinaKickStartsystem,itisnotpossibletoconfiguretheCcompilertooutputassemblermnemonics.

17.ExistingprojectsfromanIAR1.xsystemcanbeusedwithinthenewIAR2.xor3.xsystem;seetheIARdocumentmigrationguideforEW430x.x.Thisdocumentislocatedin\\EmbeddedWorkbenchx.x\\430\\doc\\migration.htm

18.Assemblerprojectsmustreferencethecodesegment(RSEGCODE)tousetheLinker→

Processing→FillUnusedCodeMemorymechanism.NospecialstepsarerequiredtouseLinker→Processing→FillUnusedCodeMemorywithCprojects.

19.EnsurethattheproperCruntimelibraryisselectedforC-onlyandmixedCandassembly

languageprojects(Project→GeneralOptions→LibraryConfiguration→Library).Forassembly-onlyprojects,theruntimelibrarymustnotgetlinkedin,otherwisethebuildfailsandalinkererrorisoutput(forexample,thattheRESETvectorisallocatedtwice).

20.NumerousCandC++runtimelibrariesareprovidedwiththeWorkbench:cl430d:C,-bitdoubles

cl430dp:C,-bitdoubles,positionindependentcl430f:C,32-bitdoubles

cl430fp:C,32-bitdoubles,positionindependentdl430d:C++,-bitdoubles

dl430dp:C++,-bitdoubles,positionindependentdl430f:C++,32-bitdoubles

dl430fp:C++,32-bitdoubles,positionindependent

SeetheIARMSP430C/C++compilerreferenceguideformoreinformationonwhichlibrarytouse.

40FrequentlyAskedQuestions

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comDebugging(C-SPY)

A.3Debugging(C-SPY)

1.DebuggingwithC-SPYdoesnotseemtoaffectanexternallyconnectedMSP430device.Shouldthisbethecase,checkwhetherthemaindebuggermenubarcontainsamenuitemcalledSimulator.Ifso,anactualC-SPYMSP430coresimulatorsessionisrunning,andnoactualcommunicationwiththetargetdeviceisestablished.Solution:EnsurethattheC-SPYdriverissettoFETDebugger(Project→Options→Debugger→Setup→Driver).

2.C-SPYreportsthatitcannotcommunicatewiththedevice.Possiblesolutionstothisprobleminclude:

•Ensurethatthecorrectdebuginterfaceisselected;useProject→Options→FETDebugger→

Connection.

•Ensurethatthecorrectparallelport(LPT1,2,or3)isbeingspecifiedintheC-SPYconfigurationin

thecaseaparallelportMSP-FET430PIFinterfaceisused;useProject→Options→FET

Debugger→Connection→ParallelPort→LPT1(default)orLPT2orLPT3.CheckthePCBIOSfortheparallelportaddress(0x378,0x278,0x3BC),andtheparallelportconfiguration(ECP,Compatible,Bidirectional,orNormal)(seeFAQDebugging#8).ForusersofIBMThinkPad™

computers,tryportspecificationsLPT2andLPT3,eveniftheoperatingsystemreportstheparallelportislocatedatLPT1.

•Ensurethatthejumpersettingsareconfiguredcorrectlyonthetargethardware.

•EnsurethatnoothersoftwareapplicationhasreservedortakencontroloftheCOMorparallelport

(forexample,printerdrivers,ZIPdrivedrivers,etc.)ifaparallelportMSP-FET430PIFinterfaceisused.SuchsoftwarecanpreventtheC-SPYorFETdriverfromaccessingtheparallelportand,hence,communicatingwiththedevice.

•OpentheDeviceManageranddetermineifthedriverfortheFETtoolhasbeencorrectlyinstalled

andiftheCOMorparallelportissuccessfullyrecognizedbytheWindowsOS.

•Itmaybenecessarytorebootthecomputertocompletetheinstallationoftherequiredportdrivers.•EnsurethattheMSP430deviceissecurelyseatedinthesocket(sothatthe\"fingers\"ofthesocket

completelyengagethepinsofthedevice),andthatitspin1(indicatedwithacircularindentationonthetopsurface)alignswiththe\"1\"markonthePCB.

CAUTION

PossibleDamagetoDevice

AlwayshandleMSP430devicesusingavacuumpick-uptoolonly;donotuseyourfingers,astheycaneasilybendthedevicepinsandrenderthedeviceuseless.Also,alwaysobserveandfollowproperESDprecautions.

3.C-SPYreportsthatthedeviceJTAGsecurityfuseisblown.WithcurrentMSP-FET430PIFandMSP430-FET430UIFJTAGinterfacetoolsthereisaweaknesswhenadaptingtargetboardsthatarepoweredexternally.ThisleadstoanaccidentalfusecheckintheMSP430andresultsintheJTAGsecurityfusebeingrecognizedasblownalthoughitisnot.ThisisvalidforMSP-FET430PIFandMSP-FET430UIFbutismainlyseenonMSP-FET430UIF.Workarounds:

•ConnectthedeviceRST/NMIpintoJTAGheader(pin11),MSP-FET430PIForMSP-FET430UIF

interfacetoolsareabletopulltheRSTline,thisalsoresetsthedeviceinternalfuselogic.

•DoNOTconnectbothVCCTool(pin2)andVCCTarget(pin4)oftheJTAGheaderandalsospecify

avalueforVCCinthedebuggerthatisequaltotheexternalsupplyvoltage.

4.C-SPYcandownloaddataintoRAM,information,andflashmainmemories.Awarningmessageisoutputifanattemptismadetodownloaddataoutsideofthedevicememoryspaces.

5.C-SPYcandebugapplicationsthatutilizeinterruptsandlowpowermodes(seeFAQDebugging#26).

6.C-SPYcannotaccessthedeviceregistersandmemorywhilethedeviceisrunning.C-SPYdisplays\"-\"toindicatethataregisterormemoryfieldisinvalid.Theusermuststopthedevicetoaccessdeviceregistersandmemory.Anydisplayedregisterormemoryfieldsarethenupdated.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

FrequentlyAskedQuestions41

Debugging(C-SPY)www.ti.com

7.WhenC-SPYisstarted,theflashmemoryiserasedandtheopenedfileisprogrammedinaccordancewiththedownloadoptionsassetinProject→Options→FETDebugger→DownloadControl.ThisinitialeraseandprogramoperationscanbedisabledselectingProject→Options→FETDebugger→DownloadControl→SuppressDownload.ProgrammingoftheflashcanbeinitiatedmanuallywithEmulator→InitNewDevice.

8.Theparallelportdesignators(LPTx)havethefollowingphysicaladdresses:LPT1:378h,LPT2:278h,LPT3:3BCh.Theconfigurationoftheparallelport(ECP,Compatible,Bidirectional,Normal)isnotsignificant;ECPseemstoworkwell(seeFAQDebugging#1foradditionalhintsonsolvingcommunicationproblemsbetweenC-SPYandthedevice).

9.C-SPYmayassertRST/NMItoresetthedevicewhenC-SPYisstartedandwhenthedeviceisprogrammed.ThedeviceisalsoresetbytheC-SPYRESETbutton,andwhenthedeviceismanuallyreprogrammed(Emulator→InitNewDevice),andwhentheJTAGisresynchronized(Emulator→ResynchronizeJTAG).WhenRST/NMIisnotasserted(low),C-SPYsetsthelogicdrivingRST/NMItohigh-impedance,andRST/NMIispulledhighviaaresistoronthePCB.

RST/NMImaygetassertedandnegatedafterpowerisappliedwhenC-SPYisstarted.RST/NMImaythengetassertedandnegatedasecondtimeafterdeviceinitializationiscomplete.

WithinC-SPY,Emulator→\"Poweron\"Resetcyclesthepowertothetargettogenerateapower-onreset.

10.C-SPYcandebugadevicewhoseprogramreconfiguresthefunctionoftheRST/NMIpintoNMI.

11.TheleveloftheXOUT/TCLKpinisundefinedwhenC-SPYresetsthedevice.ThelogicdrivingXOUT/TCLKissettohigh-impedanceatallothertimes.

12.Whenmakingcurrentmeasurementsofthedevice,ensurethattheJTAGcontrolsignalsarereleased(Emulator→ReleaseJTAGonGo),otherwisethedeviceispoweredbythesignalsontheJTAGpinsandthemeasurementsareerroneous(seeFAQDebugging#14).13.MostC-SPYsettings(breakpoints,etc.)arepreservedbetweensessions.

14.WhenC-SPYhascontrolofthedevice,theCPUisON(thatis,itisnotinlow-powermode)regardlessofthesettingsofthelow-powermodebitsinthestatusregister.Anylow-powermode

conditionsarerestoredpriortoSteporGo.Consequently,donotmeasurethepowerconsumedbythedevicewhileC-SPYhascontrolofthedevice.Instead,runyourapplicationusingGowithJTAGreleased(seeFAQDebugging#12).

15.TheView→Memory→MemoryFilldialogofC-SPYrequireshexadecimalvaluesforStartingAddress,Length,andValuetobeprecededwith\"0x\".Otherwisethevaluesareinterpretedasdecimal.

16.TheMemorydebugviewofC-SPY(View→Memory)canbeusedtoviewtheRAM,theinformationmemory,andtheflashmainmemory.TheMemoryutilityofC-SPYcanbeusedtomodifytheRAM;theinformationmemoryandflashmainmemorycannotbemodifiedusingtheMemoryutility.Theinformationmemoryandflashmainmemorycanbeprogrammedonlywhenaprojectisopenedandthedataisdownloadedtothedevice,orwhenEmulator→InitNewDeviceisselected.

17.C-SPYdoesnotpermittheindividualsegmentsoftheinformationmemoryandtheflashmainmemorytobemanipulatedseparately;considertheinformationmemorytobeonecontiguousmemory,andtheflashmainmemorytobeasecondcontiguousmemory.

18.TheMemorywindowcorrectlydisplaysthecontentsofmemorywhereitispresent.However,theMemorywindowincorrectlydisplaysthecontentsofmemorywherethereisnonepresent.Memoryshouldbeusedonlyintheaddressrangesspecifiedbythedevicedatasheet.

19.C-SPYutilizesthesystemclocktocontrolthedeviceduringdebugging.Therefore,devicecounters,etc.,thatareclockedbytheMainSystemClock(MCLK)areaffectedwhenC-SPYhascontrolofthedevice.SpecialprecautionsaretakentominimizetheeffectupontheWatchdogTimer.TheCPUcoreregistersarepreserved.Allotherclocksources(SMCLK,ACLK)andperipheralscontinueto

operatenormallyduringemulation.Inotherwords,theFlashEmulationToolisapartiallyintrusivetool.

Devicesthatsupportclockcontrol(Emulator→Advanced→ClockControl)canfurtherminimizetheseeffectsbyselectingtostoptheclock(s)duringdebugging(seeFAQDebugging#24).

42FrequentlyAskedQuestions

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comDebugging(C-SPY)

20.ThereisatimeafterC-SPYperformsaresetofthedevice[whentheC-SPYsessionisfirststarted,whentheflashisreprogrammed(viaInitNewDevice),andwhenJTAGisresynchronized(ResynchronizeJTAG)]andbeforeC-SPYhasregainedcontrolofthedevicethatthedevice

executescodenormally.Thisbehaviormayhavesideeffects.OnceC-SPYhasregainedcontrolofthedevice,itperformsaresetofthedeviceandretainscontrol.

21.Whenprogrammingtheflash,donotsetabreakpointontheinstructionimmediatelyfollowingthewritetoflashoperation.Asimpleworkaroundtothislimitationistofollowthewritetoflash

operationwithaNOP,andsetabreakpointontheinstructionfollowingtheNOP(seeFAQDebugging#23).

22.TheDumpMemorylengthspecifierisrestrictedtofourhexadecimaldigits(0toFFFF).Thislimitsthenumberofbytesthatcanbewrittenfrom0to65535.Consequently,itisnotpossibletowritememoryfrom0to0xFFFFinclusive,asthiswouldrequirealengthspecifierof65536(or10000h).23.Multipleinternalmachinecyclesarerequiredtoclearandprogramtheflashmemory.Whensinglesteppingoverinstructionsthatmanipulatetheflash,controlisgivenbacktoC-SPYbeforetheseoperationsarecomplete.Consequently,C-SPYupdatesitsmemorywindowwitherroneous

information.AworkaroundtothisbehavioristofollowtheflashaccessinstructionwithaNOP,andthensteppasttheNOPbeforereviewingtheeffectsoftheflashaccessinstruction(seeFAQDebugging#21).

24.Peripheralbitsthatareclearedwhenreadduringnormalprogramexecution(thatis,interruptflags)areclearedwhenreadwhilebeingdebugged(thatis,memorydump,peripheralregisters).WhenusingcertainMSP430devices(suchasMSP430F15x,MSP430F16x,MSP430F43x,andMSP430F44xdevices),bitsdonotbehavethisway(thatis,thebitsarenotclearedbyC-SPYreadoperations).

25.C-SPYcannotbeusedtodebugprogramsthatexecuteintheRAMofMSP430F12xandMSP430F41xdevices.Aworkaroundtothislimitationistodebugprogramsinflash.

26.Whilesinglesteppingwithactiveandenabledinterrupts,itcanappearthatonlytheinterruptserviceroutine(ISR)isactive(thatis,thenon-ISRcodeneverappearstoexecute,andthesinglestepoperationalwaysstopsonthefirstlineoftheISR).However,thisbehavioriscorrectbecausethedevicealwaysprocessesanactiveandenabledinterruptbeforeprocessingnon-ISR(thatis,mainline)code.Aworkaroundforthisbehavioris,whilewithintheISR,todisabletheGIEbitonthestacksothatinterruptsaredisabledafterexitingtheISR.Thispermitsthenon-ISRcodetobedebugged(but

withoutinterrupts).InterruptscanlaterbereenabledbysettingGIEinthestatusregisterintheRegisterwindow.

Ondeviceswiththeclockcontrolemulationfeature,itmaybepossibletosuspendaclockbetweensinglestepsanddelayaninterruptrequest(Emulator→Advanced→ClockControl).

27.Thebase(decimal,hexadecimal,etc.)propertyofWatchWindowvariablesisnotpreservedbetweenC-SPYsessions;thebaserevertstoDefaultFormat.

28.OndevicesequippedwithaDataTransferController(DTC),thecompletionofadatatransfercyclepreemptsasinglestepofalow-powermodeinstruction.Thedeviceadvancesbeyondthelow-powermodeinstructiononlyafteraninterruptisprocessed.Untilaninterruptisprocessed,itappearsthatthesinglestephasnoeffect.Aworkaroundtothissituationistosetabreakpointontheinstructionfollowingthelow-powermodeinstruction,andthenexecute(Go)tothisbreakpoint.

29.ThetransferofdatabytheDataTransferController(DTC)maynotstoppreciselywhentheDTCisstoppedinresponsetoasinglesteporabreakpoint.WhentheDTCisenabledandasinglestepisperformed,oneormorebytesofdatacanbetransferred.WhentheDTCisenabledandconfiguredfortwo-blocktransfermode,theDTCmaynotstoppreciselyonablockboundarywhenstoppedinresponsetoasinglesteporabreakpoint.

30.TheC-SPYRegisterwindowsupportsinstructioncyclelengthcounters.Thecyclecounterisactiveonlywhilesinglestepping.Thecountisresetwhenthedeviceisreset,orthedeviceisrun(Go).Thecountcanbeedited(normallysettozero)atanytime.

31.ItispossibletouseC-SPYtogetcontrolofarunningdevicewhosestateisunknown.SimplyuseC-SPYtoprogramadummydevice,andthenstarttheapplicationwithReleaseJTAGonGoselected.RemovetheJTAGconnectorfromthedummydeviceandconnecttotheunknowndevice.SelectDebug→Break(ortheStophand)tostoptheunknowndevice.Thestateofthedevicecanthenbeinterrogated.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

FrequentlyAskedQuestions

Debugging(C-SPY)www.ti.com

32.ResettingaprogramtemporarilyrequiresabreakpointifProject→Options→Debugger→Setup→RunToisenabled.IfNormorebreakpointsareset,ResetsetsavirtualbreakpointandrunstotheRunTofunction.Consequently,itmayrequireasignificantamountoftimebeforetheprogramresets(thatis,stopsattheRunTofunction).DuringthistimetheC-SPYindicatesthattheprogramisrunning,andC-SPYwindowsmaybeblank(ormaynotbecorrectlyupdated).

33.RunToCursortemporarilyrequiresabreakpoint.IfNbreakpointsaresetandvirtualbreakpointsaredisabled,RunToCursorincorrectlyusesavirtualbreakpoint.Thisresultsinveryslowprogramexecution.

34.ThesimulatorisaCPUcoresimulatoronly;peripheralsarenotsimulated,andinterruptsarestatisticalevents.

35.Ondeviceswithoutdatabreakpointcapabilities,itispossibletoassociatewithaninstruction

breakpointan(arbitrarilycomplex)expressionthatC-SPYevaluateswhenthebreakpointishit.Thismechanismcanbeusedtosynthesizeadatabreakpoint.SeetheC-SPYdocumentationforadescriptionofthiscomplexbreakpointmechanism.

36.TheROMMonitorreferencedbytheC-SPYdocumentationappliesonlytoolderMSP430Exxx(EPROM)baseddevices;itcanbeignoredwhenusingtheFETandtheflash-basedMSP430Fdevices.

37.Specialfunctionregisters(SFRs)andtheperipheralregistersaredisplayedinView→Register.38.Theputchar()andgetchar()breakpointsaresetonlyifthesefunctionsarepresent(andthemechanismisenabled).Notethatputchar()andgetchar()couldbeindirectlyreferencedbyalibraryfunction.

39.Theflashprogramanddownloadprogressbardoesnotupdategradually.Thisbehavioristobeexpected.Theprogressbarupdateswhenevera\"chunk\"ofmemoryiswrittentoflash.The

developmenttoolsattempttominimizethenumberofprogramchunkstomaximizeprogrammingefficiency.Consequently,itispossible,forexample,fora60Kbyteprogramtobereducedtoasinglechunk,andtheprogressbarisnotupdateduntiltheentirewriteoperationiscomplete.

40.AftermovingacompleteEW430project(includingworkspace,project,sourceandgeneratedobjectfiles)toadifferentstoragelocation(forexample,adifferentPC)arebuildoftheobjectfiles(rebuildproject)isrequiredbeforestartingC-Spy.TheLinkerstoresabsolutepathnamesintheobjectfiles,whichprobablydonotmatchthenewstoragelocation.C-Spycanshowamessagethatthesourcefilescannotbelocatedorcanshowstrangeartifactsduringdebugging.

44FrequentlyAskedQuestions

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

AppendixB

SLAU138AF–June2004–RevisedJune2014

FET-SpecificMenus

Topic

Page

B.1

Menus...............................................................................................................46

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

FET-SpecificMenus45

Menuswww.ti.com

B.1Menus

B.1.1Emulator→DeviceInformation

Opensawindowwithinformationaboutthetargetdevicebeingused.Also,thiswindowallowsadjustingthetargetvoltageinthecaseanMSP-FET430UIFinterfaceisusedtosupplypowertothetargetbyperformingaright-clickinsidethiswindow.Thesupplyvoltagecanbeadjustedbetween1.8Vand5V.Thisvoltageisavailableonpin2ofthe14-pintargetconnectortosupplythetargetfromtheMSP-FET430UIF.Ifthetargetissuppliedexternally,theexternalsupplyvoltageshouldbeconnectedtopin4ofthetargetconnector,sotheMSP-FET430UIFcansettheleveloftheoutputsignalsaccordingly.

B.1.2Emulator→ReleaseJTAGonGo

C-SPYusesthedeviceJTAGsignalstodebugthedevice.OnsomeMSP430devices,theseJTAGsignalsaresharedwiththedeviceportpins.Normally,C-SPYmaintainsthepinsinJTAGmodesothatthedevicecanbedebugged.Duringthistimetheportfunctionalityofthesharedpinsisnotavailable.However,whenReleaseJTAGOnGoisselected,theJTAGdriversaresettothree-state,andthedeviceisreleasedfromJTAGcontrol(TESTpinissettoGND)whenGoisactivated.Anyactiveon-chipbreakpointsareretained,andthesharedJTAGportpinsreverttotheirportfunctions.

Atthistime,C-SPYhasnoaccesstothedeviceandcannotdetermineifanactivebreakpoint(ifany)hasbeenreached.C-SPYmustbemanuallycommandedtostopthedevice,atwhichtimethestateofthedeviceisdetermined(thatis,wasabreakpointreached?)(seeFAQDebugging#12).

B.1.3Emulator→ResynchronizeJTAG

Regaincontrolofthedevice.

ItisnotpossibletoResynchronizeJTAGwhilethedeviceisoperating.

B.1.4Emulator→InitNewDevice

InitializethedeviceaccordingtothesettingsintheDownloadOptions.Basically,thecurrentprogramfileisdownloadedtothedevicememory.Thedeviceisthenreset.ThisoptioncanbeusedtoprogrammultipledeviceswiththesameprogramfromwithinthesameC-SPYsession.ItisnotpossibletoselectInitNewDevicewhilethedeviceisoperating.

B.1.5Emulator→Secure-BlowJTAGFuse

Blowsthefuseonthetargetdevice.Afterthefuseisblown,nocommunicationwiththedeviceispossible.

B.1.6Emulator→BreakpointUsage

Listallusedhardwareandvirtualbreakpoints,aswellasallcurrentlydefinedEEMbreakpoints.

B.1.7Emulator→Advanced→ClockControl

DisablethespecifiedsystemclockwhileC-SPYhascontrolofthedevice(followingaStoporbreakpoint).AllsystemclocksareenabledfollowingaGoorasinglestep(SteporStepInto)(seeFAQDebugging#19).

B.1.8Emulator→Advanced→EmulationMode

Specifythedevicetobeemulated.Thedevicemustbereset(orreinitializedthroughInitNewDevice)followingachangetotheemulationmode.

46FET-SpecificMenus

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

www.ti.comMenus

B.1.9Emulator→Advanced→MemoryDump

Writethespecifieddevicememorycontentstoaspecifiedfile.Aconventionaldialogisdisplayedthatpermitstheusertospecifyafilename,amemorystartingaddress,andalength.Theaddressedmemoryisthenwritteninatextformattothenamedfile.Optionspermittheusertoselectwordorbytetextformat,andaddressinformationandregistercontentsalsocanbeappendedtothefile.

B.1.10Emulator→Advanced→BreakpointCombiner

OpentheBreakpointCombinerdialogbox.TheBreakpointCombinerdialogboxpermitsonetospecifybreakpointdependencies.Abreakpointistriggeredwhenthebreakpointsareencounteredinthespecifiedorder.

B.1.11Emulator→StateStorageControl

OpentheStateStoragedialogbox.TheStateStoragedialogboxpermitstheusertousethestate

storagemodule.TheStateStorageModuleisnotpresentonallMSP430derivatives.SeeTable2-1forimplementationdetails

SeetheIARC-SPYFETDebuggersectionintheMSP430IAREmbeddedWorkbenchIDEUserGuide.

B.1.12Emulator→StateStorageWindow

OpentheStateStoragewindow,anddisplaythestoredstateinformationasconfiguredbytheStateStoragedialog.

SeetheIARC-SPYFETDebuggersectionintheMSP430IAREmbeddedWorkbenchIDEUserGuide.

B.1.13Emulator→SequencerControl

OpentheSequencerdialogbox.TheSequencerdialogboxpermitstheusertoconfigurethesequencerstatemachine.

SeetheIARC-SPYFETDebuggersectionintheMSP430IAREmbeddedWorkbenchIDEUserGuide.

B.1.14Emulator→\"Poweron\"Reset

Cyclepowertothedevicetoeffectareset.

B.1.15Emulator→GIEon/off

Enablesordisablesallinterrupts.NeedstoberestoredmanuallybeforeGo.

B.1.16Emulator→LeaveTargetRunning

IfC-SPYisclosed,thetargetkeepsrunningtheuserprogram.

B.1.17Emulator→ForceSingleStepping

OnGotheprogramisexecutedbysinglesteps.Thecyclecounterworkscorrectlyonlyinthismode.

NOTE:

AvailabilityofEmulator→Advancedmenus

NotallEmulator→AdvancedmenusaresupportedbyallMSP430devices.Thesemenusaregrayedout.

SLAU138AF–June2004–RevisedJune2014SubmitDocumentationFeedback

FET-SpecificMenus47

RevisionHistorywww.ti.com

RevisionHistory

ChangesfromAERevision(May2014)toAFRevisionPage••

ChangedcontentsofSection2.2.5....................................................................................................17AddedChapter3........................................................................................................................24

48RevisionHistory

SLAU138AF–June2004–RevisedJune2014

SubmitDocumentationFeedback

IMPORTANTNOTICE

TexasInstrumentsIncorporatedanditssubsidiaries(TI)reservetherighttomakecorrections,enhancements,improvementsandotherchangestoitssemiconductorproductsandservicesperJESD46,latestissue,andtodiscontinueanyproductorserviceperJESD48,latestissue.Buyersshouldobtainthelatestrelevantinformationbeforeplacingordersandshouldverifythatsuchinformationiscurrentandcomplete.Allsemiconductorproducts(alsoreferredtohereinas“components”)aresoldsubjecttoTI’stermsandconditionsofsalesuppliedatthetimeoforderacknowledgment.

TIwarrantsperformanceofitscomponentstothespecificationsapplicableatthetimeofsale,inaccordancewiththewarrantyinTI’stermsandconditionsofsaleofsemiconductorproducts.TestingandotherqualitycontroltechniquesareusedtotheextentTIdeemsnecessarytosupportthiswarranty.Exceptwheremandatedbyapplicablelaw,testingofallparametersofeachcomponentisnotnecessarilyperformed.

TIassumesnoliabilityforapplicationsassistanceorthedesignofBuyers’products.BuyersareresponsiblefortheirproductsandapplicationsusingTIcomponents.TominimizetherisksassociatedwithBuyers’productsandapplications,Buyersshouldprovideadequatedesignandoperatingsafeguards.

TIdoesnotwarrantorrepresentthatanylicense,eitherexpressorimplied,isgrantedunderanypatentright,copyright,maskworkright,orotherintellectualpropertyrightrelatingtoanycombination,machine,orprocessinwhichTIcomponentsorservicesareused.InformationpublishedbyTIregardingthird-partyproductsorservicesdoesnotconstitutealicensetousesuchproductsorservicesorawarrantyorendorsementthereof.Useofsuchinformationmayrequirealicensefromathirdpartyunderthepatentsorotherintellectualpropertyofthethirdparty,oralicensefromTIunderthepatentsorotherintellectualpropertyofTI.

ReproductionofsignificantportionsofTIinformationinTIdatabooksordatasheetsispermissibleonlyifreproductioniswithoutalterationandisaccompaniedbyallassociatedwarranties,conditions,limitations,andnotices.TIisnotresponsibleorliableforsuchaltereddocumentation.Informationofthirdpartiesmaybesubjecttoadditionalrestrictions.

ResaleofTIcomponentsorserviceswithstatementsdifferentfromorbeyondtheparametersstatedbyTIforthatcomponentorservicevoidsallexpressandanyimpliedwarrantiesfortheassociatedTIcomponentorserviceandisanunfairanddeceptivebusinesspractice.TIisnotresponsibleorliableforanysuchstatements.

Buyeracknowledgesandagreesthatitissolelyresponsibleforcompliancewithalllegal,regulatoryandsafety-relatedrequirements

concerningitsproducts,andanyuseofTIcomponentsinitsapplications,notwithstandinganyapplications-relatedinformationorsupportthatmaybeprovidedbyTI.Buyerrepresentsandagreesthatithasallthenecessaryexpertisetocreateandimplementsafeguardswhichanticipatedangerousconsequencesoffailures,monitorfailuresandtheirconsequences,lessenthelikelihoodoffailuresthatmightcauseharmandtakeappropriateremedialactions.BuyerwillfullyindemnifyTIanditsrepresentativesagainstanydamagesarisingoutoftheuseofanyTIcomponentsinsafety-criticalapplications.

Insomecases,TIcomponentsmaybepromotedspecificallytofacilitatesafety-relatedapplications.Withsuchcomponents,TI’sgoalistohelpenablecustomerstodesignandcreatetheirownend-productsolutionsthatmeetapplicablefunctionalsafetystandardsandrequirements.Nonetheless,suchcomponentsaresubjecttotheseterms.

NoTIcomponentsareauthorizedforuseinFDAClassIII(orsimilarlife-criticalmedicalequipment)unlessauthorizedofficersofthepartieshaveexecutedaspecialagreementspecificallygoverningsuchuse.

OnlythoseTIcomponentswhichTIhasspecificallydesignatedasmilitarygradeor“enhancedplastic”aredesignedandintendedforuseinmilitary/aerospaceapplicationsorenvironments.BuyeracknowledgesandagreesthatanymilitaryoraerospaceuseofTIcomponentswhichhavenotbeensodesignatedissolelyattheBuyer'srisk,andthatBuyerissolelyresponsibleforcompliancewithalllegalandregulatoryrequirementsinconnectionwithsuchuse.

TIhasspecificallydesignatedcertaincomponentsasmeetingISO/TS16949requirements,mainlyforautomotiveuse.Inanycaseofuseofnon-designatedproducts,TIwillnotberesponsibleforanyfailuretomeetISO/TS16949.ProductsAudioAmplifiersDataConvertersDLP®ProductsDSP

ClocksandTimersInterfaceLogicPowerMgmtMicrocontrollersRFID

OMAPApplicationsProcessorsWirelessConnectivity

www.ti.com/audioamplifier.ti.comdataconverter.ti.comwww.dlp.comdsp.ti.comwww.ti.com/clocksinterface.ti.comlogic.ti.compower.ti.commicrocontroller.ti.comwww.ti-rfid.comwww.ti.com/omap

TIE2ECommunity

e2e.ti.com

www.ti.com/wirelessconnectivity

MailingAddress:TexasInstruments,PostOfficeBox655303,Dallas,Texas75265

Applications

AutomotiveandTransportationCommunicationsandTelecomComputersandPeripheralsConsumerElectronicsEnergyandLightingIndustrialMedicalSecurity

Space,AvionicsandDefenseVideoandImaging

www.ti.com/automotivewww.ti.com/communicationswww.ti.com/computerswww.ti.com/consumer-appswww.ti.com/energywww.ti.com/industrialwww.ti.com/medicalwww.ti.com/security

www.ti.com/space-avionics-defensewww.ti.com/video

因篇幅问题不能全部显示，请点此查看更多更全内容

查看全文