Example: air traffic controller

MSP Debuggers User's Guide (Rev. L) - ti.com

1 SLAU647L July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggersUser's GuideSLAU647L July 2015 RevisedFebruary2018 MSPD ebuggersThismanualdescribesthe use and the featuresof the debugprobesfor MSP430 and SimpleLink MSP432 microcontrollers(MCUs).It includesinformationaboutthe documentsfrequentlyaskedquestionson how to enableand showsthe differencesbetweenthe debugprobesand offersa guideon how to identifythe specificversionof of ,Schematic(1 of 6)..2217 MSP-FETUSBD ebugger,Schematic(2 of 6)..2318 MSP-FETUSBD ebugger,Schematic(3 of 6)..2419 MSP-FETUSBD ebugger,Schematic(4 of 6)..2520 MSP-FETUSBD ebugger,Schematic(5 of 6)..2621 MSP-FETUSBD ebugger,Schematic(6 of 6).. and Top and ,Schematic(1 of 4)..3326 MSP-FET430 UIFUSBI nterface,Schematic(2 of 4).

SLAU647L–July 2015–Revised February 2018 1 Submit Documentation Feedback Copyright © 2015–2018, Texas Instruments Incorporated MSP Debuggers

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Advertisement

Transcription of MSP Debuggers User's Guide (Rev. L) - ti.com

1 1 SLAU647L July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggersUser's GuideSLAU647L July 2015 RevisedFebruary2018 MSPD ebuggersThismanualdescribesthe use and the featuresof the debugprobesfor MSP430 and SimpleLink MSP432 microcontrollers(MCUs).It includesinformationaboutthe documentsfrequentlyaskedquestionson how to enableand showsthe differencesbetweenthe debugprobesand offersa guideon how to identifythe specificversionof of ,Schematic(1 of 6)..2217 MSP-FETUSBD ebugger,Schematic(2 of 6)..2318 MSP-FETUSBD ebugger,Schematic(3 of 6)..2419 MSP-FETUSBD ebugger,Schematic(4 of 6)..2520 MSP-FETUSBD ebugger,Schematic(5 of 6)..2621 MSP-FETUSBD ebugger,Schematic(6 of 6).. and Top and ,Schematic(1 of 4)..3326 MSP-FET430 UIFUSBI nterface,Schematic(2 of 4).

2 3427 MSP-FET430 UIFUSBI nterface,Schematic(3 of 4)..3528 MSP-FET430 UIFUSBI nterface,Schematic(4 of 4).. July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggers29 MSP-FET430 UIFUSBI nterface, eZ-FETLite (TopView).. (TopView)..3832eZ-FETor eZ-FETLite LaunchPadDevelopmentKit Pin (USBC onnection)..4236eZ-FETS chematic(EmulationMCU)..4337eZ-FETS chematicDCDC(No eZ-FETLite).. (EmulationMCU)..4741eZ430 Schematic(USBC onnection).. InterfaceModule, InterfaceModule, of Tables1 DebugProbesFeaturesand eZ-FETLite eZ-FETLite eZ-FETLite Pin ,SimpleLink,MSP432,CodeComposerStudio,E2 E,EnergyTraceare trademarksof X is a registeredtrademarkof Apple, is a registeredtrademarkof Arm a trademarkof EmbeddedWorkbenchis a registeredtrademarkof IAR a registeredtrademarkof a registeredtrademarkof a trademarkof Red Hat, othertrademarksare the propertyof July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018, HardwareToolsUser's GuideIAR EmbeddedWorkbenchVersionv7+ for MSP430 User's GuideAdvancedDebuggingUsingthe EnhancedEmulationModule(EEM)WithCodeComp oserStudio Version6 MSP430 FlashDeviceBootloader(BSL)

3 User's GuideMSP430 ProgrammingWiththe AbbreviationsTermDefinitionBSLB ootloaderCCSCodeComposerStudio developmenttool for MSP430 CDCC ommunicationsdeviceclassCPUC entralprocessingunitCRCC yclicredundancycheckCTSC learto sendFETF lashemulationtoolI2 CInter-IntegratedCircuit2-wirecommunicat ionbusIAR EW430 IAR EmbeddedWorkbench developmenttool for MSP430 JTAGJ ointTestActionGroupJTAG4-wire4-wireJTAG protocolcommunicationMCLKM asterclockMSPM ixedsignalprocessorMSP-FETMSP debugprobeMSP-FET430 UIFMSP debugprobeMSPD ebugStackDynamiclibrary(Windows ), sharedobject(Linux ), or dy library(OS X ) that offersfunctionsto accessanddebugMSP430devicesusingan MSPdebugprobePCPersonalcomputerRTSR equestto sendRXReceivedataSBWSpy-Bi-Wire(2-wireJT AG protocol)communicationTXTransmitdataUART U niversalasynchronousreceiver/transmitter UIFUSB interfaceto debugand You NeedAssistanceSupportfor the MSPmicrocontrollersand the developmenttoolsis providedby the TI ProductInformationCenter(PIC).

