Creating a Project with Your Code

To create a project, you need all the software and licenses listed in PIL Software Prerequisites and Licenses.

Before  harnessing code for PIL testing, be sure it compiles and runs successfully in its original environment (SIL or MIL). Do not begin the following procedure until any issues are resolved.

Use S32 Design Studio to build your existing code with Eclipse:

1.In S32 Design Studio, open your project  and set the Build Configuration to Debug. (Right-click on the project and select Build Configurations->Set Active->Debug.)

2.Ensure that it builds without errors:

Copy the provided template files into the S32 Design Studio workspace:

1.Create a subdirectory called MxV in the workspace.

2.Copy the code files AppIF.c, AppIF.h, and MxNet_Target_Config.h from <MxVInstallDirectory>\Templates\Trace32 into the MxV subdirectory:

3. Right-click on the project and select Refresh.

Copy key parts of your code into the templates

1.Copy any initialization code from the main() function into the SUT_Init() function of AppIF.c:

2.Define macros to enable/disable hardware dependent code as shown below:

3.Copy the user code from the for loop of the main() function into SUT_Tick() of AppIF.c.

4.Copy any headers required for variable declarations and function prototypes from main.c to AppIF.h:

5.For each memory location needed as input or output from the unit under test, add the appropriate port registration function in the AppIF.h MxVRegisterPortDefinitions() function.  Ensure that the defines that specify the port counts are correct (for example, if there are 25 output port registrations, ensure that the _MXV_NUMBER_OUTPORTS is at least 25). In the figure below, all three port counts are 1.

Create a new MxVDev project. This is the project that controls the PIL Transform. If you have an existing MxV project, you can copy and modify it. Replace your current Transform with the PIL Transform.

Select these options:

•Create new folder. In the examples in this Help, the folder is named MxV.

•Custom

•MxClock

•Start MxTransIt on Finish

Copy the folders from the workspace into the MxV project folder so it can be used by the PIL Transform.

1.Copy the Eclipse project to the MxV project folder created in the previous step:

2.Copy the Debugger.ts2, Debugger.cmm, Simulator.ts2, and Simulator.cmm files from <MxVInstallDirectory>\Templates\Trace32\ARM to the ARMDemo subfolder in the MxV project folder. These templates are used to run the ARM-based S32K144 target:

Note: If the target is different than samples provided, get the script (.cmm) files from the Trace32 installer location and create a configuration (.ts2) file for your target. See FAQ for more details.

3.Modify the script (.cmm) file as appropriate for the Simulation mode. The parameter in the example below is added to Simulator.cmm, which runs S32K144 target. Add appropriate CPU configuration as necessary.  Note that the file takes a single parameter passed from MxVDev that is the file name of the elf that is built.

Use the Toolbox to create a PIL Transform.

The following properties are available to configure the PIL Transform for compiling source code and for use with the Trace32 system.

Trace32 Properties

Use the Transform's Properties box to set the following properties: •API Port: The port that will be used to communicate with Trace32.  The default is 20000. Changing the API Port To change the API port, double click on the Simulator.ts2 file to open the T32Start dialog: •Rlm Installer Folder: The location of the license manager rlm executable.  Leave blank if using a network license manager. Note: If you see this warning, you can ignore it: 0,Transform,MxV/PiL,RlmInstallerFolder path 'C:\Reprise\rlm.v12.2BL2-x64_w3.admin' does not exist   •Simulation Mode: Whether to use the Simulator or Debugger (hardware required) configuration files. •Target File: The full path to the compilation result (the .elf file). This is the file that will be loaded during Trace32 debugging. This folder is generated when the PIL Transform is built. For details, see Target File. •Trace32 Configuration Folder: The folder to which the Simulator/Debugger files were copied. •Trace32 Installation Folder: The folder in which the Trace32 debugger was installed.  Typically, C:\T32\bin\windows64 for a 64-bit Windows setup.

Build Properties

Build Tool Configuration: Click to bring up the Build Configuration dialog.   •Build Mode: Select either Eclipse (using a headless build) or Command Line (such as make): Eclipse Build This configuration is for directly building an eclipse project located on disk.  Set the following properties: •Build Configuration: The configuration name that was created in the GUI that was created to support specifically an MxVDev build.  This typically will be MxVBuild if the steps were taken above to create the configuration. •Eclipse Project Name: This is the name of the project as it appears in the Eclipse IDE. •Project Source Path: The path to the project files on disk. •Additional PATHs: Additional directories to place in the PATH while executing the command line.   Note that these will be searched in order to find the tool that is used. •MxNet include file location: This is an optional property.  If this is left blank, the current MxVDev project folder is used as the base to find the Harness/MxNet include files. When a directory is entered, the Transform sets a Windows environment variable. This directory is used to find the MxNet include files required to build.   Generic Command Line Build This configuration is used when using a command line to build. Usually, this is make, but it can be any build system that allows the target to be built. Compiler-specific Arguments If you are using Greenhills or any other compiler that enforces MISRA standards by default, add the following command-line argument to your makefile: -DMXNET_NO_STDARG=1 Sample Makefile with Additional Argument For example: Assume you have created a makefile and it is available in the ARMDemoMakefile subdirectory. Configure the command line build by setting up the following properties. •Additional PATHs: Additional directories to place in the PATH while executing the command line.   Note that these will be searched in order to find the tool that is used. •MxNet include file location: This is an optional property.  If this is left blank, the current MxVDev project folder is used as the base to find the Harness/MxNet include files. When a directory is entered, the Transform sets a Windows environment variable. This directory is used to find the MxNet include files required to build.

Use the PIL Transform to build the harnessed project:

1.Click the Build verb in the Transform's Properties box. Be sure it builds and generates the executable (.elf).

2. Set the Target File property to the full path of the generated executable (.elf):

1.Click the Enumerate verb to connect with Trace32 and enumerate the ports on the Transform:

2.Export the ports to MxVDev signal dictionary.

3.Save the Harness.

1.In MxVDev, click the Connect Harness button to connect MxV with the Transform and Trace32.

2.Use the Connections dialog to import the Signals into the MxVDev Signal Dictionary.

3.Create Scenarios and TestCases with the imported Signals:

a.Use the Pick Signals dialog to add Signals to your TestCases:

b.Create the transitions in the Test Case.

c.Save the TestCase.

4.Run the TestCase and see the result:

5.Click Accept Results and run again for a passing test.