Post Go back to editing

AD5370 Eval - Software Development API - CYPRESS USB (EZUSB CYUSB)

I would like to be able to write my own software to interface to a EVAL-AD5370 DAC board. Does anyone know if Analog Devices has a published software document that describes how to interface to their (many) USB/EVAL devices? I know that they use the CYUSB family of USB products from CYPRESS, but I can't divine a way to get from the USB port to the output pins and make it to the SPI interface. This could really qualify as more of a general question, as Analog Devices produces has many EVAL boards that have a USB interface. One of the tougher parts about trying to do this on my own is the fact that a HEX file is downloaded to the CYPRESS part right as the AD EVAL software starts. Who knows how that changes the USB Interface? The current EVAL app look like a Visual Studio app and uses ADI_CYUSB_USB4.dll. Any insight welcome - especially from an AD Software type!

(WINDOWS 8, Visual Studio V6, V10 or V11 C++ or C# / .NET)

Thanks!

Parents
  • Hi,

    I could use the CYusb software source too.

    This is cross-posted from a different thread to rbrennan:

    Your MSWindows implementation is far ahead of your Linux implementation, but your CYusb library appears to not have the same API names as the Cypress cyusb and usblib libraries.

    I would like to reverse engineer the calls to make it work.

    In particular, I am trying to figure out what "connectedDevice.ControlEndPt.XferData" in the console writer program you posted corresponds to what in the cyusb or libusb library call.

    My employer is planning to purchase at least 100 ADF4351's for a project funded by the NSF (and possibly the US Airforce -> another 400+ or so units) to revolutionize radio astronomy, but we (MIT) may not purchase your parts if I cannot get the software to work.

    Any assistance?

Reply
  • Hi,

    I could use the CYusb software source too.

    This is cross-posted from a different thread to rbrennan:

    Your MSWindows implementation is far ahead of your Linux implementation, but your CYusb library appears to not have the same API names as the Cypress cyusb and usblib libraries.

    I would like to reverse engineer the calls to make it work.

    In particular, I am trying to figure out what "connectedDevice.ControlEndPt.XferData" in the console writer program you posted corresponds to what in the cyusb or libusb library call.

    My employer is planning to purchase at least 100 ADF4351's for a project funded by the NSF (and possibly the US Airforce -> another 400+ or so units) to revolutionize radio astronomy, but we (MIT) may not purchase your parts if I cannot get the software to work.

    Any assistance?

Children
No Data