4 Contactinformationfor the PIC can be foundon the TI website. The TI E2E Communitysupportforumsfor the MSPmicrocontrollersalso provideopeninteractionand supportfroma communityof peerengineers,TI engineers,and be foundonthe July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggers2 MSPD ebugProbeOverviewTable1 is an overviewof the capabilitiesand featuresfor the JTAGor emulatorUSBcableduringan runningdebugsessionproperly,by clickingon the"Terminate"icon,beforedisconnectingth e targetdevice.(1)The MSP-FET430 PIFis for emulationtool doesnot supportany devicesreleasedafter2011.(2)See to identifythe hardware.(3)The eZ-FETE mulationIP and eZ-FETLite EmulationIP are usedas the onboardemulationfor the MSPL aunchPadtools.(4)See for moreinformation.

5 (5)The 2-wireJTAG debuginterfaceis also referredto as Spy-Bi-Wire(SBW) DebugProbesFeaturesand DeviceCompatibility(1)(2)(3)Featureand MSP430 DeviceSupporteZ430-F2013eZ430-RF2500eZ43 0-RF2480eZ430-RF2560 MSP-WDSxxMetawatcheZ430-ChronosLaunchPad (MSP-EXP430G2)MSP-EXP430FR5739 MSP-EXP430F5529 MSP-FET430 PIFMSP-FET430 UIFMSP-FETeZ-FETE mulationIPeZ-FETLite EmulationIPSupportsall programmableMSP430andCC430devices Supportsonly F20xx,G2x01,G2x11,G2x21,G2x31 SupportsF20xx,F21x2,F22xx,G2x01,G2x11,G2 x21,G2x31,G2x53 SupportsF20xx,F21x2,F22xx,G2x01,G2x11,G2 x21,G2x31 SupportsF5438,F5438A SupportsBT5190,F5438A Supportsonly F552x SupportsFR57xx,F5638,F6638 Supportsonly CC430F613x SupportsMSP432 Pxx AllowsJTAG accessprotection(FuseBlow)(4) Adjustabletargetsupplyvoltage 4-wireJTAG 2-wireJTAG(5) BSL tool or mode BackchannelUART Supportedby CCSfor Windows Supportedby CCSfor Linux Supportedby CCSfor OS X July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggersTable1.

6 DebugProbesFeaturesand DeviceCompatibility(1)(2)(3)(continued)F eatureand MSP430 DeviceSupporteZ430-F2013eZ430-RF2500eZ43 0-RF2480eZ430-RF2560 MSP-WDSxxMetawatcheZ430-ChronosLaunchPad (MSP-EXP430G2)MSP-EXP430FR5739 MSP-EXP430F5529 MSP-FET430 PIFMSP-FET430 UIFMSP-FETeZ-FETE mulationIPeZ-FETLite EmulationIPSupportedby IAR EnergyTrace , EnergyTrace++ firmwareupdatemay fail whenusinga ,do not connectthrougha USBhub whileupdatingthe firmwareon the July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018, DetermineIf YourHardwareis Basedon eZ-FETor eZ-FETLite Checkthe installedtool driversby usingthe "MSPD ebugInterface"and CDC"MSPA pplicationUART1"devices(seeFigure1). Checkthe ExperimenterBoardor LaunchPademulationsectionto find out if it is basedon an eZ-FETtool. If it is basedon an MSP430F5528device,it is an eZ-FETtool.

