This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LMH1983: TRS error

Part Number: LMH1983


Dear Technical Support Team,

When this revision was changed to H, some register specifications were changed.

I have two questions about it.

Q1)
Regarding the initialization method, please explain in detail the reset time, release time, register setting values, and order of the initialization process that starts after the device is powered on or reset and released.

Q2)
The following is a list of the problem events. Is there any difference between FVH and STC?

■ Defect occurrence
The SDI signal of the board violates the standard.
TRS error occurs in the measurement device.

When temperature cycle test is performed, error occurs in a specific temperature band, although the value differs for each board.
Errors occur in a specific temperature band (temperature dependent).
(The error does not occur outside the specified temperature bandwidth.)
 Occurs only on the 3G system (148M) (1080/59p)
 Does not occur on HD system (74M) (1080/59i)
Only occurs during GENLOCK

■Outline of Internal Operation
CLKOUT3 of LMH1983 is input as REFCLK of high-speed serial in FPGA.
It is PLLed inside the FPGA and its CLK is used in each block.
 
There are two input patterns to the LMH1983
(1).Input 27M to Hin (STC)
(2) FVH signal input to Hin, Vin, and Fin (at genlock)

(2) Problem occurs only when GENLOCK is selected.

    No problem occurs in case (1) STC.

■Check when a problem occurs
・The LMH1983 lock signal is locked
・Switching from GENLOCK to STC eliminates the problem.
・Check that there is no disturbance in the CLKOUT waveform using an oscilloscope.

Best Reagrds,

ttd

  • HI ttd,

    This part was released long time ago from other team that is not existing anymore. We will try to answer as much as we can. 

    Datasheet Revision H was released 10 years ago, there were no major register change, the changes are kind of usage clarification, this does not look to me that will affect the initialization of the device. I don't have the details you are looking for in Q1.

    Q2. Looks like you only have problem in GenLock mode with FVH input. My guess is your H-sync signal has too much jitter that the PLL1 is not able to response properly. Where is your FVH came from?

  • Hi Noel,

    Thank you for your reply.

    I understand that this device is old. I you find previous post on E2E or your local, please let me know.

    I'll check "Auto Format Detection Codes" and it shows correct or not correct format about Q2.

    Best Regards,

    ttd

  • Hi ttd,

    This device has been asked many time, I have already looked into all channels but the information available for this device is very limited. I have never seen any initialization instruction.

  • Hi Noel,

    It seems that PLL3 is stable as a result of initializing PLL1 with the following settings.

    If the initialization procedure is incorrect, please let me know the correct procedure.

    1.Power Up

    2.ADDR 0x05 [7] = 1 ⇐Software Reset

    3. Crosspoint SW

     ADDR 0x09 [3:0] = 0010’b

     ADDR 0x09 [3:0] = 0000’b

    4.Free Run Mode for PLL1

      REG 0x05 [4:3] = 00’b    //PLL1 : Free Run mode

    5. Alignment Mode for TOF3

    Initial value -> Always Align -> Wait -> Initial value(Never Align)

    ADDR 0x13 [5:4] = 10’b    //TOF3 : Always Align

    Wait 500ms (More than 2 output frame period)

    ADDR 0x13 [5:4] = 11’b    // TOF3 : Never Align

    Best Regards,

    ttd

  • Hi ttd,

    I will check later.

  • Hi ttd,

    Again I don't find any initialization requirement, I assume this requirement does not exist.

    As for your programming sequence, I think there is no harm switching the registers forth and back. If this sequence works, I don't think there is side effect.

  • Hi,

    lmh1983 shows LOST_HSYNC when NG.

    Reg 0x00=0xC6

    What the meaning of the description?

    I didn't find HSYNC_MISSING  and no_h_during_v.

    HSYNC_MISSING = LOST_HSYNC?

    ---- 

    Set if HSYNC_MISSING is high wile no_h_during_v is low. Remains set until read, then self-clears

    ----

    On the other hand, the device status of Addr:0x01 Holdover=Low, Lock_Status=High seems to maintain Genlock.

    Best Regards,

    ttd

  • Hi ttd,

    Unfortunately, I cannot find the definition of these description. Sorry that we cannot help.