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

PS and PL based Ethernet in Zynq MPSoC

$
0
0

PSwxPS and PL
1. Introduction
The page focus of this application note is onupon Ethernet peripherals
...
UltraScale+ MPSoC. This application noteIt describes using
...
physical interface Giga transceivers in PS.
...
or 10G BASE -R physical interface
...
in PL. This application noteIt also describes
...
of Ethernet ports,ports and provide kernel-modekernel mode Linux device drivers.
The designsdesign provided with
...
multiple Ethernet ports,ports and provide
...
Ethernet performance measurementsmeasurement with checksum offload support enabled.enable.
This page discusses the following.
Hardware and software design build steps for xapp1305 and xapp1306.
...
xapp1306. Visit this pagePerformance page for Performance
2. XAPP1305
XAPP1305 introduces:-
...
PL-Ethernet designs
Supports Vivado 2016.4
Petalinux 2016.4 SDK
macb driver support
Xilinx PHYSupports Xilinx phy driver supports for 1000Base-X
Four designs are described in this application note. The designs support Vivado IP Integrator tool flow.
Building PS-MIO and PS-EMIO design
...
2. Navigate to hardware/vivado/scripts/ps_emio_eth_1g for PS EMIO Ethernet design
$ vivado -source ps_emio_eth_1g_top.tcl
...
step creates thea vivado project and
...
loaded (See below Figure).tool snapshot below).
Relevant constraints file is also associated with the design.
NOTE : In this design "GEM3" is also enabled along with GEM0 in ZYNQ UltraScale+ GUI.
...
6. Choose "Include bitstream" option, and click OK (see below Figure)
{ps_emio_eth_1g_6.JPG}
...
loaded into SDSDK tool.
Building PL Ethernet(1G)
To rebuild the hardware design, execute the following (after setting up Vivado environment).
...
Prerequisites
This section lists the requirements for the PetaLinux Tools Installation
...
Xilinx website download section.
Refer to section 3.4 for PetaLinux installation instructions.
2.2 Directory structure
The xapp1305 is released with the source code, Xilinx Vivado and Petalinux projects and an SD card image that enables the user to run the demonstration.
It also includes the binaries necessary to configure and boot the Zynq UltraScale+ MPSoC board.
This wiki page assumes the user has already downloadedDownload and unzip the XAPP package and extracted its contentsfrom xilinx website. Copy the content in to the XAPP home.
directory referred to
directory.
This DIrectory is refered
as XAPP_HOME in this wiki.rest of section.
<Add directory structure here>
2.3 PS MIO and PS EMIO Ethernet
2.3.1 PS MIO and PS EMIO Ethernet BSP installation
...
necessary design sources andsources, configuration files, including pre-built and tested hardware images and software images, ready for download to your boardimages.
2.3.1.1 Create PS MIO and PS EMIO Ethernet project from PetaLinux BSP
Run petalinux-create command on the console
...
Check and enable the Xilinx PHY driver from kernel configuration.
bash> petalinux-config -c kernel
Device Drivers>Drivers > Network device
<*> Drivers for xilinx PHYs
Save the changes and exit.
2.3.1.4 Edit device for PS EMIO
Follow thisbelow process for
2.3.1.5 Apply FSBL patch
Follow this process for applying patch in FSBL.
...
bash> petalinux-package --boot --fsbl=zynq_fsbl.elf --fpga=$PETALINUX/xapp1305_ps_emio_eth/images/linux/ps_emio_eth_1g_wrapper.bit --u-boot
2.3.1.7 SD Images
SDSDcard Deployable binaries:-
a) BOOT.bin
b) image.ub
forPSfor PS emio
Copy BOOT.BIN and image.ub from $PETALINUX/ xapp1305_ps_emio_eth/images/linux to SD partition
For PS mio
Copy BOOT.BIN and image.ub from $PETALINUX/ xapp1305_ps_mio_eth/images/linux to SD partition
2.4 PL Ethernet
...
provides installable BSPBSP, which includes
...
necessary design sources andsources, configuration files, including pre-built and tested hardware images and software images, ready for download to your board or for booting in the QEMU system simulation environment.images.
The design supports with the auto-negotiation for speeds of 10/100/1000 Mbps and full duplex mode.
NOTE : Check-sum offload in enabled in the default configuration.
...
Copy BOOT.BIN and image.ub from $PETALINUX/ xapp1305_pl_eth_10g/images/linux to SD partition and run the setup.
3. XAPP1306
Here are the steps to create software for XAPP1306.
3.1 Building LWIP Images
...
appropriate hdf file) (forfile for A53 or R5).R5)x. On top
To include lwip in FSBL, click on system.mss file in FSBL_BSP generated by tool.
...
setting". Please chekcheck below images
{lvip-config_modify.jpg}
Please check the below image for enable lwip in BSP.
...
Appendix A
How to patch Linux kernel in petalinux 2016.4:
...
Linux kernel we must instruct tool
To do that, copy patch file in <PROJ_DIR>\project-spec\meta-user\recipes-kernel\linux\linux-xlnx location.
After that add below lines to to <PROJ_DIR>\meta-user\recipes-kernel\linux\linux-xlnx_%.bbapend file.
...
SRC_URI += "file://0001-kernel-10G-axienet.patch"
The first line instruct petalinux to clone new kernel copy from the git link provided here.
...
git repository. So here we are using xilinx-v2016.4Xilinx-v2016.4 is used for 2016.4
Third line is name of patch file which to be applied on this cloned kernel. This should have same name as the file present in <PROJ_DIR>\project-spec\meta-user\recipes-kernel\linux\linux-xlnx.
In my case,the project, the patch
How to patch FSBL in petalinux 2016.4:
To patch FSBL we must instruct tool to apply patch on it. FSBL soruce code is part of project only. There is not need of extra cloning of the same.

