Search the Community

Showing results for tags 'arty-z7-20'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 15 results

  1. Hello, i have a problem with the Vivado SDK. I like to include some c Header: #include <stdio.h> #include <unistd.h> #include <stdbool.h> #include <string.h> #include <arpa/inet.h> #include <sys/select.h> #include <sys/socket.h> Eclipse tell me, that my includes are unresolved. I think that is because i have nearly thirty directories in my Vivado 2017.2 SDK Installation, but it is not defined what directory exactly should be used. Can anybody tell me what is the correct include path for a 32 bit Linux application for my arty board? Thank you...
  2. Hi, I have been following the instruction on https://github.com/Digilent/Petalinux-Arty-Z7-20. These are well done and I got a running image on a SD card from the cloned git repo. Then I switched to the Digilent Apps description, changed some config and recreated the image. This one stopped after the message "Starting kernel..." After some tries, it turned out that just rebuilding the image even without any change leads to that behaviour. However, cleaning the build will again give a correct image. But I believe thats not the intention to clean for each build... What do I miss? Thanks for your help, Juergen
  3. 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...
  4. 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...
  5. Hello, i made the following design: You can see two GPIO Ports: - GPIO_RGB_LED, 3 Bit, Output only - GPIO_SW, two data bits plus one interrupt bit (e.g. Input clk), this port should throw Interrupts into the Linux App. After i build that design with Vivado, i used petalinux to create a Linux image. Here you can see the "/dev"-Folder which contains the installed Drivers: You can see three GPIO-Drivers. Now my question: In former questions i ask for the Driver Support in Linux and how i can write or use them. You told me, that there is a simple way to access memory mapped ip-cores with the "uio"-Driver. First i was glad to see that the Drivers are automaticaly added to the image. But i'am missing the expected "uio"-Drivers. What must i do to get the "uio"-Drivers for my design with petalinux? Thank you...
  6. I'm trying to build the Arty-Z7-20 petalinux project version 2017.4 but it keeps failing because off: libuio-1.0-r0 do_fetch libgpio-1.0-r0 do_fetch libpwm-1.0-r0 do_fetch gpiotil-1.0-r0 do_fetch pwmdemo-1.0-r0 do_fetch failing, because the connection times out, is there a way to bypass this?
  7. 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...
  8. Hello, i have a new created petalinux project for the zynq processor (Arty-Z7-20). I'am not using a digilent bsp file to configure the project, because i have a simple selfmade design and i like to start with a minimalistic Linux. I like to support Linux pthread and sockets, thats all. If i implement a tcp/ip Server and if i use the select Routine to wait for incomming data then the "select" Routine does not return, even if i receive data. In an other thread here in this Forum i discuss a similar issue. There i have a Problem with the "uio" Interrupt handling, because the blocking read does not return. So i think, that these two different issues have the same reason. My Linux image is not able to generate Events which can Trigger the "select" Statement. How can i enable the petalinux ability to handle "select"-commands? Thank you...
  9. deppenkaiser

    Zedboard

    Hello, i have an other question: If i look in the Mouser electronic shop i see, that the zedboard is associated with digilent and you Show on https://store.digilentinc.com/zedboard-zynq-7000-arm-fpga-soc-development-board/ the board. Why do you have no support on https://reference.digilentinc.com/reference/software/petalinux/start for the zedboard? Thank you...
  10. Hello digilent, when do you update the Arty-Z7-20 examples and resources for this board? Could you please make at least two examples: One with Maximum Support of the given hw (all Features of Arty-Z7-20) and one Basic example which has the Chance two be compatible with future Vivado Versions? The Basic example should only be able to handle tcp/ip and uio, i would be very lucky. Thank you...
  11. Hello, is it true, that a device tree file like <finally-used-device-tree>.dts is always generic and will always generated thru a <source-for-device-tree-file>.dtsi file? I found some basic files in "/my-petalinux-project/components/plnx_workspace/" e.g. "zynq-7000.dtsi" and a generic "system-top.dts" file. Must i edit those files (e.g. zynq-7000.dtsi)? Is there an other relevant Location? Thank you...
  12. Hello, since now, i have only experience in debugging bare metal apps. I will write a linux tcp/ip-server, therefor i must be able to debug my c-code. I have tried the known bare-metal-workflow and instead of Chose "bare-metal" i Chose Linux as operating System. When i start the debugging process then i got the following error: What is a "Linux Agent" and why is it disconnected? Thank you...
  13. Hello, i used the "Arty-Z7-20-base-linux"-project with Vivado 2017.2, first i copied the board files to my new installed vivado 2017.2 Installation and then i run the "create_project.tcl" script. So far so good. After that i have tried to create a hdl-wrapper, because i liked to generate a bitstream. Vivado has got the following error: As you can see, the reason is: "IP definition not found" for the listed ip-cores (see error message). Can you tell me, what i should do? What is a "Petalinux-Arty-Z7-20-2017.2-2.bsp" file and what is it good for? Thank you...
  14. deppenkaiser

    Unknown Resource

    Hello, the online Manual wrotes: "[...] The Zynq presets file (available in the Arty Z7 Resource Center) takes care of mapping the correct MIO pins to the UART 0 controller and uses the following default protocol parameters: 115200 baud rate, 1 stop bit, no parity, 8-bit character length. [..]" Where are the files? What Name do they have? How do i use them? Thank you...
  15. deppenkaiser

    Where is J14?

    Hello, i'am still trying send "Hello World" to my terminal. I made a simple design in vivado and use the uartlite ip. But i cant generate the Bitstream because of undefined ports: "[DRC NSTD-1] Unspecified I/O Standard: 2 out of 132 logical ports use I/O standard (IOSTANDARD) value 'DEFAULT', instead of a user assigned specific value. This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all I/O standards. This design will fail to generate a bitstream unless all logical ports have a user specified I/O standard value defined. To allow bitstream creation with unspecified I/O standard values (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks NSTD-1]. NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: uart_rtl_rxd, and uart_rtl_txd." So i tried to solve that issue, but i dont know which pins i should connect with the used ports. I thought, that i should read the manual, but the manuel gives me no answer! The page where J14 (USB-UART-Bridge) should be decribed is lost - maybe in the deep space or in an black hole? Where is the schematic for the Arty-Z7-20 board? I dont mean the one, where J14 is gone away. My trust in you is nearly gone... Thank you...