• Content Count

  • Joined

  • Last visited

About OvidiuD

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, @Raghu0860! If you are using a lookup table I suppose you are iterating through it with a loop. In order to make your amplitude variable you can use a variable that should be added to the value you are getting from the lookup table. That variable could be controlled by buttons or switchs, for example. Good luck!
  2. Hello, @DaveG! I'll go pinpoint some observations that might help you with your issue: 1. I don't see the IP Digilent provides in your design. In order for Pmod DHB1 to correctly work you should use the IP provided by Digilent. Here is the tutorial for general Digilent IP usage. If you have actually followed the tutorial please tell mention this. 2. The source code files you attached cannot be opened. Could you please provide them so that we could open them? 3. Here you can find a reference project with something similar. Good luck!
  3. Hello @Shweta K R! About the app, you can use any generic BLE app as long as your phone supports BLE. You can just search BLE Terminal on the Google Play Store and pick one. Good luck!
  4. Hello, @tuskiomi! We do not recommend volatile memory through FMC as it is not feasible. DDR interfaces are slow when mapping differential routes and groups of FMC signals. In this context we do not have such product. What I'd recommend is a board that has SODIMM, like Genesys ZU Good luck!
  5. Unfortunately, I do not, but you can see the way OpenScope MZ and OpenLogger MZ are configured in the code and take those as examples. Good luck!
  6. OvidiuD

    Pmod BT2

    Hi, @Niharika! I'd be glad to help you with your project and I would need questions that are more punctual in order to do so. I would greatly appreciate if you would also tell me what files provided by us you read. Until then, I will give you some links that might help you: PMod BT2 Tutorials - The "Getting started with Digilent PMod IPs" tutorial could be a great start for connecting the BT2 PMod with your Nexys4DDR
  7. Hi, @zag! OpenScope MZ and OpenLogger MZ are compatible with WaveForms Live. You can add them through WiFi after you configure them through USB. The files used for WaveForms Live are open-source so you can add the device by yourself if you have programming knowledge. Good luck!
  8. OvidiuD

    ZedBoard PCAM

    Hi @elAmericano! I'm glad your project is working. I hope you will have good luck in your future projects. Thank you for signaling your issues! About the jumper; The project works fine without a 3.3V jumper. Mine is set the same way yours is in the photo you provided. About the IPs; In theory, the SDK should automatically add those drivers and select them for use, but it seems like a bug is stopping it from doing so. The generic driver means that you only have the read and write functions for the address where that component should be rooted. Specific drivers should be used and
  9. OvidiuD

    ZedBoard PCAM

    Hi again @elAmericano! It seems to be an issue with the SDK or the project. From what I see, the simplest way to solve your issue is to rebuild your project from scratch using the tutorial from the Readme file. It has been updated to include the extra steps I have given you. Don't forget to add the repositories as the note says. Keep us up to date with your progress. I'm very curious and hopeful! Good luck!
  10. OvidiuD

    ZedBoard PCAM

    Hello, @elAmericano! I have managed to solve the issue today: 1. Make sure you have an up-to-date bistream and export that to the SDK. 2. Right click on <project name>_bsp (in SDK's Project Explorer) and click on "Board Support Package Settings". There you should go to drivers and change the driver type from "generic" to their respective name for MIPI_CSI_2_RX, MIPI_D_PHY_RX and video_scaler component types(for all components of these types) if they are not already changed to their name. 3. Right click on <project name> and click properties. There, you should go
  11. Hi, @asmi! We have added support for Realtek PHYs in the 2019.1 lwip. You can find the updated repository here. You can download/clone it and add it in your project. Then: 1)From SDk's toolbar go to Xilinx, Repositories and add embeddedsw as a local repository as in the Step 1 screenshot attached(you can either add it with a relative path or a new absolute path). 2)In the project folder hierarchy go to echoserver, to embeddedsw and right click on it, click on Properties and in the C/C++ Build tab make sure the "Exclude resource from build" checkbox is checked(like in the S
  12. Hello, @asmi Having looked into it, it seems that there is indeed a problem with the Vivado project in Vivado 2019.1. While we are looking into it, one possible alternative is for you to use Vivado 2015.4. I've just tested the project on it and it works as described in the guide.
  13. Hi @aadgl! Here you can find the fixed release. Indeed there was a problem with the release you tried which were solved, but not released yet. The documentation has been updated, too. Hope this fixes your issues. OvidiuD
  14. Hello, @Victor! At a first glance, it seems that your warnings are cause by the fact that you have an undeclared or unpinned clock in your design. Don't forget that constraints are case sensitive. Let me know if you find the error or not, so I can help give you further assistance if needed. Good luck!
  15. Hello, @Antonio Fasano! A discussion that might help you is this one. Also, you can find examples of projects with the HDMI in and HDMI out on our GitHub. Also, you can find a more complex project that includes more complex things, HDMI processing included here. Good luck!