Actions
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 297 subscribers
  • Views 110 views
  • Users 0 members are here
Related

Microzed PMOD's inaccessible

TomerSh

Hello!
I am having some problems accessing MIO_13, MIO_12, MIO_11, MIO_10, which correspond to Pmod's D0-D3.
My system is built from a customized PCB with two DACs that is connected via J1-J2 to the Microzed board. I'm working with Vivado and Vitis v2022.1.
My Vivado design is a very simple zynq processor with the GPIO and some other peripherals enabled,  I double-checked that the specific MIOs are GPIO:
in VIvado:

image

in Vitis:

image

I am using xspio_polled_example.c gpio example file (with some changes) in order to operate the LED in my board, and all PMODs. Upon running the program, MIO_0,9,14,15 as well as the LED on the board are responding, but the problematic MIOs are not.
I am connected via the PMOD interface:
image

some additional info:
I am working with Vitis because I encountered the same problem in Pynq and in the official linux image provided by microzed in their website, and wanted to be sure that my PS is configured right.

If anyone has an idea what could cause the problem, please share this information.

Thank you in advence, Tomer

  • 0

    I ran into a similar issue with a Zedboard recently. The bsp Vitis generated did not set the GPIO OEN bits for the MIO which seems to be left out of examples I have seen. To compound the issue the memory view does not accurately reflect the state of the GPIO registers.

    see  Je1 GPIO - Cant seem to access upper pins 

    File: d:\Vitis\TryAgain\GpioTest\src\helloworld.c

    I used this for each of the pins and it worked 


    121: XGpioPs_SetDirectionPin( &my_Gpio, iPortPins[ii], 1);
    122: XGpioPs_SetOutputEnablePin( &my_Gpio, iPortPins[ii], 1);   // missing from examples I have seen - 
    123: XGpioPs_WritePin( &my_Gpio, iPortPins[ii], 1);