Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 354 subscribers
  • Views 453 views
  • Users 0 members are here
Related

Zedboard CTT

Former Member

Hello,

I'm working through the Concepts Tools and Techniques document (CCT) for Vivado 2013.2. 

I got as far as Page 33.  In Step 3 of 3.1.1, it says to use the Zedboard Development Template preset to restore the Zynq PS to the default settings.  I do this, click on OK in a few spots, but the block diagram remains unchanged.  In order to get it to do what I believe is being asked, I have to delete the block, and then continue with the exercise.

Then, I get as far as Figure 3-3.  The GPIO_1[0:0] does not appear.  I also cannot get MIO[53:0] to appear.

Any ideas what I'm doing wrong?

Thanks

Brian

  • 0

    I figured out why the ports weren't appearing.  There are some tiny buttons on the processor block that must be clicked to expand the ports.  So, I found those.

    Still don't know why the template doesn't work.

    So, on to the software.  Copied from the PDF file into the C source file.  Three compiler errors:

    inbyte() doesn't seem to be defined.  I see it in a header, but not a library file.

    XPAR_PS7_GPIO_1_DEVICE_ID is not defined, but XPAR_PS7_GPIO_0_DEVICE_ID is defined.

    Similarly, XPAR_PS7_SCUGIC_1_DEVICE_ID is not defined,
    but XPAR_PS7_SCUGIC_0_DEVICE_ID is.

    Correcting for the above by
    #define inbyte getchar
    and replacing what is not defined by what is, the program immediately terminates when it is run.  Nothing gets printed to the terminal screen.

    Ideas?

    Thanks.  Brian

  • 0

    Ok.  Started with a clean project this time instead of working from HelloWorld.  That seemed to take care of several things:
    1)  No problems with using the template definition for the Zedboard Zynq.
    2)  When I got to the SDK, the inbyte() function finally found its source, so I didn't have to use the macro.

    However, I still had to change the 1s to 0s for the two device ID constants:
    XPAR_PS7_SCUGIC_1_DEVICE_ID
    XPAR_PS7_GPIO_1_DEVICE_ID

    Then the whole thing worked like a champ.

    My block diagram doesn't look exactly like the diagram in the .pdf.  Specifically, there are some extra unconnected ports and pins, and some missing ports and pins. 

    Ahh well ... to be investigated another day.

    Brian

  • 0 in reply to Former Member

    Hi Brian.
       Have you solved the promblem?(XPAR_PS7_SCUGIC_1_DEVICE_ID not declared) Would you like to share the solution?
       Thanks.
       May.

  • 0 in reply to Former Member

    Changing the constant allowed the example code to compile and run.  I was told that the ISE tools used a different indexing scheme than the Vivado tools, but the labels for the constants weren't changed in the source c code.

    Brian