Build kernel

May 18, 2017, 8:53 am

≫ Next: Build Device Tree Compiler (dtc)

≪ Previous: Build U-Boot

$

0

0

...

This is a part of the Xilinx design flow described in Getting Started.
Task Dependencies (Pre-requisites)
Fetch Sources (Linux sources)
InstallInstall Xilinx tools (cross-compilation toolchain)
Fetch Sources
Build Device Tree Compiler
Build U-Boot (mkimage utility)
Hardware Project *required(required for MicroBlaze onlyonly)
Tools Required
Cross-compilation toolchain (installed with Xilinx SDK)

---

Build Device Tree Compiler (dtc)

May 18, 2017, 8:53 am

≫ Next: Install Xilinx Tools

≪ Previous: Build kernel

$

0

0

This page describes how to download and build the device tree compiler (DTC) from mainline. This utility is required for building U-Boot sucessfully. Building the device tree compiler is a part of the Xilinx design flow described in Getting Started.
Task Dependencies (Pre-requisites)
Fetch sources (device tree compiler)
InstallInstall Xilinx tools (cross-compilation toolchain)
Fetch Sources
Tools Required
Xilinx SDK

Install Xilinx Tools

May 18, 2017, 8:56 am

≫ Next: USB

≪ Previous: Build Device Tree Compiler (dtc)

$

0

0

...

Platform specific hints & tips
Ubuntu 12.04 LTS x86_64 users may run into issues related to missing dependencies when installing the Xilinx tools. This release of Ubuntu lacks some needed 32-bit libraries which need to be installed. This can be done by executing
bash$ sudo apt-get install ia32-libs
For Ubuntu 14.04 LTS and later, set up the 32-bit repositories using the command below and then install 32-bit packages by including the :i386 suffix to the package name.
bash$ sudo apt-get install ia32-libs
Setting Up the Tools

USB

May 18, 2017, 11:24 pm

≫ Next: USB

≪ Previous: Install Xilinx Tools

$

0

0

Linux USB DWC3 Host/Peripheral Driver
Configuration:Configuration
CONFIG_USB_DWC3=y
CONFIG_USB_DWC3_DUAL_ROLE=y

...

CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_PLATFORM=y
=
=
Devicetree
usb@0 {

...

};
};
Testing Device mode:
Boardmode
ZCU102 Board Setup on zcu102:
Jumper settings:settings
J7 - ON
J113 - 1-2
J110 - 2-3
i. ConnectConnect USB cable

...

is Mass StorgeStorage Device connector)
Other end of the cable will be connected to Host PC to detect the Mass Storage Device
Linux:Linux
Create a temporary storage area, that acts as Pen Drive

...

of=/tmp/my_file bs=256 count=1048576rrcount=1048576
Insert the Mass Storage Device modules
zynqMP> insmod /lib/modules/'uname -r'/kernel/fs/configfs.ko

...

Host PC detects our device as pen drive and prompts for formatting it. Format it and copy any files to it and disconect cable from PC and reconnect.
You should see drive with files you copied earlier.
Testing Host mode:mode
ZCU102 Board Setup:Setup
Jumper settings:settings
J7 - Off
J113 - 1-2
J110 - 1-2
i. ConnectConnect a Pendrive

...

is Mass StorgeStorage Host connector)
Linux:
Linux
Linux running on our subsystem detects the pen drive connected and the terminal shows the device recognition messages (example: sda: sda1).
Interoperability Testing:

USB

May 18, 2017, 11:25 pm

≫ Next: USB

≪ Previous: USB

$

0

0

...

CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_PLATFORM=y
=
=
Devicetree
usb@0 {

USB

May 19, 2017, 1:08 am

≫ Next: Xilinx DRM KMS driver

≪ Previous: USB

$

0

0

Linux USB DWC3 Host/Peripheral Driver
WARNING
We could not get USB 3.0 to work with the USB Micro-B to A adapter that came with the ZCU102. It only worked with a direct cable from our hard drive enclosure to the Micro-B connector on the eval board without requiring an adaptor. With the adaptor in place it always fell back to USB 2.0.
Configuration
CONFIG_USB_DWC3=y

...

ZCU102 Board Setup
Jumper settings
J7 - ON
J113 - 1-2
OFF
J110 - 2-3
1-2
J113
1-2
Connect USB cable to the connector (J96) on board(this is Mass Storage Device connector)
Other end of the cable will be connected to Host PC to detect the Mass Storage Device

...

ZCU102 Board Setup
Jumper settings
J7 - Off
J113 - 1-2
ON
J110 - 1-2
2-3
J113
1-2
Connect a

...

to the connector(J96)connector (J96) on board (this is Mass Storage Host connector)
Linux
Linux running on our subsystem detects the pen drive connected and the terminal shows the device recognition messages (example: sda: sda1).
If the device only comes up as a USB 2.0 device then check your cable, see the warning at the top of the page.
Interoperability Testing:
USB 2.0

...

Host Mode
Pendrive(SanDisk Ultra Fit [16G])
Samsung 850 Evo 500GB using Delock USB3.0 enclosure
Low speed Mouse and Keyboard
Device Mode

Xilinx DRM KMS driver

May 19, 2017, 4:18 am

≫ Next: Zynq UltraScale MPSoC Base TRD: 2017.1 TRD

≪ Previous: USB

$

0

0

...

Supporting IPs
Chroma resampler(CRESAMPLE)
* The Chroma resampler IP is in maintenance mode and not recommended for new designs. For all new designs, users are recommended to use Video Processing Subsystem.The Linux drivers for the Video Processing Subsystem will be available soon *
On Screen Display(OSD)
* The OSD IP is in maintenance mode and not recommended for new designs. For all new designs, users are recommended to use Video Mixer. The Linux drivers for the video mixer will be available soon *
RGB to YUV converter(RGB2YUV)
Video Timing Controller(VTC)
DisplayPort(DP)
Soft IP (only the LogiCORE v7.0, not the Subsystems)
ZynqMP DP subsystem with (DP sub and DPDMA)
MIPI DSI2 Tx(DSI)

Zynq UltraScale MPSoC Base TRD: 2017.1 TRD

May 19, 2017, 8:37 am

≫ Next: PetaLinux Yocto Tips

≪ Previous: Xilinx DRM KMS driver

$

0

0

Hello, I'm unable to get working displayport with the 2017.1 kernel (4.9) with a design similar to the 2016.4 TRD.

I get the following errors from the displayport driver:

1. dmesg | grep -in dp

155:[ 4.370665] UDP hash table entries: 2048 (order: 4, 65536 bytes)
156:[ 4.370774] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
159:[ 4.371885] RPC: Registered udp transport module.
178:[ 4.376552] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
201:[ 5.599268] xilinx-drm-dp-sub fd4aa000.dp_sub: Xilinx DisplayPort Subsystem is probed
221:[ 5.733975] TI DP83867 ff0e0000.etherne:0c: attached PHY driver [TI DP83867] (mii_bus:phy_addr=ff0e0000.etherne:0c, irq=-1)
294:[ 6.277155] xilinx-dp-snd-pcm amba:dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
295:[ 6.284758] xilinx-dp-snd-pcm amba:dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
296:[ 6.292454] xilinx-dp-snd-codec amba:dp_snd_codec0: Xilinx DisplayPort Sound Codec probed
297:[ 6.302975] xilinx-dp-snd-card amba:dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
298:[ 6.316143] xilinx-dp-snd-card amba:dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
299:[ 6.328563] xilinx-dp-snd-card amba:dp_snd_card: Xilinx DisplayPort Sound Card probed
315:[ 6.425407] xilinx-drm-dp fd4a0000.dp: failed to get phy lane
323:[ 6.489428] xilinx-drm-dp fd4a0000.dp: failed to get phy lane

1) Do you have any idea about this issue?
2) Is there a 2017.1 TRD example coming out soon?

---

PetaLinux Yocto Tips

May 19, 2017, 4:01 pm

≫ Next: PetaLinux Yocto Tips

≪ Previous: Zynq UltraScale MPSoC Base TRD: 2017.1 TRD

$

0

0

...

SRC_URI_append = " file://inittab.patch"
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
Related Links

PetaLinux Yocto Tips

May 19, 2017, 4:02 pm

≫ Next: Yocto

≪ Previous: PetaLinux Yocto Tips

$

0

0

...

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
Related Links
Xilinx Yocto

Yocto

May 19, 2017, 4:03 pm

≫ Next: Yocto

≪ Previous: PetaLinux Yocto Tips

$

0

0

...

Booting Xen on ZCU102 using SD card
SD boot with Yocto images
PetaLinux Yocto Tips
Reference Resources
OE Layer Index

Yocto

May 19, 2017, 4:03 pm

≫ Next: PetaLinux Yocto Tips

≪ Previous: Yocto

$

0

0

PetaLinux Yocto Tips

May 19, 2017, 4:47 pm

≫ Next: PetaLinux Yocto Tips

≪ Previous: Yocto

$

0

0

...

Yocto project
Working with a user space Yocto layer

...

adapted to PetalinuxPetaLinux using the
Installing the meta-example layer on your host
git clone https://github.com/DynamicDevices/meta-example

PetaLinux Yocto Tips

May 19, 2017, 4:49 pm

≫ Next: Build Device Tree Compiler (dtc)

≪ Previous: PetaLinux Yocto Tips

$

0

0

...

petalinux-build -c bbexample-lt
Configuring the layer path in the petalinux build system

...

to your petalinuxPetaLinux project build
BBLAYERS := " \
${SDKBASEMETAPATH}/layers/poky/meta \

