• Content Count

  • Joined

  • Last visited

Everything posted by JColvin

  1. Hi @Marty, The answer depends on how determined you are to use all of the predesignated SPI pins that are available on the WF32. Base on how the SPI library is implemented, you can use any number of GPIO pins without needing to directly implement them as part of the SPI library commands; you just need to raise and lower the CS logic level as appropriate. With that in mind, you can probably use upwards of 10 modules without any issues. The main two issues that you will run into will be the power requirements for running a lot of modules and the amount of data that you can receive with
  2. Hi @Rich, Unfortunately, I don't think such a table exists for Digilent's microcontroller boards; part of the reason for this is because even if the microcontroller does not have a Pmod host port, you can still individually wire the pins from the Pmod to the microcontroller, utilizing either dedicated communication pins for the appropriate protocol (SPI, I2C, etc) or bit-banging out the appropriate protocol on a GPIO pin. In general though, all of our non-FPGA boards support all of our Pmods (with exception of perhaps the Pmod VGA which would require faster signaling than our microco
  3. Hi @s.schwarzbauer, Unfortunately, we do not have a 3D model of the Cmod S6. I can try to get some of the dimensions that you would need for your model, though know that they would just be measurements that I personally took with calipers and not a more formal set of dimensions. Which dimensions are you looking for? Thanks, JColvin
  4. Hi @parvy, No, I don't think anyone at Digilent was aware of this since (I believe; I wasn't at Digilent at the time) we developed this board (Spartan 3A/3AN) for Xilinx, but from my understanding did not sell it ourselves. We also do not have the ability to update the source for the user guide as that was also created by Xilinx, but I'll be sure to direct future users to this bit of information as well. Thank you, JColvin
  5. Hi @mustafasei, To update the firmware on the board, go from the Tools tab at the top of the LabVIEW GUI -> MakerHub -> LINX -> LINX Firmware Wizard to load the appropriate firmware onto the Arduino Mega. Let me know if you have any questions about this. Thanks, JColvin
  6. Hi @tekson, None of the Digilent employees have used either of those boards so we don't have any direct advice. It looks TI has a demo for using the DLP board with the Beaglebone boards. It may be good to reach out to TI to see if they have some recommendations on getting their mini projector working with a Xilinx SoC. Thanks, JColvin
  7. Hi @ArisBock, The JTAG HS3 will show up in the device manager as a USB Serial Converter with a Device Description as a "Digilent USB Device". You can also see if our Adept software sees the JTAG HS3 module. Let me know if you have any other questions. Thanks, JColvin
  8. Hi @Ria Nouwen, I have contacted the appropriate people at Digilent about this. I also removed your address from this post so it wasn't publicly visible; I imagine you will receive a contact via email to the email address you are using on the Forum from them. Thanks, JColvin
  9. Hi @mortuzahasan, If you are just looking for a module that goes from a micro USB to Xilinx's 14-pin JTAG header, the JTAG HS2 will likely be what you are looking for. Thanks, JColvin
  10. Hi @kursatgol, The module arrived yesterday afternoon. Our design engineer was able to get it to detect and program Zynq and other 7-series devices on a Windows 7 machine, but was not able to get it working as of yet on a Windows 10 machine. I will ask about Linux systems as well, though I do not know if they have any distribution readily available to them or not. Thanks, JColvin
  11. Hi @Caleb, Oh and if you have not done this already, you will need to manually install the Digilent Cable Drivers for your Linux system since that is not done by default. Xilinx has an answer record on how to do this here: https://www.xilinx.com/support/answers/54382.html. Alternatively, there is a different answer record with some more details on the process here: https://www.xilinx.com/support/answers/59128.html. Thanks, JColvin
  12. Hi @Caleb, The part you need now is to open up the Hardware Manager (you can see it on the left hand side of the screen under "Program and Debug" under the Generate bitstream. You'll then choose to connect to a target (have Vivado Auto-connect to find it) and choose the bitstream file which will be stored (at least in my Winoidws machine) in FileWhereProjectIsStoredProjectName.runs\impl_1\ModuleName.bit. This is shown in more detail starting in step 25 in this tutorial, as well in section 9 of our Getting started with Vivado Guide here. Let us know if you have any other questions.
  13. Hi @kursatgol, If the module did not arrive this past Friday (June 8th), I would expect that it should arrive in our office in the by June 13th at the latest, though to be fair, like other things, we don't have have control if there are any shipping delays, but I am hoping this will not be the case. Thank you for your patience, JColvin
  14. Hi @Marty, So I can better understand your environment, are you using a WiFi demo that is part of the Arduino IDE with the Digilent Core, or are you using something else such as LabVIEW MakerHub's LINX? Thanks, JColvin
  15. Hi @Marty, As you likely saw, any shield that is compatible with the Digilent Uno32 or uC32 (and generally physically compatible with Arduino Uno form factor boards) will be able to work with the WF32. I am not aware of the WF32 becoming retired anytime soon; I think what you are seeing is that the Digilent microcontroller boards are not as popular as some of our other product lines. Let me know if you have any other questions. Thanks, JColvin
  16. Hi @rpickeri, As a confirmation, you have a successfully booting petalinux project after the clean install from your other thread here? Thanks, JColvin
  17. Hi @nasajohnc, I learned that the DDC portion of this project is not necessary for this demo to be operational. My understanding, as it looks like you are aware of as well, is that it's to provide the controller with some information so that ideal timing can be created, but if you have provided the proper timing in other ways, you should be good to go without it. Thanks, JColvin
  18. Hi @Mahdi, I'm not certain what you are referring to when you say dividing the JTAG ports between Pmods since none of the Pmods you mentioned use JTAG, but we have on post on our Forum here that discusses how to get two 6-pin Pmods attached and running to the same port on the FPGA here: https://forum.digilentinc.com/topic/8795-connecting-two-6pin-pmods-to-12pin-connector-in-ip-integrator/. Thanks, JColvin
  19. Hi @parvy, The jumper settings look correct to me, so I'm not certain what the issue might be. The only thing that I can think of at the moment to try would be to switch J1 to the top half of the pins rather than the bottom half. The reasoning for this is that only one SPI flash can be used at a time (based on page 91 of the user guide) and looking at the schematics which I finally found available here https://www.xilinx.com/support/documentation/boards_and_kits/s3astarter_schematic.pdf, they show on page 13 both jumpers loaded horizontally for STMicro, which doesn't match the user guide,
  20. Hi @Hajime, In general with SDK projects, you will need to use the version of Vivado and SDK listed in the project Wiki here: https://reference.digilentinc.com/learn/programmable-logic/tutorials/nexys-video-hdmi-demo/start, so you will need to use 2016.4 in order for the project to work as is without re-creating and debugging any errors that can potentially come up in a different version. Thanks, JColvin
  21. Hi @[email protected], The demo that we have is dedicated towards the Microchip WiFi chips that Digilent has on our microcontroller boards and WiFi modules, typically a MRF24 based chip, so it has not been tested to work with an ESP8266 module and hasn't been setup to use the AT commands. Additionally, the MRF24 chips are SPI based rather than UART/Serial based like the ESP8266 module. Thanks, JColvin
  22. Hi @kursatgol, The modules that we had locally at the office weren't reliably working so we have requested a new one to be sent so we can get some accurate information about it. Thank you for your patience, JColvin
  23. Hi @stchanthony, Unfortunately, Digilent does not do any modifications for our boards, so we would not be able to change that chip for you. Since all the pins match (as you likely already knew) you can make a direct placement of the chip. I think it will in be fairly straight forward to solder and desolder though; the plastic is close to the chip, but it'll be ok since that's just the housing for the terminal inputs. Let me know if you have any more questions about this. Thanks, JColvin
  24. Hi @Kshitika, If you are set on using the NI myRIO, I would recommend posting on the NI Forum here for some better recommendations for a controller as we have very little experience with the NI myRIO. Thanks, JColvin
  25. Hi @Hajime, What version of Vivado and Xilinx SDK are you using? Thanks, JColvin