AD9739A-FMC-EBZ USB SPI not working

The PIC18F24J50-I/ML on AD9739A-FMC-EBZ(rev C) seems not working well.

I have connected a USB cable to the AD9739A-FMC-EBZ but the AD9739A_SPI.exe (downloaded from High-Speed DAC Software Suite) couldn't recognize the device.

Actually, the LED XCR1 isn't lighted on, and my PC doesn't read any USB device when connecting AD9739A-FMC-EBZ.

My FPGA development board is Xilinx KC705, and I connect AD9739A-FMC-EBZ on the FMC LPC side

At first, I found the two jumpers JP1&JP2 missing, which has been discussed in:

I've put jumpers on JP1&JP2, and finally I got 1.8V on TP12 and 3.3V on TP1.

The power supply should be no problem now, but I still find the LED XCR1 not lighted on

The jumper on J2 has been switched to USB_SPI, and the VDD to PIC18F24J50-I/ML is 3.3V right now

Is there any USB drivers I should install on my PC in order to use AD9739A-FMC-EBZ?

Or, did I miss anything to start with  AD9739A-FMC-EBZ?

Thanks for your help

  • +1
    •  Analog Employees 
    on Feb 21, 2019 4:05 PM over 2 years ago

    The board might not be programmed properly. Would you please return the board to us and we'll replace the board for you.

    Sorry for any inconvenience this might has caused.

  • I am having the exact same issue. I am also using theAD9739A-FMC-EBZ and has the same missing jumpers and other issues. I am on a tight timeline, how can I get this resolved quickly?

  • 0
    •  Analog Employees 
    on Mar 12, 2019 9:47 PM over 2 years ago in reply to everil456

    Let me check some quick settings with you and then we can focus on the diagnostics of this board:

    1- The reason we didn't assemble JP1&JP2 from the first place is that we have noticed for some applications, those supplies can't be as clean as required. So we typically expect our customers to plug clean 1.8V and 3.3V supplies to TP12 and TP1, respectively. Make sure you either have shorted JP1 and JP2, or supplied power to TP1 and TP12.

    2- Plan if you are using SPI over USP or FMC. In the case of using SPI over FMC, use a jumper and short pins 1 and 2 of P2. In the case of USB SPI, the jumper should short pins 2 and 3 of P2 and then as you plug in USB cable, XCR1 should light up.

    3- Make sure you are using the latest version of our DPG Downloader and AD9739A update plugin

    4- for the USB driver if USB SPI option is used, you need to install DPG Downloader and make sure the USB Driver option is selected 

    Please check all the above and see if SPI tool detects the AD9739A DAC. 

  • I just got AD9739A-FMC-EBZ today, and having same problem with KC705 carrier board.
    - Soldered to short JP1 and JP2 on our AD9739A-FMC-EBZ
    - With P2 to "USB SPI", XCR1 doesn't light up even when USB connected

    Additionally, wIth P2 to "FMC", we have no MU lock with the reference .bit + .elf files from the Analog Devices Wiki site. The S1 is on ADF4350 and CR1 nearby ADF4350 lights up.

    Now I'm trying to get MU lock with my own FPGA design with MicroBlaze + SPI, but still no MU lock, too.
    Do we need "clearner" 1.8V/3.3V power supply? 

    Thanks in advance

  • Updates on my situation: Re-soldered C99 and C102 in "horizontal" direction. DAC clock is supplied from ADF4350 and now working fine with our own FPGA design. USB SPI and XCR1 still not working.

  • Hi, I found the C99 and C102 are in "vertical" in default, which it connects to the ADCLK914, not the ADF4350. However, on the ADI wiki site, it says these two caps are solded  in "horizontal" in default. 

    Besides, what is your design environment? ISE or Vivado? Did you create a bit file by yourself or you used the one provided by ADI?

    Thanks in advance

Reply Children
  • I'm working with my KC705 card with Vivado. The sample .bit file and .elf files from ADI are generated by ISE+EDK, but still loadable with Vivado hardware manager and xsdb (the command-line debugger comes with Vivado SDK). At first we have confirmed that we have no MU lock with ADI's bit+elf files (while the caps are vertical) then re-soldered the caps and we got MU lock. Now the board is running perfectly with our own HDL design and MicroBlaze SPI control code, but ADI stuff is sufficient to confirm the board is alive. We have no idea with USB-SPI PIC, but it's OK because we can control SPI wires by MicroBlaze.