Cristian.Fatu

Technical Forum Moderator
  • Content Count

    132
  • Joined

  • Last visited

  • Days Won

    7

Cristian.Fatu last won the day on December 15 2017

Cristian.Fatu had the most liked content!

About Cristian.Fatu

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2544 profile views
  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 Readme.md file for the Vivado project is not right. We aplologize for this. You should download the release Zedboard-OLED-2016.4-1.zip (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 https://www.xilinx.com/products/design-tools/vivado/integration/sysgen.html, 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). https://www.dropbox.com/s/ark7wz4md7s6zod/sdlinux_Zybo.zip?dl=0 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: https://forum.arduino.cc/index.php?topic=104.0. 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. GPIO_demo.zip