element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
FPGA
  • Technologies
  • More
FPGA
Blog Creating a Custom Kria App - Part 2
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join FPGA to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: albertabeef
  • Date Created: 10 Jan 2022 1:14 PM Date Created
  • Views 9240 views
  • Likes 4 likes
  • Comments 19 comments
  • firmware
  • kria
  • vvas
  • overlay
  • kv260
  • vitis-ai
  • app
  • dfx-mgr
  • kria app
  • smart_model_select
  • xmutil
Related
Recommended

Creating a Custom Kria App - Part 2

albertabeef
albertabeef
10 Jan 2022
Creating a Custom Kria App - Part 2

This blog is part of a series of blogs which describe the development steps for an in-depth project tutorial.

  • http://avnet.me/kv260-vvas-sms-2021-1-blog

This part of the tutorial describes how to create the Vitis Platform for our custom Kria App.

Building the Vitis Platform

image

In order to build the kv260_ispMipiRx_vcu_DP platform, simply invoke make as shown below:

$ cd $PROJ_DIR/kv260-vitis

$ make platform PFM=kv260_ispMipiRx_vcu_DP

 

After the build, the Vitis Platform will be located in the following location:

platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1

 

Understanding the Vitis Platform

We already mentioned that the Vitis platform is a wrapper that defines the available resources for use by Vitis.  We can query these resources with the platforminfo command:

$ cd $PROJ_DIR/kv260-vitis

$ platforminfo platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm

==========================

Basic Platform Information

==========================

Platform:           kv260_ispMipiRx_vcu_DP

File:               .../kv260_ispMipiRx_vcu_DP.xpfm

Description:       

kv260_ispMipiRx_vcu_DP

   

 

=====================================

Hardware Platform (Shell) Information

=====================================

Vendor:                           xilinx

Board:                            kv260_ispMipiRx_vcu_DP

Name:                             kv260_ispMipiRx_vcu_DP

Version:                          1.0

Generated Version:                2021.1

Hardware:                         1

Software Emulation:               1

Hardware Emulation:               1

Hardware Emulation Platform:      0

FPGA Family:                      zynquplus

FPGA Device:                      xck26

Board Vendor:                     xilinx.com

Board Name:                       xilinx.com:kv260:1.1

Board Part:                       XCK26-SFVC784-2LV-C

 

=================

Clock Information

=================

  Default Clock Index: 0

  Clock Index:         0

    Frequency:         299.997000

  Clock Index:         1

    Frequency:         599.994000

  Clock Index:         2

    Frequency:         99.999000

 

==================

Memory Information

==================

  Bus SP Tag: HP1

  Bus SP Tag: HP3

  Bus SP Tag: HPC1

  Bus SP Tag: LPD

 

=============================

Software Platform Information

=============================

Number of Runtimes:            1

Default System Configuration:  kv260_ispMipiRx_vcu_DP

System Configurations:

  System Config Name:                      kv260_ispMipiRx_vcu_DP

  System Config Description:               kv260_ispMipiRx_vcu_DP

  System Config Default Processor Group:   smp_linux

  System Config Default Boot Image:        standard

  System Config Is QEMU Supported:         1

  System Config Processor Groups:

    Processor Group Name:      smp_linux

    Processor Group CPU Type:  cortex-a53

    Processor Group OS Name:   linux

  System Config Boot Images:

    Boot Image Name:           standard

    Boot Image Type:          

    Boot Image BIF:            kv260_ispMipiRx_vcu_DP/boot/linux.bif

    Boot Image Data:           kv260_ispMipiRx_vcu_DP/smp_linux/image

    Boot Image Boot Mode:      sd

    Boot Image RootFileSystem:

    Boot Image Mount Path:     /mnt

    Boot Image Read Me:        kv260_ispMipiRx_vcu_DP/boot/generic.readme

    Boot Image QEMU Args:      kv260_ispMipiRx_vcu_DP/qemu/pmu_args.txt:kv260_ispMipiRx_vcu_DP/qemu/qemu_args.txt

    Boot Image QEMU Boot:     

    Boot Image QEMU Dev Tree: 

Supported Runtimes:

  Runtime: OpenCL

 

We can see that the following clocks and interconnects are available for use by Vitis:

  • Clocks
    • 300MHz
    • 600MHz
    • 100MHz
  • High-Performance Interconnect
    • LPD
    • HP1
    • HP3
    • HPC1

 

