• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @manboy, I asked another engineer more familiar with the Pcam about this. Thanks, JColvin
  2. Hi @BT12, I apologize for the delay. Our projects that we have for the Genesys ZU on our GitHub, https://github.com/digilent?q=genesys+zu&type=&language=, are designed to work with 2019.1, not 2018.2, though the board files should not be picky about the Vivado version. What errors do you get in the during the Run Block Automation process? And what Xilinx evaluation board are you referring to? Thanks, JColvin
  3. Hi @ennegi, I apologize for the delay. My understanding based on the ESP32 reference manual, https://reference.digilentinc.com/reference/pmod/pmodesp32/reference-manual, is that the program loaded on it is AT Instruction Firmware, which is set up in slave mode that sets the top row of pins to UART. To use the pins as a SPI header, you would need to load custom firmware that makes use of this SPI header. Updating this firmware is somewhat described on this ESP32 forum thread here: https://esp32.com/viewtopic.php?t=5136. Digilent doesn't have any custom firmware that we have created for the module. Let me know if you have any questions about this. Thanks, JColvin
  4. JColvin

    ZYBO LED demo not working

    Hi @mainak, I would instead use the Pmod GPIO IP, https://github.com/Digilent/vivado-library/tree/master/ip/Pmods/PmodGPIO_v1_0, since the tutorial you linked is for WS2812 styled LEDs, not the on-board LEDs or the Pmod 8LD. The on-board LEDs you can control through the block design as explained in this tutorial here (or through HDL). The tutorial you linked is also for the original Zybo and not the Zybo Z7-10 which are different boards and will have different pinouts. The reason you do not find launch SDK is because Xilinx got rid of SDK in favor of Vitis starting in 2019.2. The second tutorial I linked walks you through how to use Vitis instead. Let me know if you have any questions. Thanks, JColvin
  5. Hi @idraney, We don't have a direct examples, though you could look at the preset for the Cmod A7 board file to see what what is specifically done there: https://github.com/Digilent/vivado-boards/blob/master/new/board_files/cmod_a7-35t/B.0/preset.xml. Thanks, JColvin
  6. Hi @g3333t, It is possible to do this. You would need to do some networking to get this set up though. One option would be to open a port on your router and then forwarding the traffic to the OpenScope MZ. At that point you would just need an address that is accessible via the internet at large which you put into WaveFormsLive when connecting via network, which will be dictated by your ISP. Alternatively, you could set up a VPN connection between your remote computer and a VPN server on your home network that has the OpenScope MZ/WaveFormsLive available and SSH into it, but that would be a bit more work to get going. Thanks, JColvin
  7. Hi @Tim S., I have passed your feedback on to the engineers who handle our GitHub material. Thank you, JColvin
  8. JColvin

    liblinxdevice dll

    Hi @Rcam, I don't know where the source for the .dll is or where it might be. However, LabVIEW 2020 Community Edition should work just fine with the WF32. I just ran a VI on the WF32 with the Pmod TMP3 VI. I had to use the LINX Firmware Wizard first to configure the board to be able to talk to LabVIEW in the first place, but it otherwise worked without issues. The only way that I am aware of for a buffer of values/commands that could be sent would be to create a Custom Command (https://www.labviewmakerhub.com/doku.php?id=learn:tutorials:libraries:linx:misc:custom_command_example) where you effectively send out N pieces of data and the receiving board parses those different incoming values as different types of commands to execute, probably via a switch-case setup. Thanks, JColvin WF32_TMP3.vi
  9. Hi @manboy, If you want to use a Pmod port you would need some sort of level shifter; it doesn't have to be the Pmod level shifter (Pmod LVLSHFT), but it would work for translating the voltage from 3.3V to 1.8V. Vivado will probably complain that about those IO pins suited for clocking, but I believe it should still work at 24 MHz. I would probably use one of the differential Pmod headers (JC or JD) as they do not have series resistors to hinder clocking speed. Alternatively, there are some clock pins on the FMC header (which will also support 1.8V via the VADJ jumper). Let me know if you have any questions about this. Edit: Though it looks like zygot responded a few minutes before I did with very similar information. Thanks, JColvin
  10. Hi @Tim S., Thank you for sharing this project! Do you mind if we link to this post as a community project on different Digilent Wiki pages, such as on the Zybo Z7-20 and Arty A7 Resource Centers? Thanks, JColvin
  11. Hi @Goodbye, I apologize for the delay; to clarify, you are inquiring about the material on the FTDI chip downstream of the microUSB port (J13)? Or the USB HID port and it's PIC24 (J15)? Presuming it is the first one, there is not a way to change the firmware through Vivado or installed Digilent plug-ins, though it is very possible to overwrite the EEPROM on the device with FTProg and cause it to no longer be recognized as a programmable device by iMPACT or Vivado. Thanks, JColvin
  12. Hi @erikS, In case you haven't tried it, I would also suggest trying a different USB cable in case the one you are using doesn't support data. I know I've picked up random USB cables around my house thinking they'll work fine (because why wouldn't they) only to find after 30 minutes of fighting with drivers that I was using a charging only cable. Thanks, JColvin
  13. Hi @GreenbackBoogie, I have sent you a PM about this. Thanks, JColvin
  14. JColvin

    Zybo audio demo

    Hi @bm0383, I apologize for the delay. I am taking a look into this since I am getting the same error when running the release version for the Zybo Z7-10 (which uses the same SoC) on Vivado/SDK 2018.2. Thanks, JColvin
  15. Hi @erikS, How are you powering your board? Are you powering it through the microUSB port or are you using an external power supply? Are you able to detect the FTDI chip in either the Windows Device Manager (it would be listed as USB Serial Converter A under the USB controllers dropdown) or on your Linux machine? Thanks, JColvin
  16. Hi @Fabian123, I'm sorry to hear you are not able to get the examples working as expected. Which specific projects were you attempting to get working? Most of our release projects on the Digilent GitHub from 2018.2 onwards do not use .tcl scripts to build the projects (.tcl scripts were used for earlier versions of Vivado). A number of our projects have been updated to 2020.1, though not formally released since the documentation is not complete yet (they are in the staging branches on our GitHub, https://github.com/digilent, rather than as a release) I wouldn't necessarily say that 2017 and 2018 versions are hopelessly outdated; they just aren't the newest versions. Additionally, based on Xilinx's Release Notes Vivado 2020.1, Ubuntu 2020.04 LTS is not a formally supported OS; I'm not sure if this would contribute to any errors you are seeing though; that would be more of a question for Xilinx in terms of compatibility. Let me know if you have any questions. Thanks, JColvin
  17. Hi @Ztf, I'll be honest in saying that I didn't know that we had this demo on our Wiki page, so I'm not sure if anybody has specifically run this demo besides in the 2016.2 for which it was originally created. I'll have to re-install my own 2016.4 installation to test this since I now get an error when attempting to generate a bitstream for any project. Thanks, JColvin
  18. JColvin

    liblinxdevice dll

    Hi @Rcam, From my understanding NI did all of the migration and work involved from LINX 2014 to LabVIEW 2020 Community Edition, so I'm not certain what boards are compatible with the new . The liblinxdevice.dll that was used with LINX 2014 is available on Digilent's GitHub here: https://github.com/Digilent/LINX/blob/master/LabVIEW/vi.lib/MakerHub/LINX/Resources/liblinxdevice.dll. Thanks, JColvin
  19. Hi @Ravi Kumar, Yes, the BNC Adapter is physically compatible with the OpenScope MZ. The only main pin difference is that the OpenScope MZ does not have a second Waveform Generator, so note the dedicated BNC on the adapter has not been specifically designed for the INT/CLK1. Thanks, JColvin
  20. Hi @jjohnson5253, Thanks for posting this; it looks like one of Micron's pages when you search "N25Q256A" also leads to that same 404 page. I imagine you got the link to that pdf from this page: https://www.micron.com/products/nor-flash/serial-nor-flash/part-catalog/n25q256a83esfa0f, which is in their legacy product listing (as the part is EOL). I will find out what part is currently being loaded so I can make sure our reference materials are updated. Thanks, JColvin
  21. Hi @Iceman2020, I ask for these materials for you. Thanks, JColvin
  22. Hi @trayres, You are correct in that the LWIP doesn't readily support Realtek devices, though I do not why this decision was made on Xilinx's end. You can view a couple of threads about this error on the Xilinx forum here and here as well as a discussion on the Xilinx GitHub here where extra material to support other PHYs was offered to be added, but declined anyway. I know that Digilent did make an update to more readily support Realtek PHY's for 2019.1 as mentioned in this specific post here: https://forum.digilentinc.com/topic/18837-ethernet-on-genesys-2-board/?do=findComment&comment=53349; the post was for the Genesys 2, but will also apply to the Nexys Video. Thanks, JColvin
  23. Hi @Ron H, I'm not certain what the issue might be at the moment, I will need to look into it some more. Thanks, JColvin
  24. Hi @Royi, I am not aware of any issues with mixing processors on the JTAG side. Thanks, JColvin