• Content Count

  • Joined

  • Last visited

Posts posted by elAmericano

  1. Additional:

    I compared 2018 and 2020 project.

    In 2018,

    • Ising SDK, I am finding supporting C-files and main script which clearly should be driving the peripheral devices attached to Zynq.


    In 2020 project:

    • I did not find "main.c" file.
    • I am using Vitis (not SDK in 2020)
    • Going form Vivado to Vitis, the hardware only outputs drivers for
      • AudioStream_PWM,
      • rgb_led,
      • user_io. 
    • I don't have exported hardware for
      • intc.h, dma.h, and verbose.h
      • These were referenced in 2018 sdk main.

    I have attempted to copy these "missing" resources from 2018 to 2020 project to resolve (bandaid for why these are not outputting), but couple values "AUD_NR_SAMPLES" and "AUDIO_MEM_ADDR" are now preventing me from compiling and I'm not 100% sure what these should be set to yet.


    Attached are copies of main.c and the addresses on ps7.  Can you please provide some feedback on suggested next steps?






  2. Hello 

    Out team has downloaded this project "out of box" from your github site.  https://github.com/Digilent/Arty-Z7-20-OOB/blob/master/README.md

    We are using Artix Z7-20 board, Vivado 2020.1 and Vitis.  We are able to generate the bitstream, export the hardware, configure platform / application and program FPGA. 

    After doing so, and running the "Hello World" application, the HDMI-In and Out are both working.  We see "Hello World" printed on teraterm console so seems to be functioning.

    However, buttons and switched are not having any effect on board LEDs.  The RGB are not cycling colors, and audio output is not heard on headphones when button is pressed.

    Can you clarify if there are any additional modifications needed to do (not outlined in readme) to make function as described?










    I have had OV7670 design working on older Spartan design that would like to bring into ArtyZ7.  I had purchased from Digilent some Z7 boards to get started with upgrading some of our designs.  

    I seem to have some difficulty to convert the RGB data to HDMI output.  I believe issue is with HDMI VHDL, specifically looks like timing.  The HMID output is attached.   When I move object near and far from camera, I can see changing intensities in the "noise".   

    OV7670 is running at 25MHZ/50MHZ clks.  I am using 125MHZ for the HDMI - out module to convert the RGB data to tmds.  Also attached is overall structure of project in vivado 2020.

    Appreciate any feebback or suggestions.  The goal here is to just get the OV7670 (RGB) to HDMI output from which we can start.





  4. Hello,

    I am working with Artix A7 board, implementing various PMODs successfully.  I am having some issue with PMOD-ESP32 unfortunately.

    The source files from a project off github (ESP32.c/ESP32.h) from https://github.com/mitchellorsucci/PMODESP32 as well as the included libraries (PmodESP32.c/PmodESP32.h)

    GitHub Project:

    I believe the following macros need to be re-defined in the ESP32.h file from github, however in XILINX project for Artix A7, there is a uart-lite that is connected via AXI and there is a uart connected to the ESP32 IP.  I have tried to define both.  When I define this as the uart-lite device ID, I get some output on console, but I cannot successfully connect to WIFI (which makes me believe the AT commands are being sent to AXI-UART , but not to ESP32 device uart).   When I define uart_device as ESP device, nothing prints to console terminal.    Please let me know if you have any suggestion.



    When I try to use the PmodESP32.h / PmodESP32.c included with IP, I am also not able to succesfully communicate with device.  I basically do the following

    1. ESP32_HardwareEnable(ESP32);
    2. ESP32_Initialize(ESP32, u32 UartBaseAddr, u32 GpioBaseAddr);
    3. ESP32_HardwareReset(ESP32);
    4. ESP32_SendBuffer(ESP32, u8 *buffer, u32 count);

    The commands i try to send are for connecting to WIFI and for configuring TCP, the functions return 0, which i understand means not succesful. I have reconfigure some of the functions from the github project to work with PmodESP32.c/PmodESP32.h files (the github project uses a UART only devicePtr, whereas the included PmodESP32 files have GPIO / UART structure).  


    int set_wifi_mode(PmodESP32 * devicePtr, unsigned int mode) {
        u8 tx_buf[50];
        if(mode > 3) {
            xil_printf("Mode %d is not supported for setting the WiFi mode\n\r");
            xil_printf("Please Use Modes:\n\r");
            xil_printf("\tNULL_MODE\n\r\tSTATION_MODE\n\r\tSOFTAP_MODE or\n\r\tSOFTAP_AND_STATION_MODE\n\r");
            return XST_FAILURE;
        sprintf(tx_buf, "AT+CWMODE=%d", mode);
        ESP32_SendBuffer(devicePtr, tx_buf, strlen(tx_buf));
        return XST_SUCCESS;

    int get_current_AP(PmodESP32 * devicePtr) {
        u8 tx[] = "AT+CWJAP?";
        ESP32_SendBuffer(devicePtr, tx, strlen(tx));
        return XST_SUCCESS;

    int set_current_AP(PmodESP32 * devicePtr, char * ssid, char * pwd, char * bssid) {
        u8 tx_buf[100];
        sprintf(tx_buf, "AT+CWJAP=\"%s\",\"%s\"", ssid, pwd);
        if(bssid != NULL) {
            int cursor = strlen(tx_buf);
            sprintf(tx_buf + cursor, ",\"%s\"");
        ESP32_SendBuffer(devicePtr, tx_buf, strlen(tx_buf));
        return XST_SUCCESS;

    int list_available_APs(PmodESP32 * devicePtr, char * ssid) {
        u8 tx_buf[100];
        sprintf(tx_buf, "AT+CWLAP");
        if(ssid != NULL) {
            int cursor = strlen(tx_buf);
            sprintf(tx_buf + cursor, "=\"%s\"", ssid);
        ESP32_SendBuffer(devicePtr, tx_buf, strlen(tx_buf));
        return XST_SUCCESS;


    ESP32.c ESP32.h PmodESP32.c PmodESP32.h

  5. Hello,


    Yes, I somewhat anticipated this response.  The company i work for would be interested in such a boot strapping design.  If there is some NDA we could have signed, or some other recommended pathway than starting from scratch, I would appreciated.  I have done this in the past with Spartan -3 design , and would like to avoid doing again :) very tedious stuff.


    Best Regards,


  6. Hello,

    I am working with Arty A7 and Arty Z7 dev boards with various PMODS building up a platform for imaging readout.  While these are useful getting started, I will soon need to roll out a board with some customized routing. 

    I notice many of the schematics and design files are shared in pdf.  Are any of these schematic/layout files avialble in Altium for boostrapping some of these custom designs off the open source boards?  This would really help accelerate FPGA design projects.  I noticed Altium has some open source daughter boards, but this would be a better solution.

    If these are not open source, please let me know, I may be mistaken.  If there is some kind of availability, please let me know how to proceed. 





  7. Hello,

    I am working with arty A7 and arty Z7 dev boards purchased through your website.  I have downloaded IP files from github .  However I when I import into Vivado (2018.2) I am not finding the NIC100 PMOD .  Several of the other PMODS are working and verified.  However, I am not finding the NIC100 PMOD in the add IP , even after digilent library is imported.

    Can you send me to correct github location that contains this file?




    I am working on integrating ESP32 PMOD into a vivado 2018.2 project.  I have imported DIgilent IP library into Vivado.  When I place PMOD and connect to board, during compilation.  It is actually a general message from the block design (See attached image).

    It apperas to me that this IP is for ArtyZ7?  or some other Zync product?  If so, is there IP available for Arty A7 or is this message to be ignored?


  8. Hello,


    Thanks.  Yes I am familiar with basic demos at this point and am trying to move onto more interesting projects.  I have implemented this demo but it seems to be all written in vivado HDL, with which i have a fair amount of experience coming from ISE.  I was looking for some additional resources for SDK side.  But now that I consider, perhaps even the firmware that the ArtyA7 comes pre-loaded with is likely to be pure HDL.  We can close this question.  Thank-you for your attention, it is much appreciate.

  9. Hello,

    I am working through some of the examples for the Arty A7 device.  The device seems to come pre-loaded with firmware, some simple reference design that makes use of UART, LED's and pushbuttons.

    Is there some project I can download to reproduce this reference design?  I am planning to overwrite this in the future, but I also wanted to have a copy.



  10. Well Thank's for your support. I will be working on several other projects trying to get them up and running.  I think this was important.

    One question that remains in my mind however, is how to determine if the drivers need to be imported from the ip_defs folder or not when working with various IP.  It was not very straightforward, as several other IP were using "generic" and didn't seem to cause a problem.  The two that we selected seemed somewhat non-intuitive.  I am wondering when this kind of thing will come up again, and I will need to handle.

    Thanks again.

  11. Hello,

    Nice.  Works.  no 3.3V jumper necessary.  

    For some reason the SDK was not populating the main.cc file with any of the driver information needed.  Now when I have recompiled form start, the main.cc file comes back with much more data.  

    I don't think I fully understand the source of the error.  It could have been includes.  But the project is indeed functioning now.   





  12. OK.  I will re-run.  

    While Re-reading the first line though this reminded me of another concern I had.   It requests placing jumper on 3V3, however, no pins were soldered.  Should I manually short these and remove the 2.5V jumper?  

    If that 3.3V is used or powering camera, I am wondering if this could also be impacting.  Please let me know.  Meanwhile, I will continue to re-build.

    3V3 Jumper.jpg

  13. Ok.  Will go ahead and pick up a couple of those for our team to develop with.  I will still be looking to get the other demos working with the ZED, however, there seem to be several interesting projects that could be useufl for our end application using ArtyZ7.


    Thanks for your quick, clear, concise responses.

  14. I see.  So is zed dead?  I frankly don't see alot of activity on this board to use for reference designs. Many links are broken.  Would you suggest Arty Z7 for zynq development projects as a more up to date development board? Another board?  One project we have in the works will be driven by Zynq and would like to have as many examples with PMODS / peripherals as possible.





  15. Hello,

    I have actually tried to do both.  For C++ i wrote a similar 'Hello World' example to make sure it is getting compiled.

    Unfortunately, I am seeing Hello World, but I am not seeing VGA output on the monitor.  Does this imply there is some issue with bitstream?

    BTW, this is Digilent Board with FMC PCAM adapter purchased online through Digilent Portal.  

  16. Hello,

    Thank-you for that clarification.  I must have skipped that when I was building the demo.  As seen below, I have updated the folders, and the drivers are updated.  I am also recieving "Hello World" over com port.

    Regardless, VGA signal is not showing up on my monitor.  Any other suggestions ?.  






  17. Hello,

    My group has acquired the two boards Artix A7 and ZedBoard for developing some applications.  I am noticing couple differences regarding projects and documentation. 

    One such difference has to do with the reference base design.  For Artix A7 I am finding the PMOD ports, and I2C, SPI, UART, Ethernet included in Board connections.  For ZedBoard, very few peripherals are included in the base design I was able to locate.  


    For developing new applications for Zynq, can you provide some information regarding Zynq base desing.  Is there more complete project for integrating HDMI / PMODS/ etc..

    Does the Arty Z7 provide better support with respect to this feature?  If so we may consider to develop on this board alternatively.

    I appreciate your feedback,





  18. Hello,

    Thank-you for your response.  I appreciate the feedback. 

    Upon implementing your suggested response, I have rebuilt project fresh, recompiled bitstream, and exported hardware.  As you can see, I am not having the drivers you have in the HW platform output.  

    For this reason, when I go to select the drivers, the choices are "generic" and "none".  There is no alternative.

    I think to reach your solution, I need to have these drivers output into hardware platform.  Please suggest how to do so.





  19. Hello,

    My organization has recently purchased the ZedBoard (as well as other dev boards) as we are getting ready to upgrade some older systems.  As a first step to using ZYNC, have followed all of the steps in this tutorial: https://reference.digilentinc.com/learn/programmable-logic/tutorials/zedboard-fmc-pcam-adapter-demo/start#download_and_launch_the_zedboard_fmc-pcam-adapter_demo

    However, there is some important difference.  When I go to import, i am not seeing any files named pcam_vdmi_hdmi.  I have attached the snippet of the files I am seeing in the ZedBoard_FMC_PCam_Adapter_DEMO.


    Other issues, which may be related, include after programming FPGA and launching SDK on FPGA, I am seeing no information over serial terminal.  I have Com port config for 115200.  I would expect that even cycling power or writing FPGA with bitstream, I should be expecting to see some information.  


    Some details:

    Windows 10

    Vivado 2018.2 (as suggested by author)

    ZedBoard Dev Board