theUltimateSource

Members
  • Content Count

    90
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by theUltimateSource


  1. I know that RX / TX lines for UART connection are going to be swapped at one end or another.

    zybo_led_uart.thumb.png.be0d5386a1e904fcfba024deb4976d2e.png

    but why do you swap them for the status LED that are showing activity? When the Zybo board is sending a message the RX LED lights up?


  2. @rmd91, did you get past your problem?

    After re-reading this and to summarize, you where using the board files for the Zybo on a Zybo-Z7-10 board.

    You'll have ot install the correct board file to your Vivado configuration in case it  isn't already.

    To make changes on your Vivado project you need to follow the Zybo-Z7 migration guide found on the product site for the Zybo.

    Otherwise you can follow the getting started tutorials from the resources for the Zybo-Z7 previously mentioned by jpeyron.


  3. PGOOD must not flicker. Remove attached peripherals from your board, us an external power supply or another USB host device.

    Tera Term means you are working on Windows?

    In regards to your unprintable characters, may you be using the Zybo-Z7-10 board files on a Zybo board? (just a shot in the dark).


  4. depends, I am not familiar with IOMODULE. Your code in SDK is expecting but there are none defined. You either modify your code in SDK or enable interrupt in hardware.

    Are you using the DA3? Can you show us the module configuration in hardware and parameters in your BSP (xparameters.h)?


  5. You'll design your embedded linux system with these additional components just like you would without them. The bit stream will contain both systems. It is loaded by the boot loader during the boot process. The additional components are going to be completely invisible to your linux system.

    Out of curiosity, which development board are you working with?


  6. 20 hours ago, ArKay99 said:

    I'm thinking that even though I'm running a 64 bit processor and 64 bit Windows I should dl the 32-bit PC (i386) desktop image, specifically the: ubuntu-16.04.3-desktop-i386.iso?

    Nope, 32b is not supported by the Xilinx tools. But you are right what matters is not the architecture of the host but rather the guest, I messed that up 😕

    You'll need this one.


  7. Ubuntu 16.04.3 LTS can be downloaded here

    For the exact variant you should use we need to know the architecture of your CPU (intel, arm, amd, 32b or 64b). You can check this in Win 10 system overview.

    To setup Ubuntu in VMWare, download the iso file from the link above. Then create a new VM, mount the iso in your VM, boot it then install it. I am not going into the details for these steps here.


  8. hello @MauroChimenti,

    2 hours ago, MauroChimenti said:

    git clone --recursive https://github.com/Digilent/Petalinux-Zybo-Z7-20.git 

    ------------------- ALL OK 

    2 hours ago, MauroChimenti said:

    I even added the git --- config to manage https in place of http but nothing  changed. 

    I have had no issues cloning the repo, but I am working with Ubuntu natively.

     

    2 hours ago, MauroChimenti said:

     I noticed before every error few seconds of process stopped for the digilent reps (probably because try to load the rep) instead with the linaro_lib all data is downloaded but the task is marked as failed. 

    14 hours ago, MauroChimenti said:

    Summary: 4 tasks failed:
      /home/mauro/Projects/Petalinux-Arty-Z7-20/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libgpio/libgpio.bb:do_fetch
      /home/mauro/Projects/Petalinux-Arty-Z7-20/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libuio/libuio.bb:do_fetch
      /home/mauro/Projects/Petalinux-Arty-Z7-20/Arty-Z7-20/project-spec/meta-user/recipes-apps/digilent-apps/libpwm/libpwm.bb:do_fetch
      /opt/pkg/petalinux/components/yocto/source/arm/layers/meta-linaro-toolchain/recipes-devtools/gcc/gcc-source_linaro-6.2.bb:do_fetch
    Summary: There were 5 WARNING messages shown.

    Did you checkout your submodules?

    On 6/13/2018 at 1:31 AM, fandrei said:

    So, the problem with "Please set a MACHINE in your local.conf or environment" was that I didn't check out submodules of the Petalinux-Zybo-Z7-20 project. 😕
    And then, back to the first question: how do I make the Petalinux-Zybo-Z7-20 project work with PetaLinux 2018.1, what modifications are required?


  9. I am not an expert, but I think the machine names the system you are targeting (which is "zynq", or "zynq generic" in your case). Since you are not ment to change these configurations, I'd assume your petalinux project is corrupted at some point. Try to start from scratch, if you can. 

    Also, can you share which steps you are taking to build the kernel? Otherwise my assumptions are just overly optimistic, or simply wrong. :)


  10. On 3/9/2018 at 11:12 PM, sbobrowicz said:

    2) You should use the reVISION platform and checkout the Live I/O demo. It takes HDMI input, does a convolution filter on it, and forwards it to HDMI output. FYI, I will be pushing some significant improvements to that demo within the next couple weeks. They should improve the framerate and get rid of the image tearing.

    I am sorry I seem not to be able to locate the Live I/O demo.


  11. hello @toastedcpu,

    Can you tell me which tool version you are using for this tutorial? I completed it long time ago and wanted to review it recently. However, it seems like I do no longer have that cross-compile part :( I am working on Vivado/SDK 2017.4. Back then it might have been 2017.2, I think.

    It seems like arm-xilinx-linux-gnueabi is not installed on my machine:

    console output:

    PetaLinux environment set to '/opt/pkg/petalinux'
    INFO: Checking free disk space
    INFO: Checking installed tools
    INFO: Checking installed development libraries
    INFO: Checking network and other services
    user@machine:~$ arm-
    arm-linux-gnueabihf-addr2line   arm-none-eabi-addr2line
    arm-linux-gnueabihf-ar          arm-none-eabi-ar
    arm-linux-gnueabihf-as          arm-none-eabi-as
    arm-linux-gnueabihf-c++         arm-none-eabi-c++
    arm-linux-gnueabihf-c++filt     arm-none-eabi-c++filt
    arm-linux-gnueabihf-cpp         arm-none-eabi-cpp
    arm-linux-gnueabihf-elfedit     arm-none-eabi-elfedit
    arm-linux-gnueabihf-g++         arm-none-eabi-g++
    arm-linux-gnueabihf-gcc         arm-none-eabi-gcc
    arm-linux-gnueabihf-gcc-6.2.1   arm-none-eabi-gcc-6.2.1
    arm-linux-gnueabihf-gcc-ar      arm-none-eabi-gcc-ar
    arm-linux-gnueabihf-gcc-nm      arm-none-eabi-gcc-nm
    arm-linux-gnueabihf-gcc-ranlib  arm-none-eabi-gcc-ranlib
    arm-linux-gnueabihf-gcov        arm-none-eabi-gcov
    arm-linux-gnueabihf-gcov-tool   arm-none-eabi-gcov-tool
    arm-linux-gnueabihf-gdb         arm-none-eabi-gdb
    arm-linux-gnueabihf-gprof       arm-none-eabi-gprof
    arm-linux-gnueabihf-ld          arm-none-eabi-ld
    arm-linux-gnueabihf-ld.bfd      arm-none-eabi-ld.bfd
    arm-linux-gnueabihf-nm          arm-none-eabi-nm
    arm-linux-gnueabihf-objcopy     arm-none-eabi-objcopy
    arm-linux-gnueabihf-objdump     arm-none-eabi-objdump
    arm-linux-gnueabihf-ranlib      arm-none-eabi-ranlib
    arm-linux-gnueabihf-readelf     arm-none-eabi-readelf
    arm-linux-gnueabihf-size        arm-none-eabi-size
    arm-linux-gnueabihf-strings     arm-none-eabi-strings
    arm-linux-gnueabihf-strip       arm-none-eabi-strip

     

    Also, please mark this thread as 'solved'.


  12. yes, you can use UIO drivers for GPIO. These are standard drivers for Linux. There's an API you can use to read and write from UIO devices. I think the petalinux platform from Digilent is using it, too. Make sure the memory address in your device tree matches your address mapping. This is probably defined in some include file, in your case. Without using includes, this will do:

    &axi_gpio_button {
        compatible = "generic-uio";
        reg = <0x43c00000 0x10000>;
    };

    (for some reason, my syntax highlighting is not working :( )


  13. hello,

     

    1)

    - 1st question: as you already figured you can define your device tree in a single file. See system-user.dtsi as reference in the petalinux platforms from digilent. I am a beginner, too but I think it is better to place it all in one file. Once your projects are more complex you can use several files. Instead of system-user.dtsi you can use your own file. You can change this in a file located in the directory where you place these files (meta_user/user_dtb/ something like that)

    - 2nd question: to change the kernel configuration use the petalinux-tools. I don't know what you want to change, though

    - 3rd question: have you had a look at UG1156?

    - 4th question: no, this is usually not the case. You have to configure rootfs

     

    2) 

    - 1st question: yes (one driver for each is highly recommended ^^)

    - 2nd question: http://www.wiki.xilinx.com/Linux+Drivers