
SM3E Data Sheet #:
TM054
Page 26 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
Master/Slave Configuration–Apairofdevicesareinterconnectedbycross-couplingtheirrespectiveM/S Outputs or
Output1totheotherdevice’sM/S REFinput(SeeFigure8).Additionally,thereferenceinputsforeachdevicewouldtypicallybe
correspondinglythesame,sothatwhenaMaster/Slaveswitchoccurs,synchronizationwouldcontinuewiththesamereference.The
referencesmaybedrivenbythesamesignaldirectlyorviaseparatedrivers,astheredundancyofthatpartofthesystemrequires.
Distributionpathlengthsarenotcriticalhere,asaphasebuild-outwilloccurwhenadeviceswitchesfromslavetomaster.
ThepathlengthsofthetwoM/SOutputto
M/S REFsignalsisofinterest,however.Theyneednotbethesame.However,to
accommodatepathlengthdelays,theSM3Eprovidesaprogrammablephaseskewfeature,whichallowstheapplicationtooffsetthe
outputclockfromthecross-referencesignalby-32nsto+31.75ns.Thisoffsetmaythereforebeprogrammedtoexactlycompensate
fortheactualpathlengthdelayassociatedwiththeparticularapplication’scross-referencetraces.Theoffsetmaybefurtheradjusted
toaccommodateanyoutputclockdistributionpathdelaydifferences.PhaseoffsetisprogrammedbywritingtothePhase_Offset
register,andistypicallyaone-timedeviceinitializationfunction.(SeeregisterdescriptionandRegisterAccessControlsections).Thus,
master/slaveswitcheswiththeSM3Edevicesmaybeaccomplishedwithnear-zerophasehits.
ForapplicationsthatuseHardwareControlonly(i.e.phaseoffsetprogrammingisnotavailable),itisdesirabletokeepthecross
couplepathlengthsataminimumandrelativelyequalinlength,asthepathlengthwillappearasaphasehitintheslaveclockoutput
whenamaster/slaveswitchoccursinaHardwareControlconfiguration.
Master/Slave Operation and Control–TheMaster/Slavestateisalwaysmanuallycontrolledbytheapplication.Masterorslave
stateofadeviceisdeterminedbythe
MASTER SELECT pin.Choosingthemaster/slavestatesisafunctionoftheapplication,based
ontheconfigurationoftherestofthesystemandpotentialdetectedfaultconditions.
Master/slaveswitchesshouldbeperformedwithminimaldelaybetweenswitchingthestatesofeachofthetwodevices.Thiscan
beeasilyaccomplished,forexample,bycontrollingthemaster/slavestatewithasinglesignal,coupledtooneofthedevicesthrough
aninverter.WhileperformingMaster/Slaveswitches,onehastomakesurethatbothmodulesarenotinslavemode.Thiscreatesa
“TimingLoop”thatcancauseundesirableeffects.
InthecaseofRegisterAccessAutomaticControlmode,wherereferenceselectionisautomatic,itisnecessarytoreadthe
operationalmodeBITS3-0)fromthemaster’s
Op_Moderegisterandwriteittotheslave’sOp_Moderegister.Themaster’sreference
selectionwillthenbeusedbytheslavewhenitbecomesmaster.Inadditiontohavingthereferencespopulatedthesame,andinthe
sameorderforbothdevices,itisdesireabletowritethereferencefrequencyandpriorityregisters
Ref(1-8)_Frq_Priorityandthe
Ref_Maskregisterstothesamevaluesforbothdevicestoensureseamlessmaster/slaveswitches.
Reset–Deviceresetisaninitializationtimefunction,whichresetsinternallogicandregistervalues.Aresetisperformed
automaticallywhenthedeviceispoweredup.Registersreturntotheirdefaultvalues,asnotedintheregisterdescriptions.Device
modeandfunctionalityfollowingaresetaredeterminedbythestateofthevarioushardwarecontrolpins.
Holdover History Accumulation and Maintenance -- Holdoverhistoryaccumulationandmaintenancemaybecontrolledin
greaterdetailifregisterbusaccesstothedeviceisprovided.Holdoverhistoryaccumulationandcontrolencompassesthreedevice
internalregisters,threebusaccessregistersforcontrolandaccess,andtwostatusbitsintheDPLL_Statusregister.
Oncelockhasbeenachieved,holdoverhistoryiscompiledintheaccumulationregister.ItistransferredtotheActiveholdoverhistory
whenitisready(typicallyinabout15minutes).The“HoldoverAvailable”bitandoutputpinaresetto“1”.Fromthenon,theActive
holdoverhistoryiscontinuallyupdatedandkeptinsyncwiththeholdoverhistoryaccumulationregister.(SeeFigure11).
Hold Over History
Accumulation Register
Active
Hold Over History
Backup
Hold Over History