• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @David Allen, I know you mentioned that Adept was reporting the correct ID codes, but wanted to verify that this is accurate since there is a possibility that Adept would not recognize the Ultrascale chips and just report an incorrect ID code. Could you let us know what voltage is being applied to VREF and what voltage is being applied to VCCO_0 of the FPGA banks involved in the scan chain? Thanks, JColivn
  2. Hi @skywalker, Which Digilent blog post were you looking at which linked to this forum thread? I know the Cmod A7 Resource Center in the Example Projects section links to this forum thread (after I got permission from zygot to do so), but I would like to make sure that our blog posts link to the correct information. Additionally, the reason you had to regenerate the bitstream for step 4 for the Cmod A7 OOB demo was because you were using Vivado 2018.3 when the release was designed for Vivado 2018.2. Thanks, JColvin
  3. Hi @David Allen, I asked one of our design engineers about this and they recommended that you try slowing down the clock frequency of the JTAG scan within Vivado since with the 4 devices in the scan chain, there could be some signal integrity issues due to the added capacitive load depending on how it's routed. They also recalled that Vivado has a default higher clock rate than both Adept and iMPACT so that could be why Vivado is having more difficulty if there are any signal integrity issues. Let us know how that goes. Thanks JColvin
  4. JColvin

    arty gpio demo

    Hi @adiganta, I asked around and we're thinking it's probably PuTTY, but perhaps an older version (or different tool view for it) than what is currently available now. Thanks, JColvin
  5. Hi @Guru Prasanth S, I am not as familiar with the dvi2rgb and rgb2dvi IP cores that Digilent has developed so I have asked for another engineer more familiar with them for input on this. Thanks, JColvin
  6. Hi @efkean, Are you taking into account the fact that the Pmod AD1 IP already converts the data into the 0 V to 3.3 V from the 12-bit range of 0 to 1024? The values you referenced on the Pmod AD1 IP are accurate provided that the AXI clock connected to the IP core is not faster than 100 MHz (as per the Readme on the Pmod AD1 IP core on our GitHub). If you wanted to just have the 0 to 1024 data, you would need to change the functions used in the main.c file (within the SDK project) to only call AD1_GetSample and not call AD1_RawToPhysical (and adjust the printf functions to use RawData variables rather than PhysicalData values) to get a similar result. Let me know if you have any questions about this. Thanks, JColvin
  7. Hi @joshuajohn, I have reached out the appropriate people here at Digilent to get a Statement of Volatility for the Max32 Microcontroller. Thank you, JColvin
  8. Hi @jot, I don't have a MacOS to test this for myself, and you didn't say if you did this already, but I presume after you already modified the driver and got it relocated back into the appropriate system folder, you restarted the computer in order for the changes to be applied? Otherwise, I don't have any immediate ideas at the moment as to why you might try differently, though I will ask around to see if another one of our engineers happens to use MacOS. Thanks, JColvin
  9. Hi @INTT, Since it appears you are using ISE and iMPACT, I believe the software you are looking for is available here: https://store.digilentinc.com/digilent-plugin-for-xilinx-tools-download-only/. As noted on the webpage, you will need the Digilent Adept System (for Windows) or Runtime (for Linux) for this to work. The appropriate Adept material is available for download here: https://reference.digilentinc.com/reference/software/adept/start. Let me know if you have any questions. Thanks, JColvin
  10. Hi @Naji, That list of batteries comes from the battery clip holder datasheet (it is a 3000TR/3000KCT coin cell retainer). The problem that you unfortunately encountered is that the manufacture was technically correct in listing the CR1216 battery (12 mm in diameter, 1.6 mm in height, which is where the "1216" portion of the battery name comes from) as it will make contact with the clips, but as soon as those clips get bent in any way, that particular battery is no longer secure. In the interest of future proofing (and considering that the internal height of the coin cell retainer is approximately 3 mm), I would instead use one that is 2.0 or 2.5 mm in height (1220 or 1225 battery suffix, respectively). The different prefixes (CR and BR) indicate different standard discharge currents due to different chemistry make up. More information is available on this Wikipedia page. Personally, I would go with the CR1225, though you could also bend the tabs down on the current coin cell holder to better keep the battery contained. Please let me know if you have any questions. Thanks, JColvin
  11. Hi @voltagesurge, 1. can the data logger write 500 ksps (and 62.5ksps per channel in the case of using all 8 channels) straight to a memory card, when not connetected to a computer (having some portable power supply like a power bank)? - can it do this easily being programmed using the waveforms software? -- Yes. You will not use the WaveForms software though, you would instead use WaveFormsLive.com on a web browser to set up the OpenLogger and then under the Advanced options within WaveFormsLive.com choose to Log on boot (tutorial here), which will make the OpenLogger start logging with the saved parameters. The OpenLogger, as a logger, will maintain the constant sampling rate and will not deviate from that until the SD card is entirely filled. 2. Is the waveforms software free with the openlogger (I intend to buy it from a supplier overseas as I don't live in the US)? can one just download it for free off the website? - does one just setup the software with the computer. unplug it and then when it is going to be used just switch it on and let it run and then turn the power off when one is finished? -- Yes, WaveFormsLive.com is free to use. 3. can the software be used in a harsh environment/take a hit? I will be using this in an environment where -- It doesn't seem like you completed your question, but the OpenLogger itself so long as it is not directly being jumped on will be fine. You would likely want to make sure that any wires going from the OpenLogger to the system in questio are secured and do not come undone during the process. The software/firmware will not be affected by vibrations. 4. how does the file storage system work? - what formats are possible etc? - I read that there were issues in the past, does the file storage now work smoothly? -- The OpenLogger stores data to the SD card in a specialized dlog file which will then need to be converted to CSV through this tutorial here. Thanks, JColvin
  12. JColvin

    PMod AD4 (16 bits/1MSPS)

    Hi @herve, Unfortunately we do not have another ADC Pmod that meets these requirements. The only thing that we have that meets these requirements is the Analog Discovery 2, though it is not a Pmod (and I don't know how critical it is your application for it to be a peripheral). Let me know if you have any questions about this. Thanks, JColvin
  13. Hi @JHall, I asked around about this, but unfortunately we do not have the MPLAB X project for the OpenScope MZ available. Thanks, JColvin
  14. Hi @FloMai, I apologize for the delay. I updated my Raspbian desktop to the same edition (4.19.75) but I am able to detect and run the Analog Discovery 2 with a Raspberry Pi 4 Model B without. Could you attach a picture of your setup? Otherwise, I might recommend trying an external power supply. @attila do you have another idea of something this user might try? Thanks, JColvin
  15. Hi @jerryOn, I have sent you a PM with some instructions. Thanks, JColvin
  16. Hi @G Mason, I apologize for the delay. The WiFIRE will work with IoT applications, though we do not have demos that use MPLAB X or Harmony. The application we have is an HTTP Server that is done through the Arduino IDE (with the Digilent Core). In addition to what @Cristian.Fatu here is a small video series on Digilent's YouTube Channel that does talk a little bit about using FreeRTOS on the WiFIRE material. Let us know if you have any questions about this. Thanks, JColvin
  17. Hi @myman, In addition to the resources already completely worked on and completed by @D@n, Digilent made an IP core for the Pmod ACL2 available here. We do not have a Pmod IP core for the Pmod MIC3, though you could look at the Pmod DPG1 IP core that uses the same Analog-to-Digital converter chip that the Pmod MIC3 uses; the difference here would be that rather than using the DPG1_GetPressure function which converts the 12 bits of incoming data to pressure, you would use the function of your choice to handle the 12 bits of the measured audio data. I would recommend looking into the material @D@n made for the Pmod MIC3 though since that will certainly be more comprehensive. Thanks, JColvin
  18. Hi @Johnnie White, Are you using a shield that is placed on the top of the Arty A7 or using an IP core for the SPI functionality? I did a simple check with a Verilog project, (verilog file attached below) and it successfully enabled a LED I attached to the pins. Thanks, JColvin top.v
  19. Hi @Johnnie White, My understanding for how calculating the flash offset is dependent on the size of the bitstream (which varies between different FPGA boards, though it will be the same for a particular board each time because each slice has to be configured). There is also some additional details in this Avnet tutorial in section 9.3 with regards to choosing an offset, https://www.avnet.com/opasdata/d120001/medias/docus/178/UG-AES-A7MB-7A35T-G-Arty-SREC-Bootloader-VIV2015-2-V1.pdf, though in the end the folks on the Xilinx forum would be able to better answer how that particular portion of the Xilinx software works/needs to be configured. Thanks, JColvin
  20. Hi @David Allen, There should not be any incompatibilities between the JTAG modules and Xilinx Ultrascale+ boards based on previous conversations that I have had with our design engineer. I do know that Adept is not able to program Ultrascale+ boards so you would need to communicate through the Vivado Hardware Manager. Is this a custom made board or one that already has the JTAG SMT2 NC integrated into it? Thanks, JColvin
  21. Hi @owensgd, I apologize for the delay. Do you have happen to have a picture of your setup? The other potential problem that I can think of is that the USB cable is being plugged in upside down (I have seen this situation happen multiple times with a Basys 3 in particular); the nubs on the end of the micro USB cable need to be facing upwards when plugging into the board. Additionally, within the micro USB connector itself, the small tab that contains the USB data and power lines needs to be towards the top of the connector for the cable to connect correctly. Let me know if you have any questions about this. Thanks, JColvin
  22. Hi @Constantine, I have sent you a PM with some instructions. Thanks, JColvin
  23. Hi @Constantine, Which Digilent board do you have? Thanks, JColvin
  24. Hi @voltagesurge, For the OpenLogger, getting it to log to the SD card is as straightforward as setting the "Log to" dropdown setting on WaveFormsLive.com to have it log to SD card. The SD card will need to be 32 GB since that is the largest that the FAT32 format is compatible with, so a 64 GB card will not work as it will be in a different format. When you add channels to be logged on the OpenLogger (as explained in this tutorial, https://reference.digilentinc.com/learn/instrumentation/tutorials/openlogger/datalogger) the sample rate automatically adjusts. With 8 channels, the sample rate will be 62.50 kS/s, and can be decreased to a lower sample rate if that is more appropriate for your system. As for logging to an SD card via a different microcontroller, the process will depend; there is an SD library built into the Arduino IDE, but unlike the OpenLogger, it will not be logging analog data to the SD card in the same way with regards to logging data as the SD card as analog data is collected. With regards to turning the OpenLogger on and off, that will not be so easy to do. There is not a built in way to trigger the OpenLogger to reset itself (or send a signal out on a GPIO pin to the reset pin after 20 seconds), so you would need an external system (such as another microcontroller) to send this signal. But this would overall make the system less portable. Let me know if you have any questions about this. Thanks, JColvin
  25. Hi @Karsten, I have sent you a PM with instructions. Thanks, JColvin