AnsweredAssumed Answered

HMC7044 Debugging

Question asked by Phil.G on Feb 13, 2018

Hi,

 

Background:

I was using an OCXO as a reference to the HMC7044 in my system for initial debugging and driver testing.  Things were working very well.  I am now using a recovered clock from an Aurora link as my reference to the HMC7044.  This clock is not as clean so we have been trying to optimize the PLL1 to accomodate it.

 

Question:

I am trying to use the alarms and status information from the HMC7044 as a guide in creating a stable system, but am unclear as to exactly what some of the information is telling me or how to use it to guide my debugging.  Could you please explain the following register outputs?

 

======================HMC7044==================================
HMC7044: Addr = 070, Value = FF, Binary:1111 1111
HMC7044: Addr = 071, Value = 1F, Binary:0001 1111
HMC7044: Addr = 078, Value = 01, Binary:0000 0001
HMC7044: Addr = 079, Value = 52, Binary:0101 0010
HMC7044: Addr = 07A, Value = 04, Binary:0000 0100
HMC7044: Addr = 07B, Value = 01, Binary:0000 0001
HMC7044: Addr = 07C, Value = A0, Binary:1010 0000
HMC7044: Addr = 07D, Value = 0D, Binary:0000 1101
HMC7044: Addr = 07E, Value = 71, Binary:0111 0001 <- LOS on CLKIN0 since last clear event... NOT GOOD
HMC7044: Addr = 082, Value = 02, Binary:0000 0010
HMC7044: Addr = 083, Value = 4C, Binary:0100 1100
HMC7044: Addr = 084, Value = 4C, Binary:0100 1100
HMC7044: Addr = 085, Value = 04, Binary:0000 0100 <- Indicates that the reference appears to run faster than the VCXO. What does this mean?
HMC7044: Addr = 086, Value = 03, Binary:0000 0011 <- Weird since these bits are reserved.
HMC7044: Addr = 08C, Value = 0B, Binary:0000 1011
HMC7044: Addr = 08D, Value = 02, Binary:0000 0010 <- PLL2 Autotune Signed Error(LSB), 2. Is this bad? What does it imply?
HMC7044: Addr = 08E, Value = 00, Binary:0000 0000
HMC7044: Addr = 08F, Value = 00, Binary:0000 0000
HMC7044: Addr = 091, Value = 02, Binary:0000 0010

 

Thanks for the help.

 

BR,

Phil

Outcomes