• Content Count

  • Joined

  • Last visited

Posts posted by algae

  1. I decided to go with the DD since it can get me the MHz rates that I need.

    However, I can't seem to figure out how to use the SDK to implement the ROM  or an FSM. I can generate the outputs and sample inputs, but the docs don't seem to tell me how to route the inputs to the pattern memory address lines. So, how do I go about setting the mux to use the inputs for the pattern memory addressing instead of the counter?

  2. The ROM logic looks like a good way to do this since I can implement an FSM to do the bit-banging and run at a much higher speed. Am I correct that I use the FDwfDigitalOutDataSet API function to load in the ROM pattern memory?

    How about the Algorithmic Generator? What can that do and how might I be able to use that from custom code?

  3. I'm looking for hardware that I can use to bit-bang a custom digital board I'm testing. I see the that one of the WaveForms SDK examples drives some pins and samples some pins. This would allow me to write C code to drive stimulus to my board, sample responses from the board, and respond with more stimulus in an algorithmic way as opposed to the canned pattern generator/logic analyzer combo that I think the Digital Discovery is intended for. So, the question is: what kind of expected data drive/sample rate can I expect using this bit-bang approach with your SDK through the USB port to my host computer? Alternatively, do you guys have a better solution for this short of programming an FPGA to implement my protocol and store stimulus and response data?

    Also, can I configure one of the DIO as a free-running, independent clock output while other DIO are used for communication?

  4. Hello!

    I see that the Adept runtime is used in WaveForms app on all the platforms including MacOS. I'd like to use the Adept API's on MacOS to talk to devices like the JTAG HS2. How do I go about getting the Adept SDK for MacOS so I can roll my own code for those devices?


  5. I'm trying to use the Adept SDK on cygwin and am having trouble enumerating the connected devices. I have a JtagHs2 device plugged into a USB port on my Windows box.

    When I call the DmgrEnumDevices function in my app, it tells me that it found 0 devices attached to the system.

    However, if I run the Adept app it can find the device and show its details (SN, etc.)  If I leave Adept running, my program will then report that it finds the device I have plugged into the USB.

    If I then quit Adept and run my app again, my app will not be able to find the device.

    The dadutil app can find the device with or without Adept running.

    Clearly, my app is missing something that Adept and dadutil is doing. What am I missing?

    Here's a bit of my code:

    	// report some admin stats
    	if (!DmgrGetVersion(dmgrVersion)) {
    		cout << "Could not get the Dmgr version"
    				 << endl;
    	cout << "Using Adept Dmgr version "
    			 << dmgrVersion
    			 << endl;
    	// see how many Digilent things are here
    	if (1) {
    		int numDevices;
    		if (!DmgrEnumDevices(&numDevices)) {
    			cout << "Could not enum devices"
    					 << endl;
    		cout << "Found "
    				 << numDevices
    				 << " Digilent devices"
    				 << endl;

    The code will get the Dmgr version just fine, so I can call functions in the sdk, but DmgrEnumDevices behaves differently depending on whether Adept is running. Help!

  6. Just to follow up on this topic... Qt5 (Windows/cygwin) works just fine with the Adept libraries for SPI communication. Nothing special needed here at all if you use the Qt5 IDE to build your app.

    Using cygwin's command-line to build an app with the Adept libs is a different story, though.

  7. We have some JTAG HS2 dongles for talking SPI to our devices. We've recently started playing with devices that have dual I/O SPI modes for increasing the data bandwidth without increasing the pin count. Can the JTAG HS2 handle these SPI modes? We also roll our own software so having an Adept lib that supports this would be real nice. Anybody try this before?


  8. Hello!

      I'm planning to use a JTAG HS2 cable for custom SPI communication. Before I take the plunge and get the cables, I have a few questions:

    1) is this cable based on the Digilent chip or the FTDI chip?

    2) does the the Adept API work with Qt5 running in Cygwin on Windows7? Has anyone tried this?

    3) has anyone tried using libusb to talk to the cable instead of using the Adept SDK?