You cannot open Vitis IDE workspaces directly in the Vitis Unified IDE.
The classic IDE provides an utility to enable moving a project or workspace into the Vitis Unified IDE. To use this utility, follow the steps below.
- Launch the Vitis classic IDE in the workspace with
the following command:
vitis --classic -workspace <workspace> - Use the command from the main menu.
- Specify the new workspace location and click Finish. The tool generates a Python migration script (migrate.py) and writes it to the specified workspace
folder. The Workspace
location for the export script must be a new empty
workspace. If you want to make changes to the classic IDE project and re-export it,
you must start with a clean export workspace. The workspace must not contain any
hidden files.Note: You can also recreate the workspace in the Vitis Unified IDE from scratch for migration. The migration utility does not consider all the corner cases and can encounter issues for complex designs.Figure 1. Export to Vitis Unified IDE
- After generating the migration script, a pop-up window displays the location of the
script. Run the script in the Vitis Unified IDE by
using the
vitis -s <script>form of the command as described in Launch Options in the Vitis Reference Guide (UG1702).vitis -s migrate.py
| Project Type | Limitation | Workaround |
|---|---|---|
| Embedded Platforms | There is no migration from local changes to BSP sources to the new workspace. You need to create a new BSP. The settings apply to the new BSP. | Copy the sources to the new BSP manually. |
| No migration of any embedded software repositories that you add to the Vitis IDE. If the project has any local SW repos, the system shows a warning. |
All software repositories need to be migrated to looper first. Refer to Vitis Unified Software Platform Documentation: Embedded Software Development (UG1400) for more information. The path to the migrated repository can be manually added to the migration script prior to running the script. |
|
| IP drivers included in XSAs created with 2023.1 or older releases is not compatible. | Need to regenerate the XSA. | |
| Embedded Software Applications | Applications referring to platforms that are outside the current workspace cannot be migrated. | Migrate the platform first and update the application to use the new platform before migrating the application. |
| HW Link | Hardware linker options defined using the Extra V++ command line options cannot be migrated through the script. | You need to manually define these options in the hw_link.cfg for the system project. |
| Accelerated Host applications | You can only migrate compile definitions (-D), include path (-I), library paths (-L) and libraries (-l) for accelerated host applications. | You need to set other compiler or linker settings from the C/C++ build settings window manually in the application component. |