7 Thereis a smallprinton the silkscreenthat indicateseZ-FETor eZ-FETLite (seeFigure2 andFigure3).Figure1. eZ-FETW indowsEnumerationFigure2. eZ-FETE mulationIPFigure3. eZ-FETLite July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018, DetermineIf YourHardwareis Basedon eZ430 Checkthe installedtool driversby usingthe WindowsDeviceManager(seeFigure5). eZ430toolsenumerateas HID (Debuggerport)and CDC(BackchannelUART)devices. Checkthe ExperimenterBoardto find out if it is basedon an eZ430tool (seeFigure4). If it is basedon an MSP430F1612and a TUSB3410,it is an eZ430 EmulationIPFigure5. In-SystemProgrammingand DebuggingFor detailsaboutthe hardwareconnectionsof all debugprobessee the "SignalConnectionsfor In-SystemProgrammingand Debugging"sectionof theMSP430 HardwareToolsUser's PowerSupplyFeatureof the eZ-FETand eZ-FETLiteThe eZ-FETand the eZ-FETLite only supporta maximumsupplycurrentis 75 mA.

8 For moredetails,see the specificLaunchPador experimenterboarduser' :Thesedebugprobesdo not supportexternallypoweringof the devicewhiledebugging ifan externalvoltageis neededfor stand-alonetesting,the eZ-FETemulationsectionshouldnot be bothexternalpowerand the USBpowerare connected,therecouldbe a conflictthat can damagethe PowerSupplyFeatureof the MSP-FET430 UIFand MSP-FETAll MSPdebugprobescan supplytargetswith up to 100 mA throughpin 2 of the :The targetshouldnot consumemorethan60 mA at peakcurrent,as it may violatethe foundon :If the targetboardhas a capacitoron the VCCline with a capacityof morethan10 F, it maycausean inrushcurrentduringcapacitorchargingthat may exceed60 mA. In this case,the currentshouldbe limitedby the designof the targetboard,or an externalpowersupplyshouldbe July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggersTargetVCCis selectablein a V and V in stepsof ,the targetcan be this case,the externalvoltageshouldbe connectedto pin 4 of the levelof the JTAG signalstoautomaticallymatchthe :Onlypin 2 (MSP-FETtool suppliestarget)or pin 4 (targetis externallysupplied) not supportedat the an externalsupplypowersthe targetdeviceon the targetsocketmoduleand anyusercircuitryconnectedto the targetsocketmodule,the MSP-FETtool continuesto bepoweredfromthe PC throughthe :MSP-FET430 PIFonlyThe PC parallelportswith a connectedMSP-FET430 PIFcan sourcea maximumcurrentof25 mA.

9 Becauseof the ultra-low-powerrequirementof the MSP430,a stand-aloneMSP430doesnot exceedthe ,if additionalcircuitsare added,the currentlimit couldbe this case,the MSP430mustbe sectiondescribeshow to installthe driversfor all driversare neededtoenablethe IDE (integrateddevelopmentenvironment)to use the debugprobethat is connectedto four differentwaysto installthe CCSdesktop:Duringthe CCSsetup,all MSPdebugprobedriversare installedfor all CCScloud:The automaticdriverinstalleris includedin the TI CloudAgentapplication,whichmustbedownloa dedwhenconnectinga localMSPdebugprobeto Stand-alonedriverinstaller:The stand-alonedriverinstalleris availableonly for UsinganothersupportedIDE suchas IAR EW430or the MSP-Flasher:Duringthe setup,all MSPdebugprobedriversare MSP-FET430 PIFhas the followingsystemrequirements:It supportsonly WindowsXP with IAR developmentis scheduledto installthe hardwarefor the MSP-FET430 PIFtool:1.

10 Use the 25-pinribboncableto connectthe debuggerinterfacemoduleto the parallelport of the necessarydriverfor accessingthe PC parallelport is installedautomaticallyduringCCSor a restartis requiredafterthe CCSor IAR Use the 14-pinribboncableto connectthe parallel-portdebuginterfaceto a targetboardwhichcontainsthe ,MSP-FET,eZ-FET,and eZ-FETLiteNOTE:The built-inDC-DCconverterof the MSP-FETand eZ-FETemulatorscausesa load-dependentamountof rippleon the outputvoltage(fripple= 1 kHz to 50 kHz,Vrms_ripple= 5 mV to50 mV),whichmightaffectsensitiveanalogand RF circuitsthat are suppliedby suchsensitivecircuits,TI recommendstemporarilyincreasingthe amountofpowersupplydecouplingusedduringd evelopment,usingan emulatorwith an integratedlinearregulator(MSP-FET430 UIFor eZ-FET430),or usinga July 2015 RevisedFebruary2018 SubmitDocumentationFeedbackCopyright 2015 2018,TexasInstrumentsIncorporatedMSPD ebuggersInstallationstepsfor the MSP-FET430 UIF,MSP-FET,eZ-FETor eZ-FETLite:1.


Related search queries