theUltimateSource

Members
  • Content Count

    90
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by theUltimateSource

  1. I know that RX / TX lines for UART connection are going to be swapped at one end or another. 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. @rmd91there are three: Zybo, Z7-10, Z7-20. How many VGA / HDMI ports do you have on your board?
  4. 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).
  5. you are connecting to JC not J1. In your block design you are connecting to JA? 🧐
  6. 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)?
  7. it looks like your IOMODULE does not support interrupts.
  8. 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?
  9. yes, you can do this. Your diagram only shows the Linux system, how do you want to control the remaining system?
  10. hello, can I change the reference clock for Dynamic Clock Generator IP core? Which frequency do I have to provide for REF_CLK_I?
  11. 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.
  12. 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.
  13. hello @MauroChimenti, I have had no issues cloning the repo, but I am working with Ubuntu natively. Did you checkout your submodules?
  14. hi, are you using VM or native? Which version of petalinux are you using? Which BSP are you using (Zybo-Z7 or Arty-Z7)? Which version of BSP are you using? The messages you posted, are they from a log file or terminal output?
  15. 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.
  16. The petalinux platform is not compatible with 2018.1 tools version. You'll need to create a new platform for 2018.1.
  17. The Petalinx project for the Zybo-Z7-10 will not work on a Zybo-Z7-20 without modifications. Note that there is another version specifically for your target, as well, which you can find here.
  18. ok, which step is this you are now?
  19. I am sorry I seem not to be able to locate the Live I/O demo.
  20. hello @DeAndreHJ can you post your toolchain, writing in your terminal: "arm-" + 2x tab:
  21. 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'.
  22. 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 )
  23. pin constraints are case sensitive. There's probably some mismatch between your design and constraints.
  24. 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