Create a new platform.
Syntax
platform create [options]
Create a new platform by importing hardware definition file. Platform can also be created from pre-defined hardware platforms. Supported pre-defined platforms are zc702, zcu102, zc706 and zed.
Options
Option | Description |
---|---|
-name <software-platform name>
|
Name of the software platform to be generated. |
-desc <description>
|
Brief description about the software platform. |
-hw <handoff-file>
|
Hardware description file to be used to create the platform. |
-out <output-directory>
|
The directory where the software platform needs to be created. If the workspace is set, this option should not be used. Use of this option will prevent the usage of platform in Vitis IDE. |
-prebuilt
|
Mark the platform to be built from already built software artifacts. This option should be used only if you have existing software platform artifacts. |
-proc <processor>
|
The processor to be used; the tool will create the default domain. |
-arch <processor architecture>
|
32-bit or 64-bit, this is valid only for the A53 processor. |
-samples <samples-directory>
|
Make the samples in <samples-directory> , part of the platform. |
-os <os>
|
The OS to be used. The tool will create the default domain. This works in combination with -proc option. |
-xpfm <platform-path>
|
Existing platform from which the projects have to be imported and made part of the current platform. |
-no-boot-bsp
|
Mark the platform to build without generating boot components. |
-arch <arch-type>
|
Processor architecture, <arch-type> can be 32 or 64 bits. This option is used to build the project with 32/64 bit toolchain. |
-rp <slot-info>
|
Reconfigurable partition slot information for dfx flows.This option takes tcl dictionary with key-value pairs. Multiple slots can be passed as an array. |
Returns
Empty string, if the platform is created successfully. Error string, if the platform cannot be created.
Examples
platform create -name "zcu102_test" -hw zcu102
Defines a software platform for a pre-defined hardware desciption file.
platform create -name "zcu102_test" -hw zcu102 -proc psu_cortexa53_0 -os standalone
Defines a software platform for a pre-defined hardware desciption file. Create a default domain with standalone os running on psu_cortexa53_0.
platform create -name "zcu102_32bit" -hw zcu102 -proc psu_cortexa53_0 -arch 32-bit
-os standalone Defines a software platform for a pre-defined hardware desciption file. Create a default domain with standalone os running on psu_cortexa53_0 in 32-bit mode.
platform create -name "zcu102_test" -hw zcu102 -proc psu_cortexa53 -os linux
-arch 32-bit Defines a software platform for a pre-defined hardware desciption file. Create a default domain with linux os running on psu_cortexa53 in 32-bit.
platform create -xpfm /path/zc702.xpfm
This will create a platform project for the platform pointed by the xpfm file.
platform create -name "ZC702Test" -hw /path/zc702.xsa
Defines a software platform for a hardware desciption file.
platform create -name "testplat" -hw static.xsa -rp { id 1 hw ./hw.xsa
hw_emu ./hw_emu.xsa } This will create a platform project with single slot DFX. User must specify path to hw XSA and hw_emu XSA.
platform create -name :testplat: -hw static.xsa -rp { { id 1 hw ./rp_1.xsa
hw_emu ./hw_emu.xsa } { id 2 hw ./rp_2.xsa hw_emu ./hw_emu.xsa } } This will create a platform project with multi-slot DFX. The first slot is a default ReconfigurableParition. For multi-slot platforms, there will be multiple hw XSAs with a slot_id for each slot and potentially multiple hw_emu XSAs or single XSA.