10-19-2020 02:23 AM
I have followed all the steps provided in the following link
everything is fine I am getting uio0 in linux but after changing the value of the memory location provided in example value of interrupt count is not changing and push button interrupt is also not getting received, kindly help anyone, more information I am using zcu111 and vivado 2019.2 and vitis 2019.2
10-19-2020 02:33 PM
Hi @f35
You stated "after changing the value of the memory location provided in example" in your post. Which memory location are you referring to? In the example, the AXI GPIO IP is set to a memory range, which should match with the offset pointed to by /dev/mem access.
Thanks,
-Pat
Give kudos if helpful. Accept as solution if it solves your problem.
https://tuxengineering.com/blog
10-19-2020 08:53 PM
As given in that example I am changing in memory location 0xa0000120
12-23-2020 05:57 AM
I am having the same problem with a ZCU104 and Petalinux/Vivado 2020.2. I also get uio0 in Linux and I am using the same command:
That looks good but when I check the gpio interrupt counter it is still 0. Did anyone find a solution yet?
12-23-2020 09:49 AM
There is not a direct connection of toggling the interrupt line to the counter shown in /proc/interrupts without a kernel driver servicing the interrupt. Without a driver servicing the interrupt (i.e. returning IRQ_HANDLED), the counter will stay at 0.
See this insightful post from @hokim for details and example driver code. Vitis-platform-for-ultra96v2-is-not-working
Also I posted this related case yesterday with example userland code Axi-intc-hangs-on-boot-testcase-on-zcu104/m-p/1188729/highlight/true#M47736 using GPIO+UIO interrupts.
Thanks,
-Pat
Give kudos if helpful. Accept as solution if it solves your problem.
https://tuxengineering.com/blog