cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
HeroGian91
Observer
Observer
298 Views
Registered: ‎04-28-2020

Platform error in vitis linking

Jump to solution

Goodmorning,

I am trying to follow the steps detailed in this tutorial https://www.xilinx.com/html_docs/xilinx2020_2/vitis_doc/integrate_ai_engine_application.html to integrate two PL kernels into a custom platform. In particular I have some problems with the step 3 (Linking the system).

I started creating two .xo files with the following commands:

 

PLATFORM="base_pfm_vck190/export/base_pfm_vck190/base_pfm_vck190.xpfm"

v++ --compile                \
    -t hw                    \
    --platform "${PLATFORM}" \
    -g                       \
    -k mm2s src/pl/mm2s.cpp  \
    -o mm2s.xo               \
    --save-temps

v++ --compile                \
    -t hw                    \
    --platform "${PLATFORM}" \
    -g                       \
    -k s2mm src/pl/s2mm.cpp  \
    -o s2mm.xo               \
    --save-temps

 


Then I tried to create a final xclbin file, based on a custom made xpfm, that is the same used to build the previous kernels:

 

PLATFORM="base_pfm_vck190/export/base_pfm_vck190/base_pfm_vck190.xpfm"

v++ --link                              \
	-t hw                               \
    --platform "${PLATFORM}"            \
	--config src/binary_container_1.cfg \
	-o"binary_container_1.xclbin"       \
	mm2s.xo s2mm.xo                     \
	libadf.a

 


this command fails with these errors:

 

ERROR: [VPL 60-1258] No valid platform was found that matches 'base_pfm_vck190/export/base_pfm_vck190/base_pfm_vck190.xpfm'. Please make sure that the platform is specified correctly, and the platform has the right version number. The platform repo paths are:
        /tools/Xilinx/Vitis/2020.2/platforms
The valid platforms found from the above repo paths are:

ERROR: [VPL 60-587] Failed to add a platform: specified platform base_pfm_vck190/export/base_pfm_vck190/base_pfm_vck190.xpfm is not found or is not valid
ERROR: [VPL 60-628] Kernel link setup failed to complete
ERROR: [VPL 60-806] Failed to finish platform linker
INFO: [v++ 60-1442] [15:57:49] Run run_link: Step vpl: Failed
Time (s): cpu = 00:00:01 ; elapsed = 00:00:01 . Memory (MB): peak = 1584.973 ; gain = 0.000 ; free physical = 8186 ; free virtual = 57345
ERROR: [v++ 60-661] v++ link run 'run_link' failed
ERROR: [v++ 60-626] Kernel link failed to complete
ERROR: [v++ 60-703] Failed to finish linking
INFO: [v++ 60-1653] Closing dispatch client.

 

It seems the compiler try to use a platform inside /tools/Xilinx/Vitis/2020.2/platforms despite I specified my platform with --platform option.
How can I solve this problem?

Thanks

0 Kudos
1 Solution

Accepted Solutions
HeroGian91
Observer
Observer
167 Views
Registered: ‎04-28-2020

I solved the problems, I had not noticed that, unlike v++ --compile, the linker required the full platform folder and not only the xpfm file.
Thanks

View solution in original post

4 Replies
florentw
Moderator
Moderator
282 Views
Registered: ‎11-09-2015

Hi @HeroGian91 

Can you share a test case? Or at least the xpfm file?

The log says it is not found or not valid. So I want to check if it is valid


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
HeroGian91
Observer
Observer
253 Views
Registered: ‎04-28-2020

Thanks @florentw,

the xpfm is in attachment.
Basically I am trying to reproduce the steps described in this tutorial, but directly invoking the v++ commands to better understand the compilation flow.

0 Kudos
florentw
Moderator
Moderator
183 Views
Registered: ‎11-09-2015

HI @HeroGian91 

I know well the A-to-Z tutorial as I have wrote the initial version of it.

Sorry I should have been more detailled. Can you send me the full platform folder (which included the pfm file) generated by Vitis so I can test your platform


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
HeroGian91
Observer
Observer
168 Views
Registered: ‎04-28-2020

I solved the problems, I had not noticed that, unlike v++ --compile, the linker required the full platform folder and not only the xpfm file.
Thanks

View solution in original post