Sergiu

Members
  • Content Count

    98
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by Sergiu

  1. Sergiu

    Adept DPTI support

    hello, have you looked at the projects from this location? https://github.com/Digilent/NexysVideo/tree/master/Projects/dpti Sergiu
  2. Hello @cgarry, Could you tee us what state is the "lock" signal is ? Is it also tied to an LED ? Have you looked at the examples from our reference page ? https://reference.digilentinc.com/learn/programmable-logic/tutorials/zybo-hdmi-demo/start Sergiu
  3. Hello, Using Vivado 17.4 I got the example to work with either 100 or 1000 mbps. I see a DHCP timeout in your post Please go to SDK in main.c and search for "dhcp_timoutcntr". You will find this variable set to 24. Please change it to 50 or 100 and try again. In some cases the counter expires before obtaining an IP and DHCP fails. You should also look in the MSS file (open with text editor) and search for " PARAMETER LIBRARY_NAME = lwip141". That is where the lwip settings are stored for the project. It should look like this: BEGIN LIBRARY PARAMETER LIBRARY_NAME = lwip141 PARAMETER LIBRARY_VER = 2.0 PARAMETER PROC_INSTANCE = microblaze_0 PARAMETER dhcp_does_arp_check = true PARAMETER lwip_dhcp = true PARAMETER phy_link_speed = CONFIG_LINKSPEED1000 END You can replace what you find with my settings (bolded lines) and then regenerate the bsp. Sergiu
  4. Hi You can use the AXI PS/2 IP core that you can find here. There is also a demo project for it here (made for the Nexys Video). The demo basically writes to a terminal opened on the PC whatever you type on the keyboard connected to the board's USB HID port. I am working on the wiki page for the demo project but for now you can use the IP's documentation to understand how it works. Sergiu
  5. Hello, Could you please provide more details regarding the problem? Also, please take a look at the following forum thread and see if it helps: https://forum.digilentinc.com/topic/4354-zybo-server-demo-phy-autonegotiation-fails/ Sergiu
  6. Hi, One way to start would be to take a look at the examples provided by Xilinx. You can find them at this location: C:\Xilinx\SDK\2016.4\data\embeddedsw\XilinxProcessorIPLib\drivers\uartps_v3_3\examples Or you can look at the "system.mss" file in SDK (bsp folder) and click on "import example". -Sergiu
  7. I am not sure that I understand, are you trying to power an arduino board from an FPGA pin like JC1 (K17) ?
  8. Sergiu

    XADC examples

    Hi. Have you seen this forum thread?
  9. Sergiu

    UART interrupt example

    The PS UART does have interrupt capabilities. Have you seen the UART interrupt example provided by Xilinx? I believe it will answer your questions. You can also find the controller's specifications in the Zynq reference manual page 583. Sergiu
  10. Well I'm glad to see that you got it going. Indeed that workaround should be included somewhere. Have a good day, Sergiu
  11. Well, err.h is part of the lwip library. I don't know how it can go missing. Have you tried regenerating the bsp? Is lwip correctly included in the bsp? I just ran the echo example on a zybo (2017.1) and I had no issues other than the CONFIG_LINKSPEED1000 parameter. I can send you the project if you want and you can compare it with yours. Sergiu
  12. Hi, I believe the problem is caused by the fact that the ethernet phy found on the Zybo might not be compatible with Xilinx's lwip. Therefore I believe the solution would be to set the speed manually (right now its on autodetect which I think is the part that fails). In order to set it manually please enter the following command in the XSCT console: configbsp -bsp <bsp_name> phy_link_speed CONFIG_LINKSPEED1000 --to set the speed configbsp -bsp <bsp_name> -lib lwip141 --to check if it's set regenbsp -bsp <bsp_name> --regenerate the bsp Sergiu
  13. Could you also specify the version of Vivado / SDK that you are using? Please go to the XSCT console and type in the following command and tell me what it says: configbsp -bsp <bsp_name> -lib lwip141 Sergiu
  14. Hello, The first thing I noticed is that you are not using the TKEEP bus which I believe is necessary for the DMA. Other than that, I noticed that you have not checked the "Allow unaligned transfers" option and because of that you will be restricted to 4 byte transfers (in case you are asking for different lengths). I recommend looking into these first since it is possible that this is causing the problems. Also I do not understand what you mean by 0.2 Mhz. Is that some clock frequency or did you want to say 0.2 ms/us/ns ? I would also recommend that you look at this demo project. Here I used the DMA to transfer data more or less the same way you are trying to do it so I think it will prove useful. Sergiu
  15. Sergiu

    Connect my IP module

    Hello, Looking at the schematic I believe your design should work. The problem could be the C code that you use to drive the AXI GPIO. Have you looked at the examples provided by Xilinx ? I would also recommend that you use the Logic Analyzer too look at the signals or you could connect the AXI GPIO directly to the LEDs and see if the value changes. Sergiu
  16. Hello, Since 40 / 15 = 2.(6) which is not an integer, you will have to divide by 8 (to get 5) and multiply by 3, which is exactly what the MMCM does. Dividing by 8 is easy however multiplying the frequency is not and I am not sure that it is even possible. Here is a trick used for doubling the frequency however the signal it generates does not have a 50% duty cycle which can cause problems later on. http://vhdlguru.blogspot.ro/2010/04/combinatorial-frequency-multiplier.html My advice, use the MMCM. Sergiu
  17. Which UART IP are you using ? Could you send a screenshot with your block design ? Did you configure the IP in any way other than default ?
  18. Hello, Is the board powering on? Is it recognized by the computer (device manager) ? If the board is working properly then it may be a software issue solved here. Sergiu
  19. Hello, There are a few things I want to make clear (with the risk of repeating some of what D@n already said) First of all there is the development platform a.k.a. the Xilinx Vivado which will be used to create projects with. This comes in several packages out of which the Webpack Edition is free and quite powerful in recent versions. It will allow you to write code, simulate, debug, program the boards and integrate IP Cores. You can download the software from the Xilinx website. Then there are the IP Cores and other reference material. Some are provided by Xilinx for free (microblaze, MIG, ethernet etc) and some are only available for purchase/trial. Digilent also provides reference material, manuals and demo projects, all for free, available on our wiki or github channel. A good place to start would be the Nexys Video wiki page. In short, at this level, most of the stuff is free and available. Demo projects like the one for the Nexys Video are created to use as many peripherals as posible. In any case if you run into any trouble just come to the forum. Sergiu
  20. I attached two photos that show where JP6 is located. Simply move the blue jumper to select the desired voltage.
  21. There is a jumper block on the board called JP6 which allows you to choose between 3v3 and VSWT (5v).
  22. Hello, Here is what the reference manual says: PS/2 Port The 6-pin mini-DIN connector can accommodate a PS/2 mouse or keyboard. Most PS/2 devices can operate from a 3.3V supply, but older devices may require a 5VDC supply. A 3-pin jumper on the immediately adjacent to the PS/2 connector selects whether regulated 3.3V or the main input power bus voltage (VU) is supplied to the PS/2 connector. To send 5V to the PS/2 connector, set the PS2 power jumper to VU (the main input power bus), and ensure the board is powered from USB or a 5VDC wall-plug supply. To send 3.3V to the connector, set the jumper to 3.3V. https://reference.digilentinc.com/reference/programmable-logic/genesys/reference-manual Sergiu
  23. The chips function in the same way. You can use the information provided in the reference manual / schematic in order to configure the MIG. Sergiu
  24. Hello, This issue was discussed before on the forum. https://forum.digilentinc.com/search/?type=all&q=debug+hub You can find the answer here. Sergiu
  25. Hi, That's good news. I'm glad it worked. Sergiu