zigbee专区套件ti cc2530评估模块swru197g

CCDebuggerUser’sGuideTableof Abbreviationsand Box OperatingConditionsoftheCC Initial InstallingtheUSB SupportedPC ConnectingtheCCDebuggertothe TargetConnector ConnectingtheCCDebuggertoaSystemon Minimumconnectionfor MinimumconnectionforSmartRF MinimumconnectionforSmartRFPacket ConnectingtheCCDebuggertoa ConnectingtheCCDebuggertoa UsingtheCC Updatingthe UpdatingthefirmwareautomaticallyinSmartRF UpdatingthefirmwaremanuallyinSmartRFFlash dbootrecovery ResurrectingtheCC TheCCDebuggerisprimarilyusedforflashprogramminganddebuggingsoftwarerunningonCCxxxx8051-basedSystem-on-Chip(SoC)devicesfromTexasInstruments.ThePCtoolsavailableforthesepurposesaretheSmartRF™FlashProgrammer[9]fromTexasInstrumentsandIAREmbeddedWorkbench®for8051fromIARSystems[15].Whenconnectedtothedebugger,theSoCdevicescanbecontrolleddirectlyfromSmartRF™Studio[8].SmartRFStudiowillalsobeabletocontrolsupportedCCxxxxRFtransceivers(CC2520,CC2500,CC110x,CC11xL,CC112x,CC120x)whentheyareconnectedtothedebuggerasexinedinchapterInaddition,CCDebuggerisusedforconfiguringtheCC85xxdeviceswithPurePathWirelessConfigurator[12]andcontrollingthemwithPurePathWirelessCommander[13].Abbreviationsand ChipSelect(active Debug Debug DeviceUnder LightEmitting MasterInSlave MasterOutSlave Radio Serial Systemon PositivevoltageonBox1xCC1xUSB-AtoMini-BUSB1x10-pinflatcablewith2x52.54mm1x10-pinflatcablewith2x51.27mm1xConverterboard2.54mm–1.27mmOperatingConditionsoftheCCMinimumtarget 1.2umtargetvoltage: 3.6VoltOperatingtemperature: RegulatedvoltageonCCDebugger: 3.3Voltumtargetcurrent 200mA WindowsXPSP2/SP3(32bitversions)WindowsVista® (32&64bit)Windows7 (*)OnlyapplicableifthetargetispoweredfromtheCCDebuggerFigure1-CCDebuggerconnectedtoaSoCBatteryBoardwithaInitialInstallingtheUSBTogettherequiredUSBdriverfortheCCDebugger,itisnecessarytoinstalloneofthetoolslistedSmartRF rtrftm-SmartRFFlash sh-SmartRFPacket ket- epath-wl- epath-wl-Alternatively,youcandownload“Cebal–CCxxxxDevelopmentToolsUSBDriverforWindowsx86andx64”[4]whichisastandaloneinstallerincludingonlythedevicedriver.Afterhavinginstalledthedriver,connecttheCCDebuggertothePC.TheUSBdriverwillbeinstalledautomatically.YoucanquicklycheckthatthedebuggerhasbeenassociatedcorrectlywiththeUSBdevicedriverbyopeningtheWindowsDeviceManager.Thedebuggershouldappearasa“Cebalcontrolleddevice”.Figure2-VerifycorrectdriverForfurtherdetailsortroubleshootingthedriverinstallationprocess,pleasereferto“DN304–CCxxxxDevelopmentToolsUSBDriverInstallationGuide”[5].SupportedPCCurrently,theCCDebuggercanbeusedtogetherwiththefollowingPCIAREmbeddedWorkbenchfor Incircuitdebuggingofsystem-on-SmartRFFlash SmartRF RFtestingofradiodevices(transceiversandSmartRFPacket Packetsniffingwithselectedradio ProgrammingofCC85xx AdvancedcontrolofCC85xxThedebuggerwilloperateastheinterfacebetweentheRFdeviceandthetoolslistedabove.PleaseensurecorrectconnectionbetweenthedeviceandCCDebuggerbeforestartingtousethetools.TheconnectionofthedevicetotheCCDebuggerwillbecoveredinthenextConnectingtheCCDebuggertotheTargetConnectorThetargetconnector,locatedonthelalsideofthedebugger,isa10-pin2x52.54mmpitchconnectorwithadirectioncodedsticguide.Suggestedmatching(male)surfacemountedheaderswouldbe95278-101A10LFfromFCIorBB02-HPfromGradConn.PinPinFigure3-cementofTargetConnectorTheadapterboard,whichhasa10-pin2x51.27mmpitchconnector,hasthesamepincement.Suggestedmatching(male)surfacemountedheaderswouldbe -000-10C4LFfromFCIorFTS-105-01-F-DVfromSamtec.PinPinFigure4 cementofTargetConnectorPinsonAdapterThepin-outofthetargetconnectorisshowninFigure5.Notethatnotallofthesepinsneedtobeconnectedtothetargetdeviceforprogramminganddebugging.OnlyVdd,GND,DD,DCandRESETarerequiredforSystemonChips.Theotherpinsareoptionaland/orforspecialfeatures.DC(DebugClock)CSn(SPIChip3.3V(from

DD(DebugData)SCLK(SPIClock)MOSI(SPIDataOut)MISO(SPIDataIn)Figure5-TargetConnectorPin-Pleasenotetheconceptwiththetargetvoltagesensesignal.ThissignalisusedbythelevelconvertersontheCCDebuggertohandledifferentvoltagelevelsonthetargetboardandthedebugger.Pin2onthetargetconnectormustbeconnectedtoVddonthetargetboard.CCCCVddFigure6-VoltagefromtargettoCCAlternatively,itispossibletopowerthetargetbyconnectingpin9toVddonthetarget.Inthatcase,theCCDebuggerwillsupply3.3Vtothetarget.ConnectingtheCCDebuggertoaSystemonMinimumconnectionforForsuccessfuldebuggingofaTI8051-basedRFSystemonChip,connectthetwodebugsignalsDebugData(DD)andDebugClock(DC)andtheresetsignalRESETntothedevice.NotethatDDisabidirectionalsignal.Inaddition,theCCDebuggermustbeconnectedtoGNDandVddontheboard.VddisusedasaninputtothelevelshiftersontheCCDebugger,thusallowingadifferentoperatingvoltageonthetargetthaninternallyonthedebugger.ForCC111x,CC251x,CC243x,CC253xandCC254x,exceptCC2544andCC2545,connecttheDDsignaltopinP2.1andDCtopinP2.2.ForCC2544,connecttheDDsignaltoP1.3andDCtoP1.2.ForCC2545,connecttheDDsignaltoP1.3andDCtoNotethatitispossibletopowerthetargetboardfromthedebuggerbyconnectingthe3.3Vsignalonpin9ontheconnectortothetargetboard.NOTENOTE

1010

DD(Debug

optionallybeusedtopowerthetargetboard

2.7NOTE

11

Figure7-Minimumconnectionfordebuggingof8051Note1:SomeearlyrevisionsofcertainSoCs(CC2430,CC2510andCC1110)neededanexternalpull-uptoavoidunwantedtransitionsonthedebugclocklineduringchipreset–thusinadvertentlysettingthedeviceindebugmode.AllnewrevisionsofallSoCsnowhaveaninternalpull-uponP2.2,sothisexternalcomponentisnotrequired.Note2:TheRESETnpinissensitivetonoiseandcancauseunintendedresetofthechip.Forresetlinessusceptibletonoise,itis mendedtoaddanexternalRCfilter.PleaserefertotherespectiveSoCdatasheetandreferencedesignsfor mendedRESETcircuitry.TheCCDebuggersupportsslowtransitionsontheresetline,usinga2msdelaybetweenanytransitionontheRESETlineandothertransitionsontheDCand/orDDlines.MinimumconnectionforSmartRFUsethesameconnectionasfordebuggingtheMinimumconnectionforSmartRFPacketInordertousethepacketsniffercapabilitiesoftheCCDebugger,itisalsonecessarytoconnecttheSPIbustotheSoC.TheSPIinterfaceisusedbytheCCDebuggerforreadingthecapturedRFpacketsfromtheSoC.

optionallybeusedtopowerthetargetboard

DD(Debug

2.7

11

Figure8-ConnectiontoSoCtoenablePacketNotethatthepacketsnifferwilloverwritetheflashontheSoCwithspecialpacketcapturefirmware.NoteconcerningtheSPIinterfacetotheSoCusedforpacketsniffingAllofthecurrentTIRFSoCscanbeconfiguredtooperateasSPIslaves,withtheSPIsignals(CS,SCLK,MISOandMOSI)goingtooneoftheUSARTperipherals.ThepacketsnifferapplicationwillprogramtheSoCwithfirmwarethatconfiguresoneoftheUSARTperipheralsinordertocommunicatewiththeCCDebugger.Thefirmwarecanuseanyofthefourpossiblepinconfigurations(USART0or1,pinoutalternative1or2).However,onlyasubsetiscurrentlysupported:USART0,altUSART0,altUSART1,altUSART1,altTable1-SupportedSPIconnections(markedUSART0,altUSART1,altTable2-USARTpinoutIncaseofmultiplesupportedinterfaces,thePacketSnifferapplicationwillletyouchoosewhichinterfacetouse.ConnectingtheCCDebuggertoaTheSPIinterfaceontheCCDebuggercanbeusedtointerfacemanyoftheCCxxxxtransceiversandcontrolthemfromSmartRFStudio.Thetransceivers/transmitters/receiverscurrentlysupportedare:NotethattheCCDebuggeroperatesastheSPIMaster.Inamultimastersystem,itisnecessarytomakesurethedebuggeroutputsignals(DC,DD,CSn,SCLK,MOSIandRESETn)donotinterferewiththeotherSPImasterontheboard.TheotherSPImasterwouldtypicallybethemicrocontrollerontheTheconnectiondiagramsbelowshowtheinterconnectionbetweenthedebuggerandthevarioussupportedtransceivers.

optionallybeusedtopowerthetargetboard

Figure9-CCDebuggerconnectedto

135

246

optionallybeusedtopowerthetargetboard

7

Figure10-CCDebuggerconnectedto

135

246

optionallybeusedtopowerthetargetboard

Figure11-CCDebuggerconnectedtoConnectingtheCCDebuggertoaInordertoconfiguretheCC85xxdevices(gramtheflashonthedevice)withPurePathWirelessConfigurator,thedevice’sSPIinterfacemustbeconnectedtotheCCDebuggerasshowninthefigure

optionallybeusedtopowerthetargetboard

Figure12-CCDebuggerconnectedtoUsingtheCCAfterhavingconnectedthedebuggertothetargetdevice,thedebuggercanbepoweredupbypluggingintheUSBcable.Thedebuggerwillimmedia ystartadevicedetectionprocess,lookingforallknowndevices.Ifnodevicesaredetected,theLEDwillbeRED.Ifadeviceisdetected,theLEDwillbeGREEN.IftheLEDisGREEN,itispossibletostartusingthedebuggertogetherwithoneofthesupportedPCUnderstandingtheTheThedebuggerhasnopowerorthereisnovalidfirmwareonthedebugger.MakesurethedebuggerisproperlypoweredviatheUSBcableortrytoresurrectthedebuggerusingthemethoddescribedinchapter8.4.Thedebuggerispowered,Thedebuggerispowered,butthereisnovalidfirmware.Trytoresurrectthedebuggerusingthemethoddescribedinchapter8.4.REDLED

TheDebuggerisinBootRecoveryThedebuggerwillbrieflyenterthisstatewhilethefirmwareisbeingupgraded(seechapter8).Theboardmightalsoenterthisstateifthefirmwareiscorruptoriftheuserhasmanuallydtoboardtostartupinthespecial“bootrecoverymode”(section8.3).Togooutofthestate,resetthedebuggerbypressingthe“Reset”buttonorbypower-cyclingthedevice.IftheLEDisstillblinking,reprogramtheunitbyusingtheFlashProgrammerApplication.Nodevicedetected.Nodevicedetected.ThismightbeduetooldfirmwareontheCCDebugger.Newdevicesmightnotbesupportedwiththecurrentfirmwareonthedebugger.Pleaserefertochapter8forthefirmwareupgradeprocedure.Theremightalsobeaproblemwiththehardwareconnection.ChecktheconnectiontodeviceandmakesurethetargetboardisproperlypoweredandthatVddonthetargetboardisconnectedtopin2onthedebugconnector.PressandreleasetheresetbuttontoretrythetargetdeviceThetargetdeviceThetargetdevicehasbeenproperlydetected.Itispossibletostartusingthesupportedtools(seechapter5.2).UpdatingtheInordertomakesuretheCCDebuggerworksseamlesslywithyourdevice,itisimportantthatithasthelatestandgreatestfirmware.ThischapterwilldescribehowyoucanupgradethefirmwareautomaticallyfromSmartRFStudioormanuallyfromSmartRFFlashProgrammer.Thechapterwillalsodescribehowtoresurrectaseeminglybrokendebugger.UpdatingthefirmwareautomaticallyinSmartRFUpdatingthefirmwareontheCCDebuggercanbedoneautomaticallybySmartRFStudio.Pleasefollowthefewstepsdescribedbelow.StartSmartRFDisconnectthedebuggerfromanytargetboard,andconnectittothePCviatheUSBcable.ThedebuggerwillappearinthelistofconnecteddevicesinthelowerpartoftheSmartRFStudiostartuppanel.Figure13-AutoFWDoubleclickontheiteminthelist,andanewwindowwillFigure14-AutoFWClick"Yes"andletSmartRFStudiodotheFigure15-AutoFWClick"Done"andyou'regoodtogo.Thedeviceshouldappearinthelistofconnecteddevices,nowshowingthenewfirmwarerevision.UpdatingthefirmwaremanuallyinSmartRFFlashYoucanalsoupdatethefirmwaremanuallyusingSmartRFFlashProgrammer.Youcanusethismethodifyouliketohavefullcontrolofthefirmwareimagetobeprogrammedonthecontrollerofthedebugger(grammingcustomfirmwareoroldfirmwarerevisions).StartSmartRFFlashProgrammerandselectthetabcalled“EBapplication(USB)”.ThistabwillletyouprogramcompatiblefirmwareontheCCDebugger(orevaluationboards)viatheUSBinterface(i.e.noexternalprogrammingdevicerequired).Disconnectthedebuggerfromanytargetboard,andconnectittothePCviatheUSBcable.Thedebuggerwillappearinthelistofconnecteddevices.ChiptypewillbelistedasN/A.Selecttheflashimageyouwanttoprogramonthedebugger.Normally,youwouldselect:C:\ProgramFiles(x86)\TexasInstruments\SmartRFTools\Firmware\CCSelecttheaction“Erase,programandClickthe“Performactions”buttons.Theprogrammingprocedurewillstart.Notethatthiswilltakeseveralseconds.TheCCDebuggerwillreappearinthelistofconnecteddevices,nowshowingthenewfirmwarerevisioninthedevicelist.1123451AssumingdefaultinstallationpathofSmartRFFlashdbootrecoveryIf,forsomereason,thefirmwareupdatefailsandtheCCDebuggerappearstobenonresponsive,thereisawaytotheboardtoonlyrunthebootloaderandstopallfurtherexecution.Inthismode,noattemptswillbemadetostartthefirmware,andtheboardwillonlyallowtheusertoperformanewfirmwareupgradeoverUSB.DisconnectthedebuggerfromanypowersourceandopenthesticFigure16-InternalviewofCCShortcircuitthepinsasdepictedinFigure17:P1.6ontheCC2511mustbeconnectedtoGNDduringthepower-onresettoenterbootrecoverymode.Figure17-Short-circuitpinsforbootrecoveryWhenreconnectingtheUSBcable,theLEDwillstarttoblinkwithaREDlight.Thisindicatesthatthebootloaderisrunningandthatthedebuggerisinbootrecoverymode.Atthispoint,followthesamefirmwareprogrammingstepsasdescribeatthebeginningofthisPleasealsonotethatthebootrecoverymodecanbeusedasachecktoverifythatthebootloaderonthedebuggerisworking.ResurrectingtheCCIftheCCDebuggerappearstobecompleydeadwhenapplyingpower,thereisawayto“unbrick”theboard.Themethodconsistsofreprogrammingthebootloaderonthedebuggerusingthedebugconnectorinsidethebox.Thiswillrequireanextraprogrammingdevice.Whenopeningthebox,locatethedebugconnectorheadernexttothetargetconnector.ConnectthisheadertoanotherCCDebugger(seeFigure18)ortoaSmartRF05EB(seeFigure19).WhenusingSmartRF05EB,connecta10-pinflatcablefromthe“ExtSoCDebug”plug(P3)ontheEBtothe“USBDebug”plug(P2)ontheCCDebugger.Thedeaddebuggerneedspower,soconnecttheUSBcable.TurnontheSmartRF05EBordebugger-itshoulddetecttheUSBController(CC2511)onthedebugger.Figure18-ProgrammingthebootloaderontheCCDebuggerusinganotherCCFigure19-ProgrammingthebootloaderontheCCDebuggerusingNext,usetheSmartRFFlashProgrammertoprogramthebootloaderonthedebugger.Followthesefivesteps(illustratedinFigure20below):Afterstartingtheapplication,firstselect“ProgramEvaluationBoard”inthe“Whatdoyouwanttoprogram?”dropdownbox,thenselectthe“EBBootloader”tab.Intheupperleftcorner,selectdevice:UseSmartRF05EBregardlessofthedevicebeingusedtoprogramthedebugger.I.e.selectSmartRF05EBbothwhenyouareusingaCCDebuggerandwhenyouareusingaSmartRF05EBfortheresurrection.Next,selectwhichflashimagetoprogram.Thebootloaderimageisincludedwheninstallingtheflashprogrammeranditisusuallylocatedat“C:\ProgramFiles(x86)\TexasInstruments\SmartRFTools\Firmware\CCDebugger”.ItisalsonecessarytogivethedebuggerauniqueIDnumber–any4digitnumberwillwork.ThisnumberisusedbythedriveronthePCtouniquelyidentifydevicesifmorethanonedebuggerisconnectedatthesametime.Select“Erase,programandPressthe“PerformActions”buttons.Thefirmwareupgradetakesafew1123546Figure20-SmartRFFlashProgrammer-UpdatingtheOncethebootloaderisprogrammed,youmightbeaskedtoinstallaUSBdriveronthePC.JustfollowthesameprocedureaswhenthedebuggerwasconnectedtothePCthefirsttime(seechapter5).TheREDLEDonthedebuggershouldnowbeblinking,indicatingthatthebootloaderisrunningbutthatnoapplicationhasbeenloaded.IftheREDLEDisoff,thereisprobablysomethingwrongwiththehardware.ThedebuggerfirmwarecannowbeprogrammeddirectlyoverUSBbyfollowingtheprocedureineitherchapter8.1or8.2. Help!ThedebuggerdoesnotdetecttheSoC.WhatshouldI ThereareseveralthingstoUpgradethefirmware.ManyCCDebuggershaveoldfirmwarethatwillnotautomaticallydetectnewerdevices,likeCC2543/44/45.Refertochapter8forfurtherinstructions.Checkthatthecableisorientedcorrectlyandthatthepinsareconnectedtotherightsignalsonthedebugger.Checkthatthedebuggergetspowerfromthetarget(i.eproperconnectionoftheTargetVoltageSensesignal).Thisisrequiredinorderforthelevelconvertersonthedebuggertowork.Checkthatgroundonthetargetisconnectedtogroundonthedebugger.Thisisnormallyachievedthroughthetargetconnector.Notethatsincethegroundnesarethesame,pleasebeawareofanyadverseeffectscausedbydifferentgroundnesonthetargetandonthePC(groundedviaUSBcable).Checkthatthecableisnotbroken.Especiallythesmallflatcableispronetostopworkingifhandledalotorbeingbentandstretchedbeyondnormaloperatingconditions. DoesIAREW8051supporttheCCDebuggerasdebuggingA2Yes–butmakesureyouhaveanuptodateversionofIARwiththenewdebugdriverplug-infromTexasInstruments.Youwillneedversion7.51Aorhigher. CanthedebuggerbeusedasaninterfacetotheRFdeviceforpacketA3Yes,thisissupportedforselecteddevices.Usethesameinterconnectionasinthediagramsinchapter6. IsthereawaytoremovethesticcasingwithoutdamagingA4Yes,thereis.Holdthebottompieceofthesticinonehand.Withyourotherhand,takeafirmgriponthelonglalsidesoftheupperpartofthesticandsqueezewhilemovingtheupperpartawayfromthebottom.Thetwopartsshouldseparatefromeachother.Toreassemblethestic,justclickthetwopieces IsthisaMinioraMicroUSB MiniUSBtypeQ6IhavetwoCCDebuggerswiththesameEBID,andI’munabletousethemtogether.WhatdoIdo? TwoEBswiththesameEBIDcauseadriver .ThesolutionistoresurrectoneoftheCCDebuggersandgiveitanewEBID.ConnectoneCCDebuggertoyourConnecttheCCDebuggeryouwanttoresurrecttoaseparatepowersource(e.g.anothercomputeroraUSBcharger).FollowthestepsforresurrectingtheCCDebugger,describedinsectionSeelastpageorrefertothecompletebundleincludinggerberfiles,schematicsandlayouthereCebal–CCxxxxDevelopmentToolsUSBDriverforWindowsx86andx64DN304–CCxxxxDevelopmentToolsUSBDriverInstallationTexasInstrumentsLowPowerRFOnlineSmartRFSmartRFFlashSmartRFPacketSmartRFFlashProgrammerUserPurePathWirelessPurePathWirelessSoCBatteryBoardproductwebIAREmbeddedWorkbenchfor12G2013-01-Chapter9:AddedhowtosolveproblemwithCCDebuggershavingthesameEBF2013-06-CC1100,CC1101,CC2500,andCC1200arenowalsosupportedbythedebugger.Correctedtypoinchapter6.2.1:DDtopinP2.1(notP2.2)andDCtopinP2.2(notP2.1)forallSoCsexceptCC2544andCC2545.Addeddebugpin-outforCC2545.Correctedpin-outinfigure10and11(DCtoGPIO2/GDO2,DDtoGPIO0/GDO0).Addedlinktolayoutandgerberfiles.E2012-03-Correctedtypoinchapter6.2.1.Specialdebugpin-outforCC2544,notD2012-02-AddedinformationaboutconnectionsforprogrammingofCC85xxdevices.Updatedinfoaboutconnectionsforsupportedtransceivers.Updateddriverinstallationinformationandaddedmoredetailsaboutfirmwareupgrade.DescribewhatitmeanswhentheLEDisamber.Updatedreferencelinks.C2010-09-AddedmoreinformationabouthowtoupgradetheB2010-02-FixederroneousdescriptionofinterconnectionbetweenCCDebuggerandCC2520.TheVREG_ENsignalshallbeconnectedtopin4onthetargetconnector,notpinA2010-02-Addedmoredetailsaboutthepoweringoptions.Addedmoreinformationaboutconnectionoptions.-2009-05-First Debug LEVEL DC.UART DD.DBG.

SP!.EN

毋DBG.J毋DBG.J

明含明含启"。气oDBG.USQugQUlQoDebugDebug

吕口i

T：

器EVALUATIONBOARD/KIT/MODULE(EVM)ADDITIONALTexasInstruments(TI)providestheenclosedEvaluationBoard/Kit/Module(EVM)underthefollowingTheuserassumesallresponsibilityandliabilityforproperandsafehandlingofthegoods.Further,theuserindemnifiesTIfromallclaimsarisingfromthehandlingoruseofthegoods.Shouldthisevaluationboard/kitnotmeetthespecificationsindicatedintheUser’sGuide,theboard/kitmaybereturnedwithin30daysfromthedateofdeliveryforafullrefund.THEFOREGOINGLIMITEDWARRANTYISTHEEXCLUSIVEWARRANTYMADEBYSELLERTOBUYERANDISINLIEUOFALLOTHERWARRANTIES,EXPRESSED,IMPLIED,ORSTATUTORY,INCLUDINGANYWARRANTYOFMERCHANTABILITYORFITNESSFORANYPARTICULARPURPOSE.EXCEPTTOTHEEXTENTOFTHEINDEMNITYSETFORTHABOVE,NEITHERPARTYSHALLBELIABLETOTHEOTHERFORANYINDIRECT,SPECIAL,AL,ORCONSEQUENTIALPleasereadtheUser'sGuideand,specifically,theWarningsandRestrictionsnoticeintheUser'sGuidepriortohandlingtheproduct.Thisnoticecontainsimportantsafetyinformationabouttemperaturesandvoltages.ForadditionalinformationonTI'senvironmentaland/orsafetyprograms,pleasevisit orcontactTI.NolicenseisgrantedunderanypatentrightorotherinlectualpropertyrightofTIcoveringorrelatingtoanymachine,process,orcombinationinwhichsuchTIproductsorservicesmightbeorareused.TIcurrentlydealswithavarietyofcustomersforproducts,andthereforeourarrangementwiththeuserisnotexclusive.TIassumesnoliabilityforapplicationsassistance,customerproductdesign,softwareperformance,orinfringementofpatentsorservicesdescrbedherein.AsnotedintheEVMUser’sGuideand/orEVMitself,thisEVMand/or panyinghardwaremayormaynotbesubjecttotheFederalCommunicationsCommission(FCC)andIndustryCanada(IC)rules.ForEVMsnotsubjecttotheaboverules,thisevaluationboard/kit/moduleisintendedforuseforENGINEERINGDEVELOPMENT,DEMONSTRATIONOREVALUATIONPURPOSESONLYandisnotconsideredbyTItobeafinishedendproductfitforgeneralconsumeruse.Itgenerates,uses,andcanradiateradiofrequencyenergyandhasnotbeentestedforcompliancewiththelimitsofcomputingdevicespursuanttopart15ofFCCorICES-003rules,whicharedesignedtoprovidereasonableprotectionagainstradiofrequencyinterference.Operationoftheequipmentmaycauseinterferencewithradiocommunications,inwhichcasetheuserathisownexpensewillberequiredtotakewhatevermeasuresmayberequiredtocorrectthisinterference.GeneralStatementforEVMsincludingaUserPower/FrequencyUseObligations:Thisradioisintendedfordevelopment/professionaluseonlyinlegallyallocatedfrequencyandpowerlimits.Anyuseofradiofrequenciesand/orpoweravailabilityofthisEVManditsdevelopmentapplication(s)mustcomplywithlocal erningradiospectrumallocationandpowerlimitsforthisevaluationmodule.Itistheuser’ssoleresponsibilitytoonlyoperatethisradioinlegallyacceptablefrequencyspaceandwithinlegallymandatedpowerlimitations.AnyexceptionstothisarestrictlyprohibitedandunauthorizedbyTexasInstrumentsunlessuserhasobtainedappropriateexperimental/developmentlicensesfromlocalregulatory,whichisresponsibilityofuserincludingitsacceptableauthorization.ForEVMsannotatedasFCC–FEDERALCOMMUNICATIONSCOMMISSIONPart15CompliantThisdevicecomplieswithpart15oftheFCCRules.Operationissubjecttothefollowingtwoconditions:(1)Thisdevicemaynotcauseharmfulinterference,and(2)thisdevicemustacceptanyinterferencereceived,includinginterferencethatmaycauseundesiredoperation.Changesormodificationsnotexpresslyapprovedbythepartyresponsibleforcompliancecouldvoidtheuser'sauthoritytooperatetheFCCInterferenceStatementforClassAEVMThisequipmenthasbeentestedandfoundtocomplywiththelimitsforaClassAdigitaldevice,pursuanttopart15oftheFCCRules.Theselimitsaredesignedtoprovidereasonableprotectionagainstharmfulinterferencewhentheequipmentisoperatedinacommercialenvironment.Thisequipmentgenerates,uses,andcanradiateradiofrequencyenergyand,ifnotinstalledandusedinaccordancewiththeinstructionmanual,maycauseharmfulinterferencetoradiocommunications.Operationofthisequipmentinaresidentialareaislikelytocauseharmfulinterferenceinwhichcasetheuserwillberequiredtocorrecttheinterferenceathisownexpense.FCCInterferenceStatementforClassBEVMThisequipmenthasbeentestedandfoundtocomplywiththelimitsforaClassBdigitaldevice,pursuanttopart15oftheFCCRules.Theselimitsaredesignedtoprovidereasonableprotectionagainstharmfulinterferenceinaresidentialinstallation.Thisequipmentgenerates,usesandcanradiateradiofrequencyenergyand,ifnotinstalledandusedinaccordancewiththeinstructions,maycauseharmfulinterferencetoradiocommunications.However,thereisnoguaranteethatinterferencewillnotoccurinaparticularinstallation.Ifthisequipmentdoescauseharmfulinterferencetoradioorevisionreception,whichcanbedeterminedbyturningtheequipmentoffandon,theuserisencouragedtotrytocorrecttheinterferencebyoneormoreofthefollowingmeasures:ReorientorrelocatethereceivingIncreasetheseparationbetweentheequipmentandConnecttheequipmentintoanoutletonacircuitdifferentfromthattowhichthereceiverisConsultthedealeroranexperiencedradio/TVtechnicianforForEVMsannotatedasIC–INDUSTRYCANADAThisClassAorBdigitalapparatuscomplieswithCanadianICES-Changesormodificationsnotexpresslyapprovedbythepartyresponsibleforcompliancecouldvoidtheuser’sauthoritytooperatetheConcerningEVMsincludingradioThisdevicecomplieswithIndustryCanadalicence-exemptRSSstandard(s).Operationissubjecttothefollowingtwoconditions:(1)thisdevicemaynotcauseinterference,and(2)thisdevicemustacceptanyinterference,includinginterferencethatmaycauseundesiredoperationofthedevice.ConcerningEVMsincludingdetachableUnderIndustryCanadaregulations,thisradiotransmittermayonlyoperateusinganantennaofatypeand um(orlesser)gainapprovedforthetransmitterbyIndustryCanada.Toreducepotentialradiointerferencetootherusers,theantennatypeanditsgainshouldbesochosenthattheequivalentisotropicallyradiatedpower(e.i.r.p.)isnotmorethanthatnecessaryforsuccessfulcommunication.ThisradiotransmitterhasbeenapprovedbyIndustryCanadatooperatewiththeantennatypeslistedintheuserguidewiththeumpermissiblegainandrequiredantennaimpedanceforeachantennatypeindicated.Antennatypesnotincludedinthislist,havingagaingreaterthanthe umgainindicatedforthattype,arestrictlyprohibitedfor