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.

DAC3482EVM: DAC3482 No output, good way to confirm whether DAC3482 is damaged

Part Number: DAC3482EVM

Hello team,

Is there any good way to confirm whether DAC3482 on EVM is damaged or not?

My customer followed EVM users guide "3.4 DAC348x Example Setup Procedure" and could see same output as figure 13 at customer environment once. However, on the next day, customer tried same procedure by following users guide but DAC3482 doesn't output anything somehow. They confirmed CDCE62005 clock output is correct so concern on DAC3482 damage. I would appreciate if you could provide a way to confirm if DAC3482 is damaged.

Best regards,

  • Hi Sato-san,

    They may read back the chip ID register to confirm if the SPI is working

    They can also check out the following app note to see if the output protection alarm had been kicked in:

    https://www.ti.com/lit/an/slaa585/slaa585.pdf

  • Hello Kang-san,

    Customer readback DAC3482 register information after setting "DAC3482_FDAC_1228p8MHz_4xint_NCO_30MHz_QMCon.txt".

    I attached the readback register file.

    DAC3482_Register_Read_Value.txt
       x00	   xF28C
       x01	   x0000
       x02	   x8052
       x03	   xA001
       x04     xFFFF
       x05     x0060
       x06     x2800
       x07	   xFFFF
       x08	   x0000
       x09	   x8000
       x0A	   x0000
       x0B	   x0000
       x0C	   x05A6
       x0D	   x05A6
       x0E	   x05A6
       x0F	   x05A6
       x10	   x3000
       x11	   x0000
       x12	   x0000
       x13	   x0000
       x14	   x0000
       x15	   x0640
       x16	   x0000
       x17	   x0640
       x18	   x205F
       x19	   x10F4
       x1A	   x4820
       x1B	   x0800
       x1C	   x0000
       x1D	   x0000
       x1E	   x1111
       x1F	   x8882
       x20	   x2400
       x22	   x1B1B
       x23	   x001F
       x24	   x1000
       x25	   x7A7A
       x26	   xB6B6
       x27	   xEAEA
       x28	   x4545
       x29	   x1A1A
       x2A	   x1616
       x2B	   xAAAA
       x2C	   xC6C6
       x2D	   x0004
       x2E	   x0000
       x2F	   x0000
       x30	   x61A8
       x7F	   x0004

    Looking at 0x7F, device ID is 00b and different from register map information.

    Is it due to improper SPI? or, is device damaged? or, once loading "DAC3482_FDAC_1228p8MHz_4xint_NCO_30MHz_QMCon.txt" device ID may be overwritten?

    Best regards,

  • Hello Taketo-san,

    Other registers are reading fine. I also read 0x07 = 0x0004 on my EVM. 

    Please advise if the customer is using the TSW1400 to test out the DAC EVM. If so, please advise the LED light status when testing the DAC3482. 

    Please also check the alarm page of the DAC3482 to see if any alarms showed up

  • Hello Kang-san,

    Yes they are using TSW1400 to test the DAC EVM. LED status of the board is below 8 LEDs are lit.

    • USER_LED0
    • USER_LED1
    • USER_LED2
    • USER_LED4
    • USER_LED6
    • USER_LED7
    • FPGA_CONF_DONE
    • C87


    Regarding alarm page of the DAC3482 shows below.

    Best regards,

  • Hello,

    There is DAC clock gone alarm indicates the DACCLK is not received by the DAC. I would recommend the customer to double check the CDCE62005 clock output and also increase the drive strength of the external clock source.