JColvin

Administrators
  • Content Count

    3194
  • Joined

  • Last visited

  • Days Won

    106

Everything posted by JColvin

  1. JColvin

    Analog Discovery 2

    Hi @Stas Last, I don't have LabVIEW 2017 so I'm not able to open your VI to see for myself. Additionally, are you using Digilent WaveForms VI set or the AD2 toolkit? My understanding is that the AD2 toolkit VI set does not work with LabVIEW 2017, but I think (again, I don't have LabVIEW 2017) the Digilent WaveForms VI should work. There is a thread here that discusses changing the sample rate and sample taken based off of this tutorial though I was unable to get it to correctly display all of those data points on the front panel. Thanks, JColvin
  2. Hi @Luke Abela, My understanding is that the MIG is crucial for this particular tutorial, otherwise you would have to somehow configure the usage of DDR memory without an IP to handle the intracices for you, which is not a trivial task. My recommendation (I'm not certain if you have already tried it) would be to close this project and Vivado and start with a fresh project. To confirm, you have the Digilent board files installed and are using Vivado 2018.2 on Windows 10? Thanks, JColvin
  3. Hi @FloMai, I have moved your question to a more appropriate section of the forum. There is a thread here (containing some additional threads with further details discussing the same topic) that I would recommend looking through. It is possible to use multiple AD2's on a computer though each require their own instance of Waveforms. The total number will depend on your machine setup and power capability. Because each Analog Discovery 2 needs a separate instance of WaveForms you will not be able to see 32 digital channels on a single GUI screen, though you can have one AD2 trigger it's acquisition based on a different AD2. Thanks, JColvin
  4. Hi @RelativeHardware, I'm not certain what the issue might be; is there a particular reason you are not using microblaze? I did attempt to create what you showed in your block design (though I don't have MATLAB to test this), though my block design ended up looking a bit different than yours; I attached an image of it below.. The messages I received while generating the bitstream was Vivado letting me know that the device_temp_i port was not connected to anything, but the bitstream was able to successfully generate. Thanks, JColvin
  5. JColvin

    Firmware via Android

    Hi @Taras, Unfortunately, we do not have any advice with regards to programming an FPGA from an Android device. Thank you, JColvin
  6. JColvin

    Arty Board with RMII?

    Hi @bkzshabbaz, I don't believe there is anything preventing you from doing this, though I would probably use the MII to RMII IP that Xilinx has available, much like this tutorial does for the Nexys 4 DDR. Naturally, you would need to change the xdc pin to match the ETH_REF_CLK to match the one for whichever Arty board you happen to be using. Let me know if you have any questions about this. Thanks, JColvin
  7. Hi @JXS, The bests solution that I can offer would be to use a different/better quality usb cable; there is a collection of other threads on this particular topic with the Cmod A7 on this thread here: Thanks, JColvin
  8. JColvin

    XC7A15T-1CPG236

    Hi @Saad, There is a 3D model for the Cmod A7 (likely the 35T variant) on the Cmod A7 Resource Center on the right-hand side under Design Resources. As @xc6lx45 indicated, they will be mechanically identical. Otherwise, we do not provide the Altium files for our products. Thanks, JColvin
  9. Hi @ub3rmike, I have sent you a PM about this. Thanks, JColvin
  10. Hi @amitceder, I don't quite know what you mean by it behaved the same prior to rebooting, but I confirmed with the design engineer who created Adept that Adept will not initialize on any UltraScale+ boards from Xilinx. Let me know if you have any questions. Thanks, JColvin
  11. Hello @amitceder, What platform are you attempting to use Adept and the JTAG HS3 with? Thanks, JColvin
  12. Hi @electronic, I have sent a you a PM about this. Thanks, JColvin
  13. Hi @amitceder, The Digilent Adept software is not able to program the Xilinx UltraScale plus board. If you want to program the UltraScale board, you will need to you Xilinx's Vivado software with the JTAG HS3. Let me know if you have any questions. Thanks, JColvin
  14. Hi @ub3rmike, I have reached out to another engineer about your question. Thanks, JColvin
  15. Hi @Ujjal, Based on the description of the YouTube video in the comment above yours here, it is only compatible with Window's systems. Thanks, JColvin
  16. Hi @Luke Abela, You would only receive that screen if you double clicked on the the MIG, which the tutorial you linked to does not instruct you to do. I just ran through the tutorial on Vivado 2018.2 and was able to generate the bitstream. Did you avoid clicking the "Run Connection Automation" on step 2.6? I was able to see the "Run Block Automation" for the mig_7series_0 block in step 4.1. Thanks, JColvin
  17. Hi @tfcb and @Diego, Had an epiphany just now and figured you were owed it now in the middle of the night rather than waiting till after the Labor Day holiday in the US. The reason the Uno isn't working is because of the required voltage translation; all of the code is working off of the 3.3V logic that the Pmod ISNS20 uses, but because the Uno uses 5V logic, this rescaling needs to be reflected in it's material as well. So any number in the code that relies on 3.3V logic being used will likely need to be scaled to 5V. I will provide an update tomorrow of how the numbers will look with this change (in general should be divide by 3.3 and multiply by 5, though that might need to be different for values that depend on specific Vrefs) and be able to formally test the changes in the office on Tuesday. Thanks, JColvin
  18. Hi @tfcb and @Diego, I have not been able to get the Pmod ISNS20 to work on an Arduino UNO; I have it set up so that I can simply move the connection wires from the Arduino UNO to a Digilent microcontroller (that operates at 3.3V for it's IO rather than 5V) and the module works correctly on the Digilent microcontroller but not the Uno. Originally, I had left the inputs on the ISNS20 floating, but attached the same ground source to both of them to help ensure no voltage potential was present, but to no avail. When I power cycle the Arduino Uno and restart the data collection, I get different values reported from the ISNS20 (and wildly different values, i.e. different by several amps) between each sample. I put delays in the code to ensure the data was not moving faster than the AVR could maintain and checked that the level shifter that I was using was operating as intended, but to no avail. I wish I had better news, but I do not know what else could be done differently to make it work correctly. Thanks, JColvin
  19. Hi @robzane, It looks like there code examples for PIC32 interrupts within that document that you linked. There are some additional interrupt materials available in the Relate Materials box on the right side of the screen here as well: https://learn.digilentinc.com/Documents/216. Thanks, JColvin
  20. Hi @Allmoz, We're not able to provide the schematics for the USB connectivity on the Basys 3, though there is a thread detailing what sort USB port would be needed here, though I personally have never been able to find a part that matches the dimensions. If some of the USB connectors do not have the traces ripped off, there is a possibility that you could solder the connector directly back onto the board, though there's no guarantee that'll work. Some of the connectors could still be okay; I have seen some boards come get returned where the user had plugged in the micro-USB cable upside down in the connector, but after carefully bending the connector back to the correct orientation (I used a small flathead screwdriver), I was able to plug a cable back in and have the board work with no issues. As for the switches, contact cleaner or compressed air would be what I would suggest to clean them. It is possible to remove the top half of the switch from the bottom half (since it's held on by four small tabs) to get easy access to the conductor to clean off the dirt or any sort of corrosion, though I don't know how easy it would be to get those tabs secured back into place (I would guess that it is not so easy). The part we specifically used for the Basys 3 is here, though apparently it's not stocked any more, but since it is a straightforward SPDT switch, any switch that has 4 mm of space between the centers of each of the through hole pins would work as a replacement. Let me know if you have any questions. Thanks, JColvin
  21. Hi @mustafasei, When you provide the different serial port options, such as the /dev/ttyACM0, as the LINX Resource Input, could you provide a screenshot of this input? My understanding is that the drop-down menu options do not contain the correct path to the serial port (or at least do not show up correctly). Thanks, JColvin
  22. Hi @bixie, I have moved your question to a more appropriate section of the forum where the Digilent engineer more familiar with WaveForms and WaveForms SDK will be able to see and respond to your question. Thank you, JColvin
  23. Hi @Zosty, I reached out to another engineer more familiar with Adept and learned that particular CPLD was likely added by mistake to the recognized device list within Adept, but (as you have found out) was never tested to confirm to work correctly like other CPLDs that are also on the list and within the same family (such as the XC2C256 or the XC2C32A). The solution at this point would be to use ISE to program that CPLD. If you are upgrading your machines/OS's, and still need to program this CPLD, I would recommend setting up a virtual machine on a separate partition to host and support ISE programming. Thank you, JColvin
  24. Hi @GrouchEng, Do you have a technical question associated your post? Otherwise, the link to the Digilent blog is located at the top of this page. Thanks, JColvin
  25. Hi @labviewkozou, I apologize for the delay. I must also admit I am a little confused; you have LINX 3.0 installed on a Windows 10 machine (and presumably LabVIEW 2014 Home Edition if you managed to connect to the target). But you say that you are getting an error when you are installing LabVIEW 2014 Home Edition? Where are you attempting to install LabVIEW? Thanks, JColvin