uboot.PNG

Performance tests procedure and results with LWIP

$
0
0

1G/10G Performanceperfomance testing for psPS Ethernet, PL
...
PS+PL Ethernet
1. Introduction
Below are the Linux tests performed on 1G/10G Linux driver.

PS and PL based Ethernet in Zynq MPSoC

$
0
0

wxPSPS and PL
1. Introduction
The page focus upon Ethernet peripherals in the Zynq UltraScale+ MPSoC. It describes using the processing system (PS) based gigabit Ethernet MAC (GEM) through the extended multiplexed I/O (EMIO) and multiplexed I/O (MIO) interface with the 1G physical interface in PS. It also includes the 1000BASE-X or 10G BASE -R physical interface using high speed transceivers in PL. It also describes the usage of Ethernet jumbo frames in both PS and PL. In addition to this, it also includes throughput numbers for all combinations. The designs provided with this application note enable the use of Ethernet ports and provide kernel mode Linux device drivers.
...
Copy BOOT.BIN and image.ub from $PETALINUX/ xapp1305_pl_eth_10g/images/linux to SD partition and run the setup.
3. XAPP1306
...
for XAPP1306.
3.1 Building LWIP Images
Include lwip library in FSBL ( generated with appropriate hdf file for A53 or R5)x. On top of this this FSBL create empty application and import iperf source code in it.

Performance tests procedure and results with LWIP

$
0
0

...
PS+PL Ethernet
1. Introduction
Below are the Linux tests performed on 1G/10G Linux driver.

Performance tests procedure and results with LWIP

$
0
0

1G/10G perfomanceperformance testing for
1. Introduction
Below are the Linux tests performed on 1G/10G Linux driver.

Performance tests procedure and results with LWIP

$
0
0

Performance tests procedure and results with LWIP

