jpeyron

Forum Managers
  • Content Count

    5327
  • Joined

  • Last visited

  • Days Won

    221

Everything posted by jpeyron

  1. Hi Notarobot, You need to add the board files as described here which has a link from a sub-section in the Prerequisites section of the tutorial. I have added a screen shot below. Hope this helps. cheers, Jon
  2. Hi Rappy Saha, The bit stream for the Genesys 2 needs a little over 11MB so it needs to be set at 12MB(0x00C00000). So the download.bit is stored from 0-12MB and the elf file can use the rest of the flash available. cheers, Jon
  3. Hi Jaaasooon, We have a few Zynq boards( Here, here, here and soon here). which one are you looking for weight and dimensions? cheers, Jon
  4. jpeyron

    Zybo Ethernet example

    Hi Piotr, Here is a thread that has some options for setting up a server on a zybo. Hope this helps! cheers, Jon
  5. Hi Niels00126, Here is a link to a web server using freeRTOS with Zynq. Here is a link using LightWeight IP Application Examples. You can also install Petalinux with a quick guide here. Here is a github repo about a web server for zynq. Here is a link that describes how to configure the BusyBox web server that comes with PetaLinux and create/install your own custom web content into the PetaLinux system image. Hope this helps! cheers, Jon
  6. Hi rappysaha, I went through the tutorial that JColvin link above with the Genesys 2 just now. For this project I did not compress the bitstream. I used the same offset as the Arty with success and updated the tutorial. The only difference to the getting started with microblaze project in you block design that you need to do is to add the quad spi IP along with adding a clock to the mig( used a roughly 45Mhz clock) ui_addn_clk_0 and connect it to the est_spi_clk on the quad spi IP as shown below. There are two flash memory options that fit Spansion S25FL256S choose 0. Also I will attach my project and screen shots as well. Hope this helps! cheers, Jon QUAD_SPI_Genesys2.zip
  7. Hi digizybo, I asked around and was able to figure out how to make custom ip's with the code that the instructable provided. 1) make an empty project for the zybo 2) add the code i.e. trigger_ip.sv to the project 3) go to tools and select create and package IP 4) select package your current project 5) select where you want the ip to be made and keep include .xci file selected 6) click on compatibility and select the family of fpga you would like it to work on or select all of them if you would like, life cycle beta. 7) click on review and package and click on package IP, click yes and at this point you have made a custom ip! I have included my files for the 2 different IPs and a project that has them in the block design. hope this helps! cheers, Jon trigger_ip.zip drp_controller.zip trigger.zip
  8. Hi Ronald, Here is a link for a quick start guide with Petalinux and Zybo. This should walk you though getting it up and going on your zybo. Hope this helps! cheers, Jon
  9. jpeyron

    PMod BT2

    Hi Graham1904, Looking at the schematic here it shows that on J1 pin 12 and pin 6 are tied to 3.3v which is what J2 pin 5 is tied to as well. J1 is as follows: pin 1 - RTS pin 2 - RX pin 3 - TX pin 4 - CTS pin 5 - GND pin 6 - VCC(3.3v) pin 7 - Status pin 8 - /Reset pin 9 - NC pin 10 - NC pin 11 - GND pin 12 - VCC(3.3v) J2 is as follows: pin 1 - MISO pin 2 - MOSI pin 3 - SCK pin 4 - /CS pin 5 - VCC(3.3v) pin 6 - GND I have included screen shots of J1 and J2 of the schematic. Hope this helps! cheers, Jon
  10. Hi martin, I was able to get the onboardOLED to work. I have attached the project. There are a couple of pins that are not tied to anything do to the difference between the PmodOLED and the onboardOLED. There are a two critical warnings about pin1 and 3 that continue throughout the vivado process that will not affect the project. The onboardOLED display is oriented differently than the PmodOLED so the print is upside down. Hope this helps! thank you, Jon genesys_2_oled.zip
  11. Hi martin, The screen shot above looks correct. You should not use the OLEDrgb sdk code there are some slight differences between the two components which could cause it not to work. I am in the process of trying to get the onboard working tonight. If you were just wanting to get the oled working ASAP you can use the Nexys Video OLED demo. You will need to use the Clocking wizard to convert differential clock to a single 100MHZ clk signal and then change the Nexys Video xdc to the Genesys 2 master xdc with the appropriate constraints as described in the xdc in the demo which is here. cheers, Jon
  12. Hi Loredana, I have updated and verified our github with the PmodRTCC IP. cheers, Jon
  13. Hi vvk, Have you looked here for possible solutions to this issue? cheers, Jon
  14. Hi mikearmagedon, I just checked with someone that is more informed on this topic and I was wrong about needing to use the ILA. Just use the onboard usb jtag debugger and the arm dap is in the scan chain automaticly next to the FPGA fabric. You should be to see this in the vivado hw manager. To debug code ect... you should be using SDK and it will automaticly detect the jtag interface and use it. cheers, Jon
  15. Hi Adam, The FMC part number is ASP-134603-01 and its mate is ASP-134604-01 Pmods are right angle female MTE connectors PPTC062LJBN-RC Hope this helps! cheers, Jon
  16. Hi reda9, First off, it looks like you are trying to constrain the same pins twice. So that would be one issue also could you post the errors that you are getting. thank you, Jon
  17. Hi mikearmagedon, The ILA works with JTAG so that is one option. Have you though about using the system debuger in sdk to debug you issues? cheers, Jon
  18. Hi Mazdarx2001, What version of the myDigital do you have? You can find the version on the bottom of the board. Looking at the schematic for the Rev E it shows that the VEXT and VREG are the only power pins that do not come from the myDAQ connector. So you would need to look at the myDAQ user manual/schematic to see what power pins pass through the myDAQ. I got a simular result when connecting a myDAQ without having it active. Without looking through the myDAQ manual/schematic I would guess that you would need to download and be using labview to use the +5V pin. Hope this helps. thank you, Jon
  19. Hi Sam, I sent you a PM about this issue. cheers, Jon
  20. Hi Aeneas, What OS are you using? Have you tried using an external usb hub? Are you able to see the board in the device manager? Are the drivers up to date? I found a thread with a similar error here. thank you, Jon
  21. Hi Branimir, Welcome to the forum! The Zybo is a great development board. cheers, Jon
  22. Hi zwabbit, The schematic ordering is what the pins are ordered on the board. In reference to the arty TMS,TDI and TCK are inputs to the arty and TDO is an output. thank you, Jon
  23. Hi ker_ouss, When I used the PmodBT2 with a microcontroller I used my computer to pair with the PmodBT2. I needed to be in a place with almost no bluetooth devices around to narrow down which one was the PmodBT2 then i pair the computer to the PmodBT2. Here is a demo using the nexys 4 with the PmodBT2 that might help you with transfering data. cheers, Jon
  24. Hi jgoglio, I have included the sdk files below. Most of the functions in PmodJSTK2.c are used in basic_example.c and calibrate_example.c. I would suggest to use a serial terminal(like tera term) and look at the output when using the PmodJSTK2 and you should be able to see how to interpret the output based on the joysticks position. thank you, Jon PmodJSTK2.c PmodJSTK2.h basic_example.c calibrate_example.c
  25. Hi Fernando, ISE is used to make a project and generate a bit file. You need to use Adept 2 to program the bit file on to the Basys 2. Yuo can download Adept 2 from here. cheers, Jon