Group Actions
Engagement
  • Author Author: albertabeef
  • Date Created: Date Created
  • Views 7092 views
  • Likes 4 likes
  • Comments 19 comments
Related
Recommended

Creating a Custom Kria App - Part 2

albertabeef
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.

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.

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

Parents

  • Seeking help. Following the advice to source all the petalinux & xilinx vivao (or vitis) setting, i managed to start the build, but after long hours of running (>12hrs), it come to this error:

    [Sun Feb 20 17:44:01 2022] Waiting for synth_1 to finish...

    /home/user/Desktop/Xilinx/Vivado/2021.1/bin/loader: line 312: 4616 killed       "$RDI_PROG"   "$@"

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

    make[2]: *** [project/kv260_ispMipiRx_vcu_DP.xsa] Error 137

    make[2]: Leaving directory 'home/user/Desktop/CustomApp/kv260-vitis/platforms/vivado/kv260_ispMipiRx_vcu_DP'

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

    make[1]: *** [vivado/kv260_ispMipiRx_vcu_DP/project/kv260_ispMipiRx_vcu_DP.xsa] Error 2

    make[1]: Leaving directory 'home/user/Desktop/CustomApp/kv260-vitis/platforms'

    Makefile:78: recipe for target '/home/user/Desktop/CustomApp/kv260-vitis/platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm' failed

    make: *** [/home/user/Desktop/CustomApp/kv260-vitis/platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm] Error 2

    I can't check the runme.log to see what went wrong because my VM become freeze after running this step. Hoping someone can point me how to troubleshoot this. Thanks.

Comment

  • Seeking help. Following the advice to source all the petalinux & xilinx vivao (or vitis) setting, i managed to start the build, but after long hours of running (>12hrs), it come to this error:

    [Sun Feb 20 17:44:01 2022] Waiting for synth_1 to finish...

    /home/user/Desktop/Xilinx/Vivado/2021.1/bin/loader: line 312: 4616 killed       "$RDI_PROG"   "$@"

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

    make[2]: *** [project/kv260_ispMipiRx_vcu_DP.xsa] Error 137

    make[2]: Leaving directory 'home/user/Desktop/CustomApp/kv260-vitis/platforms/vivado/kv260_ispMipiRx_vcu_DP'

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

    make[1]: *** [vivado/kv260_ispMipiRx_vcu_DP/project/kv260_ispMipiRx_vcu_DP.xsa] Error 2

    make[1]: Leaving directory 'home/user/Desktop/CustomApp/kv260-vitis/platforms'

    Makefile:78: recipe for target '/home/user/Desktop/CustomApp/kv260-vitis/platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm' failed

    make: *** [/home/user/Desktop/CustomApp/kv260-vitis/platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm] Error 2

    I can't check the runme.log to see what went wrong because my VM become freeze after running this step. Hoping someone can point me how to troubleshoot this. Thanks.

Children
  • in reply to juanyi

    I had reviewed back the steps in this https://xilinx.github.io/kria-apps-docs/main/build/html/docs/build_vivado_design.html#prerequisites, and it says i need to make extensible XSA, has pointed it out before. So I tried to make XSA, but it come to error too, it is recipe failed blablabla, the messages before the error are saying board cannot find so I guess I need to set the board preset follow this this https://github.com/Xilinx/kv260-vitis/tree/release-2021.1/platforms/vivado/kv260_ispMipiRx_vcu_DP, but i can't find this file Vivado_init.tcl, it's not in the directory shown in the readme.

    Linux: $HOME/.Xilinx/Vivado/Vivado_init.tcl

    Can someone tell me how to get through this? It's like detective game, one clue lead to another one, again and again..

  • in reply to juanyi

    Juanyi,

    Have you configured your VM machine to have sufficient resources (disk, memory) ?
    Can you check if you disk space is full ?

    In the message you shared, it looks like a process was killed : "home/user/Desktop/Xilinx/Vivado/2021.1/bin/loader: line 312: 4616 killed"

    Regards,

    Mario.

  • in reply to albertabeef

    I had allocated 500GB memory & 10GB RAM for the VM. Using df -h in terminal, I can see the memory is ample.
    image

    From the VM session monitor, what i observer is, after running all those build or make steps, the RAM usage will still remain fully consumed even if the step already stop/end. This is where the VM freeze.

    As for the line which says bin/loader: line312: 4616 killed, this is directory where i installed Vivado. Open the file and scroll to line 312, shown below.

    image

    No idea what that is though.

  • 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?

  • 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.