SM3E Data Sheet #:
TM054
Page 28 of 36 Rev: 04 Date: 01/26/11
Copyright 2011 The Connor-Winfield Corp. All Rights Reserved
Specifications subject to change without notice
Application Notes continued
Boundary Scan IEEE1149.1-2001 (Limited Testability Support) - Thismoduleexposesaboundaryscanchainwhichcontains
oneormoreboundaryscantestableIEEE1149.1-2001complaintdevices.TheexposedboundaryscanchainisIEEE1149.1-2001
compliant,andsupportsalldocumentedtestingmodesofdevicescontainedwithinchain.Integrationofthismoduleintoanexisting
boundaryscanchainwillrequirethefollowing.
-Substitutionofmodulesfootprintwithprovidedtestabilitymodelschematic.
-Modifiednetlistwillneedtobeloadedintoboundaryscantestvectorgenerationsoftware.
TestabilityModelSchematicandBSDLfile(s)canbeobtaineddirectlyfromfactory.
Control Modes
Thedevicemustbeoperatedinamanualcontrolmode,orautomaticcontrolandreferenceselectionmode.
Reset maybepulledlowforaminimumof10mSduringchipstart-up(oranyotherdesiredtime)toinitializethefulldevicestate.
TheBITSclockoutputfrequencyisselectedbythe
T1/E1pin.WhenT1/E1=1,theBITSfrequencyis1.544MHz,andwhen
T1/E1=0,theBITSfrequencyis2.048MHz.
MASTER SELECT-Determinesthemasterorslavemode.Setto“1”foramaster,and“0”foraslave.Master/slaveswitches
shouldbeperformedwithminimaldelaybetweenswitchingthestatesofeachofthetwodevices.Thiscanbeeasilyaccomplished,for
example,bycontrollingthemaster/slavestatewithasinglesignal,coupledtooneofthedevicesthroughaninverter.
Forsimplexoperation,thedeviceshouldbeinMastermode-set
MASTER SELECTto“1”.
Holdover History Accumulation and Maintenance continued –Wheneverholdoverisentered,itistheActiveHoldoverHistory
thatisusedtodeterminetheholdoverfrequency.TheHistory_Cmdregisterallowstheapplicationtoissuethreeholdoverhistory
controlcommands:
1)SavetheActiveHoldoverHistorytotheBackupHistory.
2)RestoreaBackupHistorytotheActive.
3)FlushtheactiveHistoryaswellastheaccumulationregister.TheBackuphistoryremainsintact.
BoththeActiveandtheBackupholdoverhistoriesareloadedwiththecalibratedfreerunsynthesizercontroldataonreset/power-up.
Theapplicationmightusethe“savetobackup”inasituationwhere,forexample,theprimaryreferenceisknowntobeofhigher
qualitythananysecondaryreferences,inwhichcaseitmaybedesirabletosaveandthenrestoretheholdoverhistoryaccumulated
ontheprimaryreferenceiftheprimaryreferenceislostandholdoverisentereduponlossofasecondaryreference.Userscanrestore
thehistoryfrombackupanytime,evenwhileoperatinginHoldovermode.Thefrequencytransientwillbesmoothandcontinuous.
Itistheresponsibilityofapplicationsoftwaretokeeptrackoftheageandviabilityoftheholdoverbackuphistory.Giventimeand
temperatureeffectsonoscillatoraging,theapplicationmaywishtoperiodicallyperforma“Save”oftheActivehistorytokeepthe
backupcurrent.
Whenswitchingtoanewreference,theactiveholdoverhistorywillremainintactandmarkedas“HoldoverAvailable”(ifitwas
availablebeforethereferenceswitch)untilanewhistoryisaccumulatedonthenewreference(Typically15minutesafterlockhas
beenachieved).Duringthenewhistoryaccumulation,the“HoldoverBuildComplete”bitisreset.Oncethenewhistoryaccumulationis
complete,itistransferredtotheActiveHistoryandthe“HoldoverBuildComplete”bitisset.Theactivehistorywillthencontinuetobe
updatedtotrackthereference.
TheHistory_Policyregisterallowstheapplicationtocontrolhowanewhistoryisbuilt.Whensetto“Rebuild”:
1)Historyaccumulationbeginswhenlockisachievedonthenewreference.
2)Theholdoverhistoryisrebuilt(takingabout15minutes).TheActiveHistoryremainsuntoucheduntilitisreplacedwhenthebuild
iscomplete.
Whenthepolicyissetto“Continue”:
1)Ifthereisno“Available”ActiveHistory,anewbuildoccurs,asunderthe“Rebuild”policy.
2)Ifthereisan“Available”ActiveHistory,itwillcontinue,theaccumulationregisterwillbeloadedfromthe
ActiveHistory,andthe“Build”processisessentiallycompletedimmediatelyfollowinglockonthenewreference.
The“Continue”policymaybeusedbytheapplicationif,forexample,itisknownthatthereferenceswitchedtomaybetracedtothe
samesourceandthereforelikelyhasnofrequencyoffsetfromthepriorreference.Inthatcase,the“Continue”policyavoidsthedelay
ofrebuildingtheholdoverhistory.Iftheswitchislikelytobebetweenreferenceswithknownorunknownfrequencyoffset,thenitis
preferabletousethe“Rebuild”policy.
ThetimesincetheholdoverstatewasenteredmaybereadfromtheHoldover_Timeregister.Valuesarefrom0to255hours,
limitedat255,andresetto0whennotintheholdoverstate.