Quantcast
Channel: Xilinx Wiki : Xilinx Wiki - all changes
Viewing all 11776 articles
Browse latest View live

reVISION Getting Started Guide 2017.2 (Change XKB link to AR link)

$
0
0
...
Solution: UG894, page 18 "Initializing Tcl Scripts" shows how to create and modify the file Vivado_init.tcl which can be used to set additional global parameters. Add the following line to the Vivado_init.tcl file:
set_param drc.maxThreads 1
...
source.. See XKB69564AR69564 for details.
HDMI input/output may behave incorrectly on ZCU102 board with ES2 silicon
Some designs may exhibit incorrect behavior when HDMI is used as the input and/or output. For the output, one possible behavior is that the display monitor does not show a picture, and remains black. For the input, one possible behavior is that even though a source is connected to the HDMI input, the system will not recognize this.

AXI USB Device Driver

$
0
0
...
Changelog-2017.3Changelog-2017.32017.3
None
Related Links

AXI USB Device Driver

$
0
0
...
{Img1.png}
ChangelogChangelogChangelog
Changelog-2017.1
Changelog-2017.3Changelog-2017.32017.3
None

2017.3 Linux and DTG Release Notes

$
0
0
...
Zynq Ultrascale+ MPSOC USB
drivers/usb/dwc3/
Added UASP (USB(USB Attached SCSI
Added SMMU support for HOST and DEVICE mode
http://www.wiki.xilinx.com/Zynq+Ultrascale+MPSOC+Linux+USB+device+driver
...
Zynq and ZynqMP SD Controller
drivers/mmc/host/sdhci-of-arasan.c
add support for switching to UHS-I modes on ZynqMP Platform
http://www.wiki.xilinx.com/SD+controller
Zynq/

2017.3 Linux and DTG Release Notes

$
0
0
...
Corrected errors when dwc3 loaded as module
http://www.wiki.xilinx.com/Zynq+Ultrascale+MPSOC+Linux+USB+device+driver
Zynq and ZynqMP SD Controller
drivers/mmc/host/sdhci-of-arasan.c
For SD boot issues preventing SD driver deferred probe after host init
add support for switching to UHS-I modes even if there is not provision for SD power cycle
http://www.wiki.xilinx.com/SD+controller

DTG Feature Changes
Module Name

ZCU102 Image creation in OSL flow

$
0
0
...
git checkout xilinx-v2017.1
export CROSS_COMPILE=aarch64-linux-gnu-
make ARCH=arm64 xilinx_zynqmp_defconfigexport ARCH=aarch64
make xilinx_zynqmp_zcu102_revB_defconfig

make ARCH=arm64
Build device-tree
mkdir repo/my_dt

ZCU102 Image creation in OSL flow

$
0
0
...
export CROSS_COMPILE=aarch64-linux-gnu-
export ARCH=aarch64
make xilinx_zynqmp_zcu102_revB_defconfigxilinx_zynqmp_defconfig
make
Build device-tree

2017.3-zc702-release.tar.xz


2017.3-zc706-release.tar.xz

2017.3-zcu102-release.tar.xz

2017.3-zcu106-release.tar.xz

Zynq2017.3 Release

$
0
0
...
Download
The gziped tar ball contains the pre-built Linux images for the board platform
{2017.2-zc702-release.tar.xz}{2017.3-zcu106-release.tar.xz}
{2017.3-zcu102-release.tar.xz}
{2017.3-zc706-release.tar.xz}
{2017.3-zc702-release.tar.xz}

Extract the archive
tar -zxhvf 2017.3-<board>-release.tar.xz

2017.3-zed-release.tar.xz

Zynq2017.3 Release

$
0
0
...
{2017.3-zc706-release.tar.xz}
{2017.3-zc702-release.tar.xz}
{2017.3-zed-release.tar.xz}
Extract the archive
tar -zxhvf 2017.3-<board>-release.tar.xz

PetaLinux kernel and application build steps in configuring ZU MPSoC board as PS PCIe End Point and Root Port

$
0
0
Important! Tag the page
Important! All External Links should open in a new tab/window; all Internal Links to Xilinx wiki pages, should open in the same tab/window.
This document provides an overview of how to build linux kernel and test application in configuring ZU+ MPSoC as PS PCIe End Point and PS PCIe Root Port DMA Controller.
This DMA controller is part of Zynq Ultrascale+ processing system (PS) and does not require any additional hardware design in programmable logic.
Section 1
Sub-Heading 1
Sub-Heading 2
Insert Code: Use Widget-> Insert Code
Insert your code here.
Related Links
Title 1 & Link 1
Title 1 & Link 1


image2017-9-20_11-10-21.png

image2017-9-21_16-53-48.png

image2017-9-21_16-53-48.png

image2017-9-21_16-51-25.png

PetaLinux kernel and application build steps in configuring ZU MPSoC board as PS PCIe End Point and Root Port

$
0
0
...
clean:
<Press TAB key> rm -f $(APP_OBJS) $(APP)
4.
Include
Include header file
bash> vi project-spec/meta-user/recipes-apps/simple-test/simple-test.bb
#
...
"file:${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = " file://simple-test.c \
file://common_include.h\[[file:Makefile\"file://common_include.h\[[file:Makefile\"S = "${WORKDIR}"do_compile() {oe_runmake}do_install() {install -d ${D}${bindir}install -m 0755 simple-test ${D}${bindir}}
5. Give PetaLinux build command to build the application as part of rootfs bash> petalinux-build
Application pio-test build steps for demonstrating Ingress Translation
In PetaLinux project directory i.e. in ps_pcie_dma directory create application pio-test, to include this into part of PetaLinux is explained in following steps.bash> petalinux-create -t apps --template c --name pio-test –enable> # Download source files pio-test.c and header file common_include.h from attachments and copy it into the below path in PetaLinux project directory.> bash> cp pio-test.c project-spec/meta-user/recipes-apps/pio-test/files/ bash> cp common_include.h project-spec/meta-user/recipes-apps/pio-test/files/> # Open Makefile and add target clean to the Makefile showed in below path. Target clean is highlighted in red below. Press <TAB> key before clean command. bash> vi project-spec/meta-user/recipes-apps/pio-test/files/Makefile>
APP = pio-test# Add any other object files to this list belowAPP_OBJS = pio-test.oall: buildbuild: $(APP)$(APP): $(APP_OBJS)$(CC) $(LDFLAGS) -o $@ $(APP_OBJS) $(LDLIBS)clean:<Press TAB key> rm -f $(APP_OBJS) $(APP)
4. Include header file common_include.h in pio-test.bb file. Changes are highlighted in red. The pio-test.bb should look like.
bash> vi project-spec/meta-user/recipes-apps/pio-test/pio-test.bb
#
# This file is the pio-test recipe.
#
SUMMARY = "Simple pio-test application"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = "file://pio-test.c \
file://common_include.h \
file://Makefile \
"

S = "${WORKDIR}"
do_compile() {
...
do_install() {
install -d ${D}${bindir}
...
-m 0755 simple-testpio-test ${D}${bindir}
}
5. Give PetaLinux build command to build the application as part of rootfs
bash> petalinux-build
PetaLinux Build Images Location for PS PCIe End Point DMA. image.ub with (simple-test and pio-test apps) and BOOT.BIN are located in PetaLinux project directory in images/linux
ZCU102 common boot steps for testing PS PCIe EP DMA and Root Port DMA.
Two Boards are needed in this demonstration. ZCU102 and ZCU112 boards.On ZCU112 /End Point (copy BOOT.BIN from attachment above into SDcard)
Set the boot mode pins of ZCU112 to SD boot mode as shown in the picture below
{image2017-9-20_11-10-21.png}
3. Place the ZCU112 board on the PCIe slot of host machine(ZCU102 or x86).
ZCU102 board with SD boot.
4. On Host machine (ZCU102)
To test EndPoint DMA use SDCard with the image.ub (simple-test and pio-test apps) and BOOT.BIN build from PS PCIe End Point DMA build steps.
To test Root Port DMA use SDCard with the image.ub (simple-test app) and BOOT.BIN build from PS PCIe Root Port DMA build steps.
Set the boot mode settings in DIP switch on host ZCU102 board to SDCard.
Mode switch SW6 should be set to boot from SD card.
Use the following switch settings:
SW6.1: ON
SW6.2: OFF
SW6.3: OFF
SW6.4: OFF
Running the simple-test application on ZCU102 testing PS PCIe End Point DMA.
1. Follow steps in ZCU102 common booting steps to test PS PCIe EP DMA and Root Port DMA.
2. ZCU112 board switch on power and execute SD boot. The following prints will be seen on console for ZCU112.
{image2017-9-21_16-53-48.png}
3. Power On Host machine (ZCU102)
After boot up check whether end point is enumerated using lspci utility.
{image2017-9-21_16-51-25.png}

Sub-Heading 1
Sub-Heading 2
Viewing all 11776 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>