Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Cristian.Fatu

  1. Hello, We are happy that you enjoy Zybo Z7-20 board. The heatsink part is Malico BHBH3119191300-07.
  2. Hello, Please check to have the POWER jumper (JP2) set to USB and the POWER switch (SW16) set to ON.
  3. Hello, I can't give you more details about Multisim, still your question seems to me to be independent to Multisim. You should take a look in the constraints file (xdc) which is specific to each board. Here you can find more details about Vivado constraint files. Here you can find the Nexys 4 DDR constraint file. Please tell me if I can give you more details.
  4. Solved, wrong JP3 jumper configuration.
  5. Hello, We found this part number: CSD-11-A0000. In case you want to look for alternates I am sending in a message the component datasheet.
  6. I wrote you a message requesting more details about this problem.
  7. Hello, Nexys 3 being a Spartan®-6 FPGA board is not recognised by Vivado. So you should focus to the ISE related materials from Pmod OLED resource center page: Nexys 3 Verilog Example - ISE 14.2 Nexys 3 VHDL Example - ISE 14.2 Still, here is an answer to your question: Unfortunately the information from file for the Vivado project is not right. We aplologize for this. You should download the release (click on "1 release"). In order to create the project, you should run in vivado the create_project.tcl script (after changing directory to proj). Good luck.
  8. Hello, We have never used System Generator on our boards, therefore we cannot confirm that it is working. Still, looking on the Xilinx product page, you can read:
  9. Hello, We have booted using the bsp you specified. We have used external power (and suggest you to do so), having set the JP5 to REG. The dmesg messages seem similar in our case to the ones you posted. Also, the first item listed by lsusb is identical to yours. Obviously we cannot plug the USB device you use (class-compliant MIDI device). We have tried an USB Flash drive, properly recognized as mass storage device. So, everything seems to be OK on our side. Please read chapter 8 (USB Host) from the reference manual. There are some details about how the USB port behaves. Maybe this is useful for you.
  10. Hello, There is no need for SPI in communication with Pmodi2S2. Indeed, PmodA pins of BasysMX3 can be configured as SPI2. But its pins can be also configured as general IO pins, so it could be possible to implement an IO driven communication over I2S protocol. Still, I consider that this is not feasible under decent quality, because: - Unlike FPGA boards (which are the main target for PmodI2S2), the BasysMX3 board being a microcontroller board cannot provide high frequencies needed for MCLK. - The MCLK and SCLK should be exact clocks (having a certain division factor), which is hard to achieve on BasysMX3 board. If you still want to try to use the Pmodi2S2 maybe you should consider using a FPGA board and look at the example posted on Digilent website: Pmod I2S2 FPGA Volume Control Demo.
  11. Hello, I post some information about the OOB QSPI demo. We actually don't load the SPI flash using an MCS file, we copy the needed files using Linux manually. Use the linked package to load the QSPI back to default state. Place these files on a micro SD card and boot the ZYBO with it. After ~4 minutes, the QSPI will have been programmed with the default image (there will be some terminal output indicating what is going on). Good luck.
  12. I assume you use Windows. In order to know which COM port to choose, please take a look in the Windows Device manager before and after you plug the USB cable. You should see something like this: The standard Pynq image is communicating at 115200 baud rate, so if you use this image you should setup the terminal at this baud. This is how my Terra Term looks after booting: Good luck.
  13. We are discussing this issue on the Digilent technical support channel.
  14. Hello, I jump in this discussion just to note that Arduino Uno provides, in the POWER bank pins, a "3.3 V" pin. So I am thinking (without too much knowledge) that this could be used to solve at least the power of the connected Pmod. Still, you should be concerned if this pin provides enough power for your Pmod: I also note that Arduino Due has 3.3 V IO logic level. Good luck.
  15. Hello, We consider very important, prior to deciding that the board is defective, to run one of our projects that will proof that the buttons are running or not. We have created a very simple project that simplifies the GPIO demo by just connecting the push buttons to the LEDs. I am sending you the bit file for your A35T FPGA, please open hardware manager, connect to your board and program the bit. Press buttons, and you should see the corresponding LED lit. Depending on this result, we will continue the Technical support issue you just open.
  16. Hello, In the resource center we provide a library pack:, to be used with MPLAB X. It provides two modules for UART, located in the corresponding .c source files: uart.c provides UART functions to be used with USB - UART interface. uart_jb.c provides UART functions to be used over pins from PMOD JB connector. We also provide an UART demo. Please take a look, maybe use the library or at least use the code as an inspiration (UART initialization steps from UART_Init functions, for example).
  17. Cristian.Fatu


    As mentioned by Dan, you can also use Adept application to accomplish this task. The other option is to use Xilinx tools. Adept has the advantage of being able to use the bit file, while Xilinx tools (iMPACT) requires the step of creating the mcs file. Still, our advice is to try to use the iMPACT, as this is the recomended Xilinx way. So please try to use the tutorial that Bogdan just sent.
  18. Even if this seems to be a very old topic, I post some information related to it. The following link reveals a wrong line in the defines of the example project xuartps_intr_example.c of 2016.4 version (posted by K_Ashish). Changing from XPAR_XUARTPS_1_INTR to XPAR_XUARTPS_0_INTR makes the critical difference between wrong and right.
  19. Hello, I am trying to provide some answers on this matter. For the first question: You can connect any number of Pmods, as long as you have proper available Pmod connectors. What I mean by "proper" is that you should check the needed pins functionality for a Pmod. As James was saying in this answer, you might need hardware SPI or I2C communication. And only some specific PIC32 pins provide this. You can check to which Pmod connector pins they are routed in the board reference manual, usually in the appendix at the end of document. For your example: So, take the needed Pmods one by one and try to find a place where to plug them. Related to the software, include each Pmod library in your project. You might need to change the hardware interface number: for example the Digilent library implements access to hardware interface SPI1, while you need access to hardware interface SPI2. This is not difficult. For to the second question: Yes, you can use any cable to connect pin to pin from the Pmod connector to the Pmod itself. Of course, if you are interested in high speed, this can come with a cost. But most of the time, high speed is not an issue. In fact, Digilent even provides such a cable: You can find some more details of the Digilent Pmod specifications in this document Interface_Specification.pdf. Related to mechanical dimensions: yes, would be nice to have them on the website. Until then, we are providing them upon request. Good luck.
  20. As James answered, unfortunately you can't use the library as it is. For example, if you take a look in Oled2Driver.cpp, you will notice that it uses PIC32 register names. But maybe this library can be used as a starting point if you want to build your functionality. See how Microchip PMP (Parallel Master Port) is used and you can build your own functionality to access OLED2. The library is rather complex, as it also implements character generator, some graphic directives. Still you can focus only on the part you are interested.
  21. Regarding the specific errors you mention, we tried to create a simple helloworld application (which just includes <stdio.h>). Although the eclipse highlights “Unresolved inclusion: <stdio.h>” (similar to the situation described by you), the project builds without errors, and the C/C++ Build Settings (right mouse option on project) identifies the linux compiler arm-linux-gnueabihf-gcc. The conclusion is that this might be just an eclipse issue. Creating a linux application is a complex task, more difficult than creating a standalone application. There are several tutorials available on the Internet of how to handle Linux applications in SDK. Also, please read Apart from Linux approach, we direct you to some tutorials for understanding basic concepts of Vivado / SDK. Please start with the following tutorial, which guides you through the process of creating the Block Design (in Vivado), export the hardware to SDK: Also, you can read the following tutorials / wiki pages: Good luck.
  22. The last version of VmodCAM is rev. C. Anyway, this example is the only one we have, so try to use it "as it is". When you add new questions, please add new posts, as editing the previous posts is not a good approach because existing answers seem to "float" over replaced questions.
  23. Yes, it is stereo vision implementation. Please read the documentation inside the zip file to find more, as I know very few about this project.
  24. Hello, Hoping that this might help you, I am sending you a demo application. It is a 3D Vision demo, based on VmdoCAM. Please note that this demo was not released, so it is not "polished". Camera Demo Good luck!
  25. In these days when a lot of perfectly working boards are just thrown away because they are obsolete, I think we should admire and encourage the "effort" of using these old (but unused) boards. I think that some more details can be useful on this matter. This is a Xilinx board, meaning that it was engineered by Xilinx and only produced by Digilent. It is based on Spartan 3 FPGA XC3S200, which is very old and, comparing with up to date FPGAs, not very powerful. But is more than enough for small applications or for learning VHDL or Verilog. On PC side, in order to generate the programming file (bit file), you need Xilinx tools ISE (as mentioned in the above messages). In order to program the bit file on the board, you need a programming cable. On the PC side it will be connected to USB, on the board it will connect to JTAG connector J7 (1x6 pins). Please read more about this mater on the page 41 of the board's user guide An example of such a cable is Digilent HS2 On the other hand, let's look from the other perspective: You should be aware that the current direction of Xilinx tools is to move towards Vivado, so using this "ancient" board you lose the possibility to learn Vivado. If you are student or your work is related to academia, almost at the price of the Digilent HS2 you can get all the Basys3 board This relies on the Artix 7 family FPGA, is up to date and also doesn't need a programming cable. Good luck !