$
0
0
...
1G/10G performance testing for PS Ethernet, PL Ethernet and PS+PL Ethernet
1. Introduction
Below areThis page provides the Linux tests performed on 1G/10G Linux driver.performance number for XAPP1306 and XAPP1306. t also includes procedure to run tests.
Netperf is used to to take this performance number(TCP and UDP).
Performance numbers for all combinations are on below link.
...
With LWIP (xapp 1306):
1. 2016.4
2. Setting up and testing PS Ethernet
2.1 PS Ethernet with Linux
Kernel version used (4.4)
...
Refer to this
Please note that the static IP address assignment on the laptop/PC should be done.
3. Setting up and testing PL Ethernet
3.1 PL Ethernet with Linux (1G)
Kernel version used (4.4)
...
-> Make sure CPU frequency is of the order of 1.3 GHz for ZynqMP.
-> Bus speed should be negotiated at 10gbps/Full duplex
4.4.Setting up and testing PS+PL Ethernet
4.1 PS+PL Ethernet with Linux
Kernel version used (4.4)
...
rxperf, PC
{http://confluence.xilinx.com/download/attachments/29199788/rxperf.png?version=1&modificationDate=1468401862588&api=v2}
code
code


Performance tests procedure and results with LWIP

$
0
0
...
Refer to this
Please note that the static IP address assignment on the laptop/PC should be done.
3. Setting3.Setting up and
3.1 PL Ethernet with Linux (1G)
Kernel version used (4.4)

Performance tests procedure and results with LWIP

$
0
0
...
Refer to this
Please note that the static IP address assignment on the laptop/PC should be done.
3.Setting3. Setting up and
3.1 PL Ethernet with Linux (1G)
Kernel version used (4.4)

xapp1305.png

xapp1305.jpg

xapp1306.png

PS and PL based Ethernet in Zynq MPSoC

$
0
0
...
Download and unzip the XAPP package from xilinx website. Copy the content in to XAPP directory.
This DIrectory is refered as XAPP_HOME in rest of section.
<Add directory2.2.1 xapp1305
{xapp1305.jpg} Directory Structure for xapp1305
2.2.2 xapp1306
{xapp1306.png} Directory
structure here>for xapp1306
2.3 PS MIO and PS EMIO Ethernet
2.3.1 PS MIO and PS EMIO Ethernet BSP installation

Zynq UltraScale MPSoC Base TRD 2016.4

$
0
0

1 Revision History
This wiki page complements the 2016.3 version of the Base TRD. For other versions, refer to the Zynq UltraScale+ MPSoC Base TRD overview page.
Change Log:
Update all projects, IP and tools versions to 2016.3
Add support for ZCU102 rev 1.0 board with ES2 silicon
Split reference design into 9 design modules with dedicated tutorials
Remove support for HDMI input via FMC-HDMI-CAM
Add USB webcam support for video capture (USB2 only!)
Add virtual video device (vivid) support for video capture
Use X11 Qt and Mali backend instead of fbdev
2 Overview
The Zynq UltraScale+ MPSoC Base Targeted Reference Design (TRD) is an embedded video processing application running on a combination of APU (SMP Linux), RPU (bare-metal) and PL.
The design consists of the following video data paths:
Video capture pipelines capturing video from:
a virtual video device (vivid) implemented purely in software
a USB webcam connected to the PS (optional)
a test pattern generator (TPG) implemented inside the PL
A memory-to-memory processing pipeline implementing a 2D-convolution filter with programmable coefficients.
A display pipeline with two layers, one used for video and the other for a graphical user interface (GUI) rendered by the GPU.
The TRD demonstrates the value of offloading computation intensive tasks like the 2D-convolution filter from the PS onto PL, thereby freeing APU resources. The APU load is plotted on the GUI to compare a pure software vs hardware accelerated implementation. The RPU is used to monitor the live memory throughput of the design by reading the built-in AXI performance monitors (APM) inside the PS. The data is sent to the APU via the OpenAMP communication framework and plotted on the GUI.
This wiki contains information about:
How to setup the ZCU102 evaluation board and run the reference design.
How to build all the TRD components based on the provided source files via detailed step-by-step tutorials.
Additional material that is not hosted on the wiki:
User Guide containing information about system, software and hardware architecture.
Reference Design Zip File for ZCU102 rev 1.0 / ES2 silicon including all source code and project files.
Reference Design Zip File for ZCU102 rev D / ES1 silicon including all source code and project files.
Third Party Library Sources for separately licensed material that is not included in the reference design.
Note: Certain material in this reference design is separately licensed by third parties and may be subject to the GNU General Public License version 2, the GNU Lesser General License version 2.1, or other licenses.
3 Software Tools and System Requirements
3.1 Hardware
Required:
ZCU102 evaluation board / power cable
Monitor with DisplayPort input supporting one of the following resolutions:
3840x2160 or
1920x1080 or
1280x720
Display Port cable (DP certified)
USB hub with mouse and keyboard
SD card
Optional:
USB webcam
3.2 Software Tools
Required:
Linux host machine for all tool flow tutorials (see here for detailed OS requirements)
SDSoC Development Environment version 2016.3
Xilinx Software Development Kit (XSDK) version 2016.3
PetaLinux Tools version 2016.3
Git distributed version control system
GNU make utility version 3.81 or higher
Optional:
Silicon Labs quad CP210x USB-to-UART bridge driver
Serial terminal emulator e.g. teraterm
3.3 Licensing
The video Test Pattern Generator IP inside the Vivado project requires a license which can be obtained from here.
Steps to generate the license:
Click on the link mentioned above.
Fill in the login details and proceed.
Click on “Generate Node-Locked License" icon as shown in the picture:
{TPG_lic.jpg}
Under system information, give the host details.
Proceed until you get the license agreement and accept it.
The License (.lic file) will be sent to the email-id mentioned in the login details.
Copy the license file locally and give the same path in the SDSOC license manager.
3.4 Compatibility
The reference design has been tested successfully with the following user-supplied components.
DisplayPort Monitor:
Make/Model
Native Resolution
Viewsonic VP2780-4K
3840x2160 (30Hz)
LG 27MU67-B
3840x2160 (30Hz)
Acer S277HK
3840x2160 (30Hz)
Dell U2414H
1920x1080 (60Hz)
GeChic On-Lap1303H
1920x1080 (60Hz)
DisplayPort Cable:
Cable Matters DisplayPort Cable-E342987
Monster Advanced DisplayPort Cable-E194698
USB Webcam:
Make/Model
Supported Resolutions
Supported Formats
Logitech HD Pro Webcam C920
1920x1080 (5fps), 1280x720 (10fps)
YUYV
Logitech HD Webcam C525
1920x1080 (5fps), 1280x720 (10fps)
YUYV
4 Design Files
The top-level directory structure is shown in the figure below.
{base-trd-2016-3-dir-structure.png}
4.1 Design Modules
The reference design is split into 9 design modules DM1 to DM9:
DM1 – APU SMP Linux
DM2 – RPU0 FreeRTOS Application
DM3 – RPU1 Bare-metal Application
DM4 – APU/RPU1 Inter Process Communication
DM5 – APU Qt Application
DM6 – PL Video Capture
DM7 – OpenCV-based Image Processing
DM8 – PL-accelerated Image Processing
DM9 – Full-fledged Base TRD
Each module is described in more detail in UG1221 and on the respective tutorial page.
The following table shows the dependency matrix between different modules. For example: DM6 (row) depends on or builds on top of modules DM1 and DM5 (columns).
DM1
DM2
DM3
DM4
DM5
DM6
DM7
DM8
DM1
DM2
DM3
DM4
+
+
DM5
+
DM6
+
+
DM7
+
+
+
DM8
+
+
+
+
DM9
+
+
+
+
+
+
+
+
4.2 Design Components
The below figure shows the relevant design components for DM9 as well as inter-dependencies and generated output products.
{base-trd-2016-3-dm9-dc-dependencies.png}
The below table shows which design components are used in which design modules. A graphical view for each design module is provided on the respective design module tutorial page.
Design Component
Design Module
DM1
DM2
DM3
DM4
DM5
DM6
DM7
DM8
DM9
apu/perfapm-client/perfapm-client
Y
Y
apu/perfapm-client/perfapm-client-test
Y
apu/petalinux_bsp
Y
Y
Y
Y
Y
Y
Y
apu/videao_app/video_lib
Y
Y
Y
Y
Y
apu/videao_app/video_qt2
Y
Y
Y
Y
Y
apu/zcu102_base_trd/samples/filter2d
Y
Y
Y
pl/zcu102_base_trd
Y
pl/zcu102_dp_only
Y
pmu/pmu_fw
Y
Y
Y
Y
Y
Y
Y
Y
Y
rpu0/heartbeat
Y
Y
rpu1/perfapm-server/perfapm
Y
Y
Y
rpu1/perfapm-server/perfapm-ctl
Y
rpu1/perfapm-server/perfapm-server
Y
Y
5 Tutorials
5.1 Board Setupboard_setup
Required:
Connect power supply to J52.
Connect USB mouse and keyboard using a USB hub to J83.
Connect DisplayPort cable to P11; connect other end to monitor.
Insert SD card (FAT formatted) with binaries copied from $TRD_HOME/images/dm9 directory.
Connect micro-USB cable to J83 USB UART connector; use the following settings for your terminal emulator:
Baud Rate: 115200
Data: 8 bit
Parity: None
Stop: 1 bit
Flow Control: None
Optional:
Connect USB webcam to a USB hub to J83.
Jumpers & Switches:
Set boot mode according to your board and silicon revision
For rev D with ES1 silicon: SW6[4:1] - on,off,on,off
For rev 1.0 with ES2 silicon: SW6[4:1] - on,off,off,off
Configure USB 2.0 jumpers for host mode
J110: 2-3
J109: 1-2
J112: 2-3
J7: 1-2
J113: 1-2
{base-trd-2016-3-board-setup.png}
To run the prebuilt SD card image for design module 9, follow the instructions here .
5.2 Build and Run Flow
The following tutorials assume that the $TRD_HOME environment variable has been set as below.
For rev 1.0 / ES2:
% export TRD_HOME=</path/to/downloaded/zip-file>/rdf0421-zcu102-base-trd-2016-3
For rev D / ES1:
% export TRD_HOME=</path/to/downloaded/zip-file>/zcu102-base-trd-2016-3
For some modules, the $PETALINUX environment variables needs to be set as well. This is done automatically when you source the PetaLinux settings.sh script (see PetaLinux installation guide).
For the individual tutorials, follow the links below:
DM1 Tutorial – APU SMP Linux
DM2 Tutorial – RPU0 FreeRTOS Application
DM3 Tutorial – RPU1 Bare-metal Application
DM4 Tutorial – APU/RPU1 Inter Process Communication
DM5 Tutorial – APU Qt Application
DM6 Tutorial – PL Video Capture
DM7 Tutorial – OpenCV-based Image Processing
DM8 Tutorial – PL-accelerated Image Processing
DM9 Tutorial – Full-fledged Base TRD
6 Other Information
6.1 Known Issues
The board doesn't boot and the INIT_B LED stays red.
Frequency: Rare
Workaround: Power cycle the board
SDSoC accelerator code runs very slow in pure software implementation when Debug configuration is used
Frequency: Always
Workaround: Set project build configurations to Release which sets sdsoc compiler to optimize most (-O3)
Linux 'reboot' command not working
Frequency: Always
Workaround: Power cycle the board
At 1080p and 720p resolutions, the mouse cursor disappears when moved too far to the right and/or bottom of the screen
Frequency: Always
Workaround: Move mouse toward left and/or top until the cursor reappers on the screen
PetaLinux prints the following warning message: WARNING: Failed to pack PMUFW, pre-built PMUFW doesnt exist. See help to load custom pmufw
Frequency: Always
Workaround: Message can be ignored
Video capture cannot be started in GUI for native display of 1280x720 or 1920x1080 in auto-detection mode
Frequency: Always
Workaround: Edit the file autostart.sh and modify the arguments for the desired target resolution, e.g. for 1920x1080 change line
video_qt2_wrap.sh &
to
video_qt2_wrap.sh -r 1920x1080 &
or close the application and restart with command
run_video.sh -r 1920x1080
6.2 Limitations
The application only supports the following display resolutions: 3840x2160p30, 1920x1080p60, and 1280x720p60.
The application does not support audio.
Only USB2.0 webcams are supported at this point.
Make sure the DisplayPort cable is plugged in when you power on the board, otherwise the framebuffer console will default to 1024x768 resolution and the application will not start.
DP-to-HDMI adapters are not supported, see AR 67462
7 Support
To obtain technical support for this reference design, go to the:
Xilinx Answers Database to locate answers to known issues
Xilinx Community Forums to ask questions or discuss technical details and issues. Please make sure to browse the existing topics first before filing a new topic. If you do file a new topic, make sure it is filed in the sub-forum that best describes your issue or question e.g. Embedded Linux for any Linux related questions. Please include "ZCU102 Base TRD" and the release version in the topic name along with a brief summary of the issue.


Zynq UltraScale MPSoC Base TRD 2016.4

$
0
0
{under.jpg}
1 Revision History
This wiki page complements the 2016.3 version of the Base TRD. For other versions, refer to the Zynq UltraScale+ MPSoC Base TRD overview page.

Zynq UltraScale MPSoC Base TRD 2016.4 - Design Module 1

$
0
0
Return to the Design Tutorials Overview.
Design Overview
This design module showcases the following:
Boot APU only
FSBL, ATF, U-boot, PMU-FW
APU OS: SMP Linux
Ethernet via FTP/SCP
Serial console via UART0
File system via SD, USB or SATA
Standard Linux applications on rootfs
{base-trd-2016-3-dm1-bd.png}
Design Components
pmu_fw
petalinux_bsp
zynqmp_fsbl
bl31
u-boot
kernel
device tree
rootfs
Build Flow Tutorials
PMU Firmwarepmu_fw
The pmu_fw application is a bare-metal application that executes on the PMU MicroBlaze. It is loaded by the CSU early on in the boot process before the FSBL executes. The application's primary responsibility is to handle platform management.
Create a new XSDK workspace.
% cd $TRD_HOME/pmu/pmu_fw
% xsdk -workspace . &
Click 'Import Project' from the welcome screen, browse to the current working directory and make sure the pmu_fw, pmu_fw_bsp, and zcu102_base_trd_hw_platform projects are selected. Click Finish.
{mpsoc_base_trd_pmu_fw.png}
Right-click the pmu_fw project and select 'Build Project'.
Copy the generated pmu_fw executable into the PetaLinux BSP.
cp $TRD_HOME/pmu/pmu_fw/pmu_fw/Debug/pmu_fw.elf $TRD_HOME/apu/petalinux_bsp/images/linux
Petalinux BSP
This tutorial shows how to build the Linux image and boot image using the PetaLinux build tool.
Configure the PetaLinux project.
% cd $TRD_HOME/apu/petalinux_bsp
% petalinux-config --get-hw-description=./hw-description --oldconfig
Select the device-tree matching design module 5 and build all Linux image components
% cd subsystems/linux/configs/device-tree
% cp system-dm1.dts system-top.dts
% petalinux-build
% cd -
Create a boot image.
% cd images/linux
% petalinux-package --boot --bif=dm1.bif --force
Copy the generated boot image and Linux image to the dm1 SD card directory.
% mkdir -p $TRD_HOME/images/dm1
% cp BOOT.BIN image.ub $TRD_HOME/images/dm1
Run Flow Tutorial
See here for board setup instructions.
Copy all the files from the $TRD_HOME/images/dm1 SD card directory to a FAT formatted SD card.
Power on the board to boot the images; make sure all power rail LEDs are lit green.
The user can now see the linux-boot on the serial console:
{linux_fbconsole.png}
Upon completion of the linux-boot, use the below login and password to log into the framebuffer or serial console:
root@Xilinx-ZCU102-2016_3 login: root
password: root
The SD card file system is mounted at /media/card
References
How to mount a USB3 or SATA hard drive:
http://www.wiki.xilinx.com/SATA
http://www.wiki.xilinx.com/Zynq+Ultrascale+MPSOC+Linux+USB+device+driver (under host mode)

Zynq UltraScale MPSoC Base TRD 2016.4 - Design Module 2

$
0
0
Return to the Design Tutorials Overview.
Design Overview
This design module demonstrates the FreeRTOS and application running on RPU-0, where:
FreeRTOS boots on RPU-0
FreeRTOS application "heartbeat" prints periodic messages on UART-1
{base-trd-2016-3-dm2-bd.png}
Design Components
pmu_fw
petalinux_bsp
zynqmp_fsbl
heartbeat.elf
Build Flow Tutorials
PMU Firmware
Please refer to design module 1 - PMU firmware for instructions or skip this step if you have built the PMU firmware in a previous module.
Heartbeat Applicationheartbeat
The heartbeat application is a FreeRTOS application that executes on RPU-0 after the FSBL has finished. This application is a simple dual task application that demonstrates communication between the two tasks by printing messages to the UART1 console.
Create a new XSDK workspace.
% cd $TRD_HOME/rpu0/heartbeat
% xsdk -workspace . &
Click 'Import Project' from the welcome screen, browse to the current working directory and make sure the heartbeat, heartbeat_bsp, and zcu102_base_trd_wrapper_hw_platform_0 projects are selected. Click Finish.
{zcu102_base_trd_2016_1_heartbeat_projects.jpg}
Right-click on the heartbeat project and select 'Build Project'.
Copy the generated heartbeat executable into the PetaLinux BSP.
cp heartbeat/Debug/heartbeat.elf $TRD_HOME/apu/petalinux_bsp/images/linux
PetaLinux BSP
This tutorial shows how to build the first stage bootloader (FSBL) and boot image using the PetaLinux build tool.
The petalinux-config step can be skipped if this was already done in a previous module.
% cd $TRD_HOME/apu/petalinux_bsp
% petalinux-config --get-hw-description=./hw-description --oldconfig
Build the FSBL. This step can be skipped if this was already done in a previous module.
petalinux-build -c bootloader
Create a boot image.
% cd images/linux
% petalinux-package --boot --bif=dm2.bif --force
Copy the generated boot image to the dm2 SD card directory.
% mkdir -p $TRD_HOME/images/dm2
% cp BOOT.BIN $TRD_HOME/images/dm2
Run Flow Tutorial
See here for board setup instructions.
Copy all the files from the $TRD_HOME/images/dm2 SD card directory to a FAT formatted SD card.
Power on the board to boot the images; make sure all power rail LEDs are lit green.
The user can now see FSBL and PMU-firmware prints on UART-0 and prints from heartbeat application can be viewed on UART-1 which is shown in the following picture:
{heartbeat_console.png}

xapp1305.png

xapp1305.jpg

Viewing all 11776 articles
Browse latest View live


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