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.

DAC38J84: DAC38J84: Internal PLL can not Locked

Part Number: DAC38J84
Other Parts Discussed in Thread: LMK04828

Dears.

I'm testing a scrip created using the GUI, but I get a PLL error.

We need register values that match our setting.

The settings for using the DAC38J84 are shown below.

Input Clock : 122.88Mhz

Input Data rate : 122.88 Mhz

Interpolation :16

Complex mixer enable

JESD LMFS : 2441

Internal PLL use.

When register 6c address is set as below, 0x000F is read.

Please, Check

DacRegWrite(0x00, 0x0218);

           DacRegWrite(0x01, 0x0003);

           DacRegWrite(0x02, 0x2012);

           DacRegWrite(0x03, 0xA300);

           DacRegWrite(0x04, 0xF3F3);

           DacRegWrite(0x05, 0xFF07);

           DacRegWrite(0x06, 0xFFFF);

           DacRegWrite(0x07, 0x3100);

           DacRegWrite(0x08, 0x0000);

           DacRegWrite(0x09, 0x0000);

           DacRegWrite(0x0A, 0x0000);

           DacRegWrite(0x0B, 0x0000);

           DacRegWrite(0x0C, 0x0400);

           DacRegWrite(0x0D, 0x0400);

           DacRegWrite(0x0E, 0x0400);

           DacRegWrite(0x0F, 0x0400);

           DacRegWrite(0x10, 0x0000);

           DacRegWrite(0x11, 0x0000);

           DacRegWrite(0x12, 0x0000);

           DacRegWrite(0x13, 0x0000);

           DacRegWrite(0x14, 0x0000);

           DacRegWrite(0x15, 0x0000);

           DacRegWrite(0x16, 0x3000);

           DacRegWrite(0x17, 0x0000);

           DacRegWrite(0x18, 0x0000);

           DacRegWrite(0x19, 0x3000);

           DacRegWrite(0x1A, 0x0000);

           DacRegWrite(0x1B, 0x0000);

           DacRegWrite(0x1E, 0x9999);

           DacRegWrite(0x1F, 0x9980);

           DacRegWrite(0x20, 0x8008);

           DacRegWrite(0x22, 0x1B1B);

           DacRegWrite(0x23, 0x01FF);

           DacRegWrite(0x24, 0x0020);

           DacRegWrite(0x25, 0x8000);

           DacRegWrite(0x26, 0x0000);

           DacRegWrite(0x2D, 0x0001);

           DacRegWrite(0x2E, 0xFFFF);

           DacRegWrite(0x2F, 0x0004);

           DacRegWrite(0x30, 0x0000);

           DacRegWrite(0x31, 0x0400);

           DacRegWrite(0x32, 0x0F00);

           DacRegWrite(0x33, 0xA330);

           DacRegWrite(0x34, 0x0000);

           DacRegWrite(0x3B, 0x1800);

           DacRegWrite(0x3C, 0x1028);

           DacRegWrite(0x3D, 0x0088);

           DacRegWrite(0x3E, 0x0108);

           DacRegWrite(0x3F, 0x0000);

           DacRegWrite(0x46, 0x0044);

           DacRegWrite(0x47, 0x190A);

           DacRegWrite(0x48, 0x31C3);

           DacRegWrite(0x49, 0x0000);

           DacRegWrite(0x4A, 0x031E);

           DacRegWrite(0x4B, 0x0301);

           DacRegWrite(0x4C, 0x0403);

           DacRegWrite(0x4D, 0x0300);

           DacRegWrite(0x4E, 0x0F0F);

           DacRegWrite(0x4F, 0x1C61);

           DacRegWrite(0x50, 0x0000);

           DacRegWrite(0x51, 0x00DC);

           DacRegWrite(0x52, 0x00FF);

           DacRegWrite(0x53, 0x0000);

           DacRegWrite(0x54, 0x00FC);

           DacRegWrite(0x55, 0x00FF);

           DacRegWrite(0x56, 0x0000);

           DacRegWrite(0x57, 0x00FF);

           DacRegWrite(0x58, 0x00FF);

           DacRegWrite(0x59, 0x0000);

           DacRegWrite(0x5A, 0x00FF);

           DacRegWrite(0x5B, 0x00FF);

           DacRegWrite(0x5C, 0x1133);

           DacRegWrite(0x5E, 0x0000);

           DacRegWrite(0x5F, 0x0123);

           DacRegWrite(0x60, 0x4567);

           DacRegWrite(0x61, 0x0211);

           DacRegWrite(0x64, 0x0001);

           DacRegWrite(0x65, 0x0001);

           DacRegWrite(0x66, 0x0001);

           DacRegWrite(0x67, 0x0001);

           DacRegWrite(0x68, 0x7709);

           DacRegWrite(0x69, 0x0000);

           DacRegWrite(0x6A, 0x0000);

           DacRegWrite(0x6B, 0xBD07);

           DacRegWrite(0x6C, 0x0007);

           DacRegWrite(0x6D, 0x0090);

           DacRegWrite(0x6E, 0x0000);

           DacRegWrite(0x6F, 0x0000);

           DacRegWrite(0x70, 0x0000);

           DacRegWrite(0x71, 0x0000);

           DacRegWrite(0x72, 0x0000);

           DacRegWrite(0x73, 0x0000);

           DacRegWrite(0x74, 0x0000);

           DacRegWrite(0x75, 0x0000);

           DacRegWrite(0x76, 0x0000);

           DacRegWrite(0x77, 0x0000);

           DacRegWrite(0x78, 0x0000);

           DacRegWrite(0x79, 0x0000);

           DacRegWrite(0x7A, 0x0000);

           DacRegWrite(0x7B, 0x0000);

           DacRegWrite(0x7C, 0x0000);

           DacRegWrite(0x7D, 0x0000);

           DacRegWrite(0x3B, 0x1800);

           DacRegWrite(0x25, 0x8000);

           DacRegWrite(0x3C, 0x1228);

           DacRegWrite(0x3C, 0x1028);

           DacRegWrite(0x3E, 0x0128);

           DacRegWrite(0x4C, 0x0401);

           DacRegWrite(0x4D, 0x0300);

           DacRegWrite(0x4B, 0x0303);

           DacRegWrite(0x4D, 0x0300);

           DacRegWrite(0x4E, 0x0F0F);

           DacRegWrite(0x00, 0x0818);

Thank you.

  • Hi Henry,

    Please help confirm if the customer is providing the 122.88MHz clock to the EVM, or are they planning on using the on-board LMK04828 to provide the 122.88MHz reference clock

    Basically, for the first step of GUI config, which one are they choosing?

    Could the customer also post various screen shots of the GUI so I can take a further look at their configuration? It is easier than looking through the various lines of codes.

  • Hi Henry,

    I am still waiting for your feedback. Just to close this out with some following information. If you want to reopen this post you can simply reply back.

    The PLL settings can be set in the following GUI section:

    With the PLL setting listed in the datasheet below

  • HI. KANG

    It is GUI capture as below.

    We need register values that match our setup conditions.

    Please, Review

    Thank you

  • Henry,
    I have answered your question through TI internal FAEs email chain. I will close this issue on E2E. Please look for email from our TI team.
    -Kang