• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @efkean, Unfortunately (presuming I understand your question correctly), the serial terminals that are typically used with Xilinx SDK (Tera Term or the built-in serial terminal) do not have a plotting feature available, so you will not get the same user experience in this way. You would need to export the data to a different software such as Matlab or Octave. Alternatively, you can find a way to visualize the data through something like Python in a similar way that was done on this project. Thanks, JColvin
  2. Hi @paoppe, We don't have a CAD file for the Cora Z7, though we do now have an image of the hole dimensions present on the Cora Z7 which should help. Please let us know if you have any other dimensions you are looking for. Thanks, JColvin
  3. Hi @efkean, I would recommend taking a look at these two threads on our Forum (link1 link2) that discuss getting the Pmod AD1 running on a Zedboard. What do you mean when you said the analog values don't look like the Arduino's? That the values are different by a few millivolts, completely different voltage readings, different format, or something else? Thanks, JColvin
  4. Welcome to the Forums @Beqo06!
  5. Welcome to the Forums @cwerner77!
  6. Hi @voltagesurge, The OpenLogger should be able to accomplish what you are looking for including the portability portion, though there is a caveat which I will get to later. The way the embedded ADCs on the OpenLogger are set up, each channel is sampled individually, so if you were using 7 channels, the maximum sample rate for each channel would be ~71.42 kHz (500 kHz / 7 channels). It is also entirely possible to use a different microcontroller that has analog inputs, but the same restriction will apply in that each channel is sampled individually so you would divide the maximum sample rate (usually quoted on the list of features for the microcontroller) by the number of channels. The Arduino IDE (which supports a wide variety of microcontrollers including Digilent made ones, different Arduinos, and the Teensy) has built-in examples for reading in analog data, so that side of coding will not be difficult. Logging that data to an SD card will be where the work is. With regards amplifying the signal, you can amplify it before it goes to the data logger, but you must still be within the accepted voltage range of the analog inputs. The OpenLogger for example has an input voltage range of -10 V to +10 V. Most microcontrollers typically have a much smaller voltage input range such as 0 V to +3.3 V. What sort of resolution were you anticipating on needing to read for your signal (i.e. millivolts, microvolts)? Additionally, what voltage range are you planning to measure? Here is the previously mentioned caveat. Because the OpenLogger is a logger (and not an oscilloscope, which makes high speed acquisitions based on an external trigger), it will log data continuously at a certain sample rate and continue till it runs out of space. With the size of SD cards as they are nowadays (up to 32 GB for the FAT32 format, which is the format the OpenLogger needs), you would be able to record these 20 seconds worth of data (and the idle time inbetween) for quite some time, potentially long enough for your needs depending on what your application is. The other caveat with regards to your system is the number of channels. 7 channels can be readily supported by a number of devices, OpenLogger and otherwise, but 24 analog channels not so much. You would need to look into either dedicated Analog-to-Digital converters or have a microcontroller that supports multiple ADC peripherals (such as Digilent's Analog-to-Digital converter Pmods). Let me know if you have any questions about this (and a little bit more about the requirements for your system). Thanks, JColvin
  7. Hi @Tim S., Here on the Forum or even on this thread will be best; the engineers that write the content also communicate with customers on the forum so this will be the most direct line to them. Thanks, JColvin
  8. Hi @mladenik, The Pmod DA4 2x6 output header is designed like the image on the right; that is, when looking at the output header so that the physical outputs are directly facing you, Pin 1 is in the top right with Pin 2 directly below it in the bottom right. Pin 3 is directly to the left of Pin 1 with Pin 4 directly below Pin 3. This pattern continues until Pin 11 is in the top left with Pin 12 on the bottom left. The silkscreen labeling, as shown in this image, https://reference.digilentinc.com/_media/reference/pmod/pmodda4/pmodda4-1.png, shows the orientation and location of each of the outputs where 'A' corresponds to 'VOUTA', 'B' corresponds to 'VOUTB", and so forth. Please let me know if you have any further questions and I will be happy to answer them. Thanks, JColvin
  9. JColvin


    Hi @Ely4, I'm not certain if they will automatically connect since Bluetooth Low Energy is more security oriented than Bluetooth classic and requires the various associated bluetooth characteristics to be shared and confirmed between the two devices. Based on section 2.6.13 of the RN4871 User Guide, if a bonded connection is lost due to any reason (such as a power cycle), reconnecting with the device does not bond the devices again and provide a secure link (if that is of concern for you). You may be able to utilize the scripting capability to preload the known characteristics (which you can find out be connecting to a Pmod BLE through a BLE phone app) that is part of the RN4871, though I personally haven't used that feature of the chip. Thanks, JColvin
  10. JColvin

    pmod wifi

    Thanks for sharing what you found!
  11. Hi @AThomas, Which JTAG IC are you using? We at Digilent also like to keep track of the usage of the JTAG reprogramming application (and as the application re-flashes the chip, it's easy to ruin a number of devices unitentionally, much like how our JTAG devices become unrecognized in the first place). Thanks, JColvin
  12. Hi @mladenik, The Pmod DA4 is designed the way you would expect. I am not certain why the schematic is labeled the way it is, but the silkscreen labeling on the Pmod DA4 is accurate (I verified this with a multimeter referencing the pins on the AD5628 chip). Let me know if you have any questions about this. Thanks, JColvin
  13. Hi @Zed_Guy, XDC files do not change between different versions of Vivado, though the IP blocks that are supported in a particular version are sometimes incompatible between versions. XDC files inform Vivado how to associate a physical pin to a "pin" (not the official name) in an HDL project. As Bianca noted, if you are looking for an XDC for a particular project designed by Avnet, you will need to contact Avnet for the XDC for that project. Let me know if you have any questions about this. Thanks, JColvin
  14. Hi @danciprian, I don't believe WaveForms supports JTAG debugging at this point in time, but I have moved your question to a more appropriate section of the forum where the engineer far more experienced with the WaveForms software will be able to see and respond to your question. Thanks, JColvin
  15. Hi @YellowYoung, I apologize for the long delay. I'm not certain what else would have to be done differently. Since you have set the IOStandard and worked with the header changes, what I would attempt to do is to use a logic analyzer or multimeter to confirm that signals are successfully being transmitted from the FPGA through the FMC to the FMC card. If they are not being transmitted, then I would be concerned if the Bank the FMC pins are located on are damaged. Thanks, JColvin
  16. Hi @AlGee, I apologize for the delay. You can safely ignore this error; it just means that the Pmod IP was originally created for a different board; it will still work as expected. Thanks, JColvin
  17. Hi @tip.can19, The CYINIT pin appears to be an initialization bit, presumably to have the IP block to prepare itself for incoming data. It looks like this Xilinx thread addresses this in more detail. Thanks, JColvin
  18. Hi @nathan, We do not have a stereo camera solution for either variant of the Arty Z7. To my knowledge, the only product we have that enables stereo vision is the FMC Pcam Adapter, but that is only known to be compatible with the Zedboard, Nexys Video, Genesys 2, and the NetFPGA 1G CML. Let me know if you have any questions. Thanks, JColvin
  19. Hi @V94, If you are just trying to run the Embedded Vision Demo to confirm it works, all you need to do is copy the BOOT.bin file (located in the bin folder of the Embedded Vision Demo source files that are linked within the PDF you attached) onto a microSD card. If you are wanting to view the project files, you would need to open up Xilinx SDK 2017.4 (opening Vivado 2017.4 is only necessary if you want to make changes to the block design), choose the Workspace location (I choose the sdk folder within the Embedded Vision Demo folder), and then go to File -> Import -> General -> Existing Projects into Workspace, and then click Next. The first radio button option where it says "Select root directory" will have a Browse button; click Browse and select the same sdk folder within the Embedded Vision Demo folder. 5 checked projects should appear in the white box area consisting of the fsbl, fsbl_bsp, pcam_vdma_hdmi, pcam_vdma_hdmi_bsp, and the system_wrapper_hw_platform_0. If all 5 of those are checked, go ahead and click Finish. You will then be able to see the source code and make changes to the project from there. Let me know if you have any questions. Thanks, JColvin
  20. Hi @Starglow, We do have a cable that will connect to the host board, https://store.digilentinc.com/jtag-2x7-ribbon-cable/, but it does not have the male header to connect to the JTAG HS3, and all of headers that Digilent sells have a 2.54 mm pitch rather than the 2.00 mm pitch that Xilinx choose for their JTAG integration. I did do a Digikey search (though you are welcome to browse your favorite source for these) for a list of compatible headers that should work in your situation; the only thing I was not able to specify in the search was the 0.5 mm square posts to ensure the pins remain secure in the plastic header. Let me know if you have any questions about this. Thanks, JColvin
  21. Hi @xcellsior, I haven't done anything like this specifically, but I did jump down the rabbit hole and found you can use this command in Windows PowerShell to list out the Device ID of an attached Analog Discovery 2 (presuming it is the only "USB Serial Converter" device attached to the PC): Get-WMIObject Win32_PnPEntity | where {$_.Name -like "USB Serial Converter*"} | Format-Table PNPDeviceID The 12 digit value after the last backslash (\) will be the serial number of the attached Analog Discovery 2. I did not determine the CLI equivalent of this command though. If by chance when you say "PI" you happen to mean a Raspberry Pi, the Analog Discovery 2 and accompanying WaveForms software are compatible with the Raspberry Pi 4 Model B. Let me know if you have any more questions. Thanks, JColvin
  22. Hi @attila, do you have some thoughts on this? I tested this on my own Analog Discovery Studio, but was also unable to get a clean compensation at 10x attenuation using the probes Digilent provides. However, when I switch the setup to the Analog Discovery 2 (with the BNC adapter, DC coupled, 0 Ohm on the AWG) without otherwise changing the probe setup or workspace, I get a clean view of the square wave in both 1x and 10x attenuation. Thanks, JColvin
  23. Hi @Lars Lindner, This thread has some additional suggestions, or at least echos some of the ones already here in a bit more detail. Thanks, JColvin
  24. Hi @Steve Withers, I have contacted another Digilent engineer much more familiar with the DMC60c about this. Thanks, JColvin
  25. Hi @perryxue13, I apologize for the delay. Which version of the Digilent Core, https://reference.digilentinc.com/learn/software/tutorials/digilent-core-install/start, do you have installed? Do you get this error for just one particular sketch, or any sketch? Thanks, JColvin