...

core-image-minimal.bbappend file content
IMAGE_INSTALL += " bbexample-lt"

...

example under qemuQEMU
1. Rebuild your layer
petalinux-build -c bbexample_lt -x cleansstate

Build Device Tree Compiler (dtc)

May 19, 2017, 6:37 pm

≫ Next: Build kernel

≪ Previous: PetaLinux Yocto Tips

$

0

0

...

After the build process completes the dtc binary is created within the current directory. It is neccessary to make the path to the dtc binary accessible to tools (eg, the U-Boot build process). To make dtc available in other steps, it is recommended to add the tools directory to your $PATH variable.
export PATH=`pwd`:$PATH
Next StepBuild Steps
Fetch Sources
Build FSBL
Build Device Tree Compiler (DTC)
Build PMU Firmware
Build Arm Trusted Firmware (ATF)
Build U-Boot
Build and Modify a Root File System
Build Device Tree Blob
Build Linux Kernel
Prepare Boot Image
Prepare Boot Medium
Setup a Serial Console
Additional Information: Build Qt and Qwt Libraries

---

Build kernel

May 19, 2017, 6:40 pm

≫ Next: Build U-Boot

≪ Previous: Build Device Tree Compiler (dtc)

$

0

0

...

make ARCH=powerpc UIMAGE_LOADADDR=0x8000 uImage
If the mkimage utility is available in the build environment, linux-xlnx/arch/microblaze/boot/uImage which is a U-Boot header.
Next StepBuild Steps
Fetch Sources
Build FSBL
Build Device Tree Compiler (DTC)
Build PMU Firmware
Build Arm Trusted Firmware (ATF)
Build U-Boot
Build and Modify a Root File System
Build Device Tree Blob
(You are here) Build Linux Kernel
Prepare Boot Image
Prepare Boot Medium
Setup a Serial Console
Additional Information: Build Qt and Qwt Libraries
Related Links
Fetch Sources

Build U-Boot

May 19, 2017, 6:40 pm

≫ Next: Build PMU Firmware

≪ Previous: Build kernel

$

0

0

...

U-Boot> bootm <addr of kernel> <addr of rootfs> <addr of device tree blob (dtb)>
Note: Make sure the kernel and root filesystem images are wrapped by with the U-Boot header. The device tree blob does not need to be wrapped with the U-Boot header.
Next StepBuild Steps
Fetch Sources
Build FSBL
Build Device Tree Compiler (DTC)
Build PMU Firmware
Build Arm Trusted Firmware (ATF)
(You are here) Build U-Boot
Build and Modify a Root File System
PrepareBuild Device Tree Blob
Build Linux Kernel
Prepare Boot Image
Prepare Boot Medium
Setup a Serial Console
Additional Information: Build Qt and Qwt Libraries
Related Links
Zynq U-boot

Build PMU Firmware

May 19, 2017, 6:40 pm

≫ Next: Build ARM Trusted Firmware (ATF)

≪ Previous: Build U-Boot

$

0

0

...

Generate and build the PMUFW
hsi% generate_app -hw $hwdsgn -os standalone -proc psu_pmu_0 -app zynqmp_pmufw -compile -sw pmufw -dir <dir_for_new_app>
Next StepBuild Steps
Fetch Sources
Build FSBL
Build Device Tree Compiler (DTC)
(You are here) Build PMU Firmware
Build Arm Trusted Firmware (ATF)
Build U-Boot
PrepareBuild and Modify a Root File System
Build Device Tree Blob
Build Linux Kernel
Prepare Boot Image
Prepare Boot Medium
Setup a Serial Console
Additional Information: Build Qt and Qwt Libraries
Related Links
Zynq-7000 AP SoC Software Developers Guide

Build ARM Trusted Firmware (ATF)

May 19, 2017, 6:41 pm

≫ Next: Build Device Tree Compiler (dtc)

≪ Previous: Build PMU Firmware

$

0

0

...

make PLAT=zynqmp RESET_TO_BL31=1
After the build process completes the bl31.elf binary is created within the /build/zynqmp/release/bl31 directory.
Build Steps
Fetch Sources
Build FSBL
Build Device Tree Compiler (DTC)
Build PMU Firmware
(You are here) Build Arm Trusted Firmware (ATF)
Build U-Boot
Build and Modify a Root File System
Build Device Tree Blob
Build Linux Kernel
Prepare Boot Image
Prepare Boot Medium
Setup a Serial Console
Additional Information: Build Qt and Qwt Libraries

Build Device Tree Compiler (dtc)

May 19, 2017, 6:41 pm

≫ Next: Fetch Sources

≪ Previous: Build ARM Trusted Firmware (ATF)

$

0

0

...

Fetch Sources
Build FSBL
Build(You are here) Build Device Tree
Build PMU Firmware
Build Arm Trusted Firmware (ATF)