deppenkaiser

Members
  • Content Count

    63
  • Joined

  • Last visited

  • Days Won

    2

deppenkaiser last won the day on April 17

deppenkaiser had the most liked content!

About deppenkaiser

  • Rank
    Frequent Visitor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. deppenkaiser

    Linux Driver

    @morsucci, uio-interrupt is working. I made an error in my pointer arithmetic.
  2. deppenkaiser

    New Development Board

    @deppenkaiser, you don't Need an other board, because uio-interrupt is working.
  3. deppenkaiser

    Arty-Z7-20 BSP 2017.4: GPIO with Switches

    UIO Interrupt is working too!
  4. deppenkaiser

    Arty-Z7-20 BSP 2017.4: GPIO with Switches

    @deppenkaiser, your macro to Access the Memory is wrong, if you would use the right macro, then your Offset calculation would work. @sbobrowicz: I found the error in my Offset calculation, thats could be also the reason for my uio issue! :-) I will tell you the results.
  5. deppenkaiser

    Arty-Z7-20 BSP 2017.4: GPIO with Switches

    Hello @sbobrowicz, 1. I got "Petalinux-Arty-Z7-20-2017.4-1.zip". 2. I fixed the incomplete archive with "vivado-library.zip". 3. I fixed the Vivado build Errors. 4. I created a Linux "Hello world"-App with SDK. 5. I created and configure a new petalinux project with the get-hw-description Option. 6. I build the petalinux image. 7. I saw no uio devices. 8. I added one uio device for the "axi_gpio_sw" device (with Interrupt). 9. I build a new petalinux image. 10. I saw one uio device with registered Interrupts in /proc/interrupts 11. I Changed the "Hello world"-App to read data from UIO with GPIO Channel 1. 12. I added the same code to read channel two but i used the correct Offset for channel two. #define GPIO_CHANNEL_1_DATA 0x00 #define GPIO_CHANNEL_1_DIRECTION 0x04 #define GPIO_CHANNEL_2_DATA 0x08 #define GPIO_CHANNEL_2_DIRECTION 0x0C 13. I saw no data changing even if i use the Switches. 14. I think that there are more Errors on the given Vivado design. Can you please check this? Why can i read data from channel one and not from channel two? Thank you....
  6. deppenkaiser

    Arty-Z7-20 with Vivado 2018.1

    Hello, you know, that i try to use uio. And i still got no result. Therefor i try the next Vivado 2018.1 with the still not delivered petalinux. I created a new Project in Vivado 2018.1 and i tried to choose the Arty-Z7-20 board. But i can't select it; before i did it, i copied the digilent board files into the Xilinx Directory. When do you provide the new board files for Vivado 2018.1; i Need the Arty-Z7-20 :-) Thank you...
  7. Hello, finally i was able to make a petalinux build with the BSP 2017.4 - so far, so good. Then i find out, which uio device is connected with the Arty-Z7-20 Buttons and switches. Both - the Buttons and also the Switches - are connected to one GPIO-IP-Core (Dual-Channel, all inputs). One AXI-GPIO has one base address and a dual channel GPIO has even only one base address. So the only way to address both channels is to use the base address offset for channel one and for channel two, isn't it? If i read channel one - which is assigned to the Buttons - then i can read the Buttons. If i read the channel two (Switches) - one code line later - then i got no result. So my questions is: What must i do to read the Arty-Z7-20 Switches (petalinux, BSP 2017.4)? Thank you...
  8. deppenkaiser

    Arty-Z7-20 with 2017.4 BSP based petalinux build failed

    @morsucci, i think that i have two ways to get a petalinux configuration. The first way is to extract the configuration from the BSP and the second way is to get it from the HDF (new configuration but suited to the design). You know, that i still have the uio issue. So the reason for the things i did - even this thread - is to get the "digilent" configuration from BSP which is able to support uio Interrupts; because you told me that they exist and work. In the Xilinx Forum i got some help but it won't help. The english Queen would say "I'am not amused." I have invested a lot of time... You put the current Arty-Z7-20 BSP on to the download page a few days ago. But it has build Errors and it is not complete because the ip-repo was not included. Now i see that the BSP isn't complete in a further way. So what must i do to get uio with Interrupt handling? Thank you...
  9. deppenkaiser

    Arty-Z7-20 with 2017.4 BSP based petalinux build failed

    It seems that some "digilent-apps" are not available, isn't it? Summary: 3 tasks failed: /home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libuio/libuio.bb:do_fetch /home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libgpio/libgpio.bb:do_fetch /home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libpwm/libpwm.bb:do_fetch Summary: There were 6 ERROR messages shown, returning a non-zero exit code. ERROR: Failed to build project Do i need the apps and what are they good for? Thank you...
  10. Hello, i have some errors while building the 2017.4 BSP based petalinux image. czymic@ubuntu:~/projects/2017.4/Arty-Z7-20$ petalinux-build [INFO] building project [INFO] sourcing bitbake INFO: bitbake petalinux-user-image Parsing recipes: 100% |##########################################| Time: 0:01:30 Parsing of 2473 .bb files complete (0 cached, 2473 parsed). 3266 targets, 226 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Initialising tasks: 100% |#######################################| Time: 0:00:06 Checking sstate mirror object availability: 100% |###############| Time: 0:00:18 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: libuio-1.0-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-lkhXXEii1h"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export GIT_SSL_CAINFO="/home/czymic/petalinux/2017.4/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/etc/ssl/certs/ca-certificates.crt"; export PATH="/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/scripts:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/plnx_arm/usr/bin/crossscripts:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/bin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/sbin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/scripts:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/bitbake/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/sysroots/x86_64-petalinux-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/sbin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/sbin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/../x86_64-petalinux-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-uclibc:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-musl:/home/czymic/petalinux/2017.4/tools/common/petalinux/utils:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin/unexport:/home/czymic/petalinux/2017.4/tools/hsm/bin:/home/czymic/petalinux/2017.4/tools/webtalk/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin:/home/czymic/petalinux/2017.4/tools/common/petalinux/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-none-eabi-r5/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/microblaze-xilinx-elf/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/microblazeel-xilinx-linux-gnu/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-none-eabi/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-linux-gnueabi/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/aarch64-none-elf/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/aarch64-linux-gnu/bin:/home/czymic/bin:/home/czymic/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"; export HOME="/home/czymic"; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/mitchellorsucci/libuio.git failed with exit code 128, output: fatal: unable to connect to github.com: github.com[0: 192.30.253.112]: errno=Connection refused github.com[1: 192.30.253.113]: errno=Connection refused ERROR: libuio-1.0-r0 do_fetch: Function failed: base_do_fetch ERROR: Logfile of failure stored in: /home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/work/plnx_arm-xilinx-linux-gnueabi/libuio/1.0-r0/temp/log.do_fetch.48850 ERROR: Task (/home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libuio/libuio.bb:do_fetch) failed with exit code '1' ERROR: libgpio-1.0-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-lkhXXEii1h"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export GIT_SSL_CAINFO="/home/czymic/petalinux/2017.4/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/etc/ssl/certs/ca-certificates.crt"; export PATH="/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/scripts:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/plnx_arm/usr/bin/crossscripts:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/bin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/sbin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/scripts:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/bitbake/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/sysroots/x86_64-petalinux-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/sbin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/sbin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/../x86_64-petalinux-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-uclibc:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-musl:/home/czymic/petalinux/2017.4/tools/common/petalinux/utils:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin/unexport:/home/czymic/petalinux/2017.4/tools/hsm/bin:/home/czymic/petalinux/2017.4/tools/webtalk/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin:/home/czymic/petalinux/2017.4/tools/common/petalinux/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-none-eabi-r5/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/microblaze-xilinx-elf/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/microblazeel-xilinx-linux-gnu/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-none-eabi/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-linux-gnueabi/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/aarch64-none-elf/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/aarch64-linux-gnu/bin:/home/czymic/bin:/home/czymic/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"; export HOME="/home/czymic"; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/mitchellorsucci/libgpio.git failed with exit code 128, output: fatal: unable to connect to github.com: github.com[0: 192.30.253.113]: errno=Connection refused github.com[1: 192.30.253.112]: errno=Connection refused ERROR: libgpio-1.0-r0 do_fetch: Function failed: base_do_fetch ERROR: Logfile of failure stored in: /home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/work/plnx_arm-xilinx-linux-gnueabi/libgpio/1.0-r0/temp/log.do_fetch.48851 ERROR: Task (/home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libgpio/libgpio.bb:do_fetch) failed with exit code '1' ERROR: libpwm-1.0-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-lkhXXEii1h"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export GIT_SSL_CAINFO="/home/czymic/petalinux/2017.4/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/etc/ssl/certs/ca-certificates.crt"; export PATH="/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/scripts:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/plnx_arm/usr/bin/crossscripts:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/sbin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/usr/bin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/sbin:/home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/sysroots/x86_64-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/scripts:/home/czymic/petalinux/2017.4/components/yocto/source/arm/layers/core/bitbake/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/sysroots/x86_64-petalinux-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/buildtools/sysroots/x86_64-petalinux-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/sbin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/sbin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/../x86_64-petalinux-linux/bin:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-gnueabi:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-uclibc:/home/czymic/petalinux/2017.4/components/yocto/source/arm/tmp/sysroots/x86_64-linux/usr/bin/arm-xilinx-linux-musl:/home/czymic/petalinux/2017.4/tools/common/petalinux/utils:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin/unexport:/home/czymic/petalinux/2017.4/tools/hsm/bin:/home/czymic/petalinux/2017.4/tools/webtalk/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/petalinux/bin:/home/czymic/petalinux/2017.4/tools/common/petalinux/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-none-eabi-r5/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/microblaze-xilinx-elf/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/microblazeel-xilinx-linux-gnu/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-none-eabi/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/gcc-arm-linux-gnueabi/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/aarch64-none-elf/bin:/home/czymic/petalinux/2017.4/tools/linux-i386/aarch64-linux-gnu/bin:/home/czymic/bin:/home/czymic/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"; export HOME="/home/czymic"; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/mitchellorsucci/libpwm.git failed with exit code 128, output: fatal: unable to connect to github.com: github.com[0: 192.30.253.112]: errno=Connection refused github.com[1: 192.30.253.113]: errno=Connection refused ERROR: libpwm-1.0-r0 do_fetch: Function failed: base_do_fetch ERROR: Logfile of failure stored in: /home/czymic/projects/2017.4/Arty-Z7-20/build/tmp/work/plnx_arm-xilinx-linux-gnueabi/libpwm/1.0-r0/temp/log.do_fetch.52387 ERROR: Task (/home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libpwm/libpwm.bb:do_fetch) failed with exit code '1' NOTE: Tasks Summary: Attempted 1534 tasks of which 1513 didn't need to be rerun and 3 failed. Summary: 3 tasks failed: /home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libuio/libuio.bb:do_fetch /home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libgpio/libgpio.bb:do_fetch /home/czymic/projects/2017.4/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libpwm/libpwm.bb:do_fetch Summary: There were 6 ERROR messages shown, returning a non-zero exit code. ERROR: Failed to build project ==================================================================================================================================================== What must i do, to be able to build the BSP based image with: petalinux-create -t project -s <Path to BSP> and petalinux-build Thank you...
  11. deppenkaiser

    Arty-Z7-20 and Vivado 2017.4

    @jpeyron, FYI: The Vivado-Build still has some Errors which i have fixed. Now, I try to build the petalinux image which is derived from the given bsp. I will tell you the results later.
  12. deppenkaiser

    Arty-Z7-20 and Vivado 2017.4

    @jpeyron, sorry, where is the download Content? I see only this: And here you can see my repo Folder: regards deppenkaiser
  13. deppenkaiser

    tcp/ip select does not work

    @deppenkaiser, please look here: https://forums.xilinx.com/t5/Embedded-Linux/tcp-ip-select-does-not-work-on-petalinux-zynq/m-p/844172#M25229
  14. deppenkaiser

    Arty-Z7-20 and Vivado 2017.4

    Hello, i was very happy, that i got the new 2017.4 Vivado design, but my happyness ends after five minutes. I have build Errors, can you please tell me what i have to do? Here is the screenshot: Thank you...
  15. deppenkaiser

    Zedboard

    @jpeyron, is the zedboard a product from digilent? Who is "AVNET"? You know my uio issue, i asked the same question on the Xilinx Forum. The answers i got say, that my Code is looking good, but there is one difference that i should check. I ask them what board they are using, and one of them told me, that he uses a zedboard. From my Point of view - at this Moment - the zedboard is the only board which Supports the needed funtionality. It is surely not the same if i use your BSP or if i use "petalinux-create" to create a defaults based configuration. But it can not be usefull if i'am not able to create an own design. The Slogan "Arty is for makers [...]" seems not to be true. I saw, that you creates a 2017.4 BSP. I will test it after the easter Holidays. For your info: I Need only four hours to create my Project, i guess that you Need only two hours. Why can't you proof the issue with your informations you have. You see, that i have all needed parts developed but the uio-interrupt functionality is not working. If something unknown is the reason and this could not be solved - what ever - then i would not put the blame on you. I only Need an answer, because i have limited time and limited resources and i trust your PR! Thank you...