HOWTO: Migrate Application Projects from S32DS for Vision 2018.R1 to S32DS 3.x

[#1]

You can use a project that was created in an earlier version of S32 Design Studio, but it requires changes to the build
configuration settings and the project structure.

Migrating ISP Application Project

The following explains how to configure your ISP application project.

1. Click File > Import... > General > Existing Projects into Workspace, then click Next.
2. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish.
3. Remove all VSDK specific settings from the build configuration settings:
   1. Right-click the project in the Project Explorer view and click Properties on the context menu.
   2. Open C/C++ Build > Settings and remove the following settings for the A53 build configuration:
      • Standard S32DS C Compiler/Standard S32DS C++ Compiler > Preprocessor: Remove VSDK_UMAT_USE_OPENCV from the Defined symbols list.
      • Standard S32DS C Compiler/Standard S32DS C++ Compiler > Includes: Remove all the ${S32DS_VSDK_DIR} paths from the Include paths list.
      • Standard S32DS C++ Linker > Libraries: Remove all libraries from the Libraries and Library search paths lists.
4. Click SDKs on the left pane of the project properties, then attach VSDK_MODULE_WIN to the A53 build configuration.
5. Remove typedefs.h from the A53_inc folder.

Migrating APEX2 Application Project

The following explains how to configure your APEX2 application project.

1. Click File > Import... > General > Existing Projects into Workspace, then click Next.
2. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish.
3. Remove some build configuration settings:
   1. Right-click the project in the Project Explorer view and click Properties on the context menu.
   2. Open C/C++ Build > Settings and remove the following settings for the A53 and TEST_A53 build configurations:
      • Standard S32DS C Compiler/Standard S32DS C++ Compiler > Preprocessor: Clear the Defined symbols and Undefined symbols lists.
      • Standard S32DS C Compiler/Standard S32DS C++ Compiler > Includes: Remove all the ${S32DS_VSDK_DIR} paths from the Include paths list.
      • Standard S32DS C++ Linker > Libraries: Clear the Libraries and Library search path lists.
   3. Remove the following settings for the APU build configuration:
      • APU C Compiler/APU C++ Compiler > Preprocessor: Clear the Defined symbols lists.
      • APU C Compiler/APU C++ Compiler > Includes: Remove all the ${S32DS_VSDK_DIR} paths from the Include paths list and clear the Include files list.
      • APU C++ Linker > General: Remove the script file.
      • APU C++ Linker > Libraries: Clear the Libraries and Library search path lists.
   4. Remove the following settings for the EMU and TEST_EMU build configurations:
      • Cross G++ Compiler > Preprocessor: Clear the Defined symbols list.
      • Cross G++ Compiler > Includes: Remove all paths except the ${ProjDirPath} ones from the Include paths list.
      • Cross G++ Linker > Libraries: Clear the Libraries and Library search path lists.
4. Replace the Project_Settings/Scripts/gen_apu_load.tcl file with a copy from any APEX2 project created in new S32 Design Studio.
5. Remove typedefs.h from the A53_inc folder and S32V_APU.lcf from Project_Settings/ Linker_Files .
6. Right-click the project in the Project Explorer view and click SDKs on the context menu. Attach VSDK_MODULE_WIN to all build configurations.
7. Emit the source code from the updated Visual Graph Tools projects.
8. If you want to debug your application using APEX2 Emulator, update the debug configuration settings:
   1. Right-click the project in the Project Explorer view and click Debug As > Debug Configurations... on the context menu.
   2. In the left pane, open the configuration under C/C++ Application.
   3. In the right pane, go to the Environment tab. Edit the PATH value:
      ${S32DS_GCC_TOOLCHAIN_DIR};${S32DS_OPENCV_DIR}/x86/mingw/bin 
      Then select the Replace native environment with specified environment check box.
   4. Go to the Debugger tab and update the GDB debugger location:
      ${S32DS_GCC_TOOLCHAIN_DIR}/gdb.exe

Migrating APEX2 Graph Project

The following explains how to update your APEX2 graph diagram.

1. Click File > Import... > General > Existing Projects into Workspace, then click Next.
2. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish.
3. Open the graph diagram.
4. In the Palette pane, drag Add Kernels and drop it to the canvas.
5. Select the kernel used in your old project. You can start typing the kernel name in the search box or use the filtering button to specify the kernel location. Click OK.
6. Remove your old kernel and connect the Input and Output elements with the respective ports of the newly added kernel.
7. Repeat the 5-7 steps for each kernel on the diagram.
8. Right-click the canvas and click Validate diagram on the context menu. If a validation problem was found, the Problems view displays an error or warning. The element that caused the error is marked on the diagram with a red cross icon, so you can easily find and fix it.

Migrating APEX2 Program Project

The following explains how to update your APEX2 program diagram.

1. Click File > Import... > General > Existing Projects into Workspace, then click Next.
2. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish.
3. Open the program diagram.
4. In the Palette pane, drag Process from Graph and drop it to the canvas.
5. Select the updated graph. Click OK.
6. Remove your old process and connect the Inlet and Outlet elements with the respective ports of the newly added process.
7. Repeat the 5-7 steps for each process on the diagram.
8. Right-click the canvas and click Validate diagram on the context menu. If a validation problem was found, the Problems view displays an error or warning. The element that caused the error is marked on the diagram with a red cross icon, so you can easily find and fix it.