This information will be important when configuring a Vitis Example or Overlay to be built with this Vitis platform.

 

Next Steps

The following blogs cover the previous development steps for this in-depth project tutorial.

  • http://avnet.me/kv260-vvas-sms-2021-1-part1

The following blogs will cover the remaining development steps for this in-depth project tutorial.

  • http://avnet.me/kv260-vvas-sms-2021-1-part3
  • http://avnet.me/kv260-vvas-sms-2021-1-part4
  • http://avnet.me/kv260-vvas-sms-2021-1-part5
  • http://avnet.me/kv260-vvas-sms-2021-1-part6
  • http://avnet.me/kv260-vvas-sms-2021-1-part7
  • Sign in to reply

Top Comments

  • juanyi
    juanyi over 3 years ago in reply to albertabeef +2
    I have a positive news to share, searching through xilinx support and found this thread. https://support.xilinx.com/s/question/0D52E00006vFXkwSAG/is-there-a-workaround-for-vivado-rdiprog-crash-during-synth…
  • schneisw
    schneisw over 3 years ago +1
    Tip: If you are getting some errors after running make, you might not have sourced the settings scripts for both Vivado and Vitis. I noticed this after doing neither, and then only Vivado, which incidentally…
  • Jan Cumps
    Jan Cumps over 3 years ago in reply to juanyi +1
    Before my Ubuntu knows where the tools are, I first have to execute an environment setting script: for Vivado: source /tools/Xilinx/Vivado/2020.2/settings64.sh for Vitis: source /tools/Xilinx…
  • juanyi
    juanyi over 3 years ago in reply to albertabeef

    Happy to ask, happier to share Smiley

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • albertabeef
    albertabeef over 3 years ago in reply to juanyi

    Juanyi,

    Wow, great debugging of the issue !

    Thank you very much for sharing your solution with the community, this is VERY appreciated Slight smile

    Regards,

    Mario.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • juanyi
    juanyi over 3 years ago in reply to albertabeef

    I have a positive news to share, searching through xilinx support and found this thread. https://support.xilinx.com/s/question/0D52E00006vFXkwSAG/is-there-a-workaround-for-vivado-rdiprog-crash-during-synth-while-running-20211-on-ubuntu-18046-lts?language=en_US 

    They points out that the RAM issue with linux on VM (especially small RAM machine like mine), it needs swap memory to cater for Vivado large appetite for RAM. I then follow this https://askubuntu.com/questions/920595/fallocate-fallocate-failed-text-file-busy-in-ubuntu-17-04 to create swap memory and finally after running ~5hrs, managed to generate the XSA file.

    Next to build platform. :)

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • albertabeef
    albertabeef over 3 years ago in reply to juanyi

    I do not recognize this error, so am not able to help.  Very sorry about that.

    The kv260-vitis repository is provided for use with 2021.1 tools.

    If you change tool version, you will run into other issues, which will not be supported.

    I recommend working through the build of the kv260 vitis platforms with 2021.1 (update1).

    Since this is a Xilinx design, please reach out for help on the Xilinx forums ... 

    Best Regards,

    Mario.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • juanyi
    juanyi over 3 years ago in reply to juanyi

    Message below is what I see when I run make xsa for the platforms in kv260-vitis folder.

    [Thu Feb 24 22:53:12 2022] Launched synth _1...

    Run output will be captured here: /home/user/Desktop/CustomApp/kv260-vitis/platforms/vivado/kv260_ispMipiRx_vcu_DP/project/kv260_ispMipiRx_vcu_DP.runs/synth_1/runme.log

    launch_runs: TIme (s): cpu = 00:00:07 ;  elapsed = 00:00:08 . Memory (MB): peak = 3999.527 ; gain = 456.219 ; free physical = 3494 ; free virtual = 8942

    [Thur Feb 24 22:53:12 2022] Waiting for synth_1 to finish...

    /home/yyee/Desktop/Xilinx/Vivado/2021.1/bin/loader: line312:  4630 Killed                                   "$RDI_PROG"      "$@"

    Makefile:29: recipe for target 'project/kv260_ispMipiRx_vcu_DP.xsa' failed

    Make: *** [project/kv260_ispMipiRx_vcu_DP.xsa] Error 137

    It is the same error code caused by the same line in Vivado bin loader file. Something wrong with my installation? Should I update it to 2021.2?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube