Create and Configure an MxV Project

hmtoggle_plus1Create an MxVDev Project

Create a new MxVDev project. Select these options:

•Create new folder. In this demonstration, the folder is named MxV.

•Custom

•MxClock

•Start MxTransIt on Finish
hmtoggle_plus1Copy the Eclipse Files into the MxVDev Project

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

pm01

pm02

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:

pm04

pm05

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.

pm06

 
hmtoggle_plus1 PIL Transform Configuration

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.

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.

To change the API port, double click on the Simulator.ts2 file to open the T32Start dialog:

T32Start-marked

•Rlm Installer Folder: The location of the license manager rlm executable.  Leave blank if using a network license manager.

Note: At Danlaw, the RLM server is esp-wilic001

•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.

pm07

Build Tool Configuration: Click 3dots_button to bring up the Build Configuration dialog.  

•Build Mode: Select either Eclipse (using a headless build) or Command Line (such as make):

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.

pm08

 

pm09

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.

For example: Assume you have created a makefile and it is available in the ARMDemoMakefile subdirectory.

pm10

Configure the command line build by setting up the following properties.

pm11

•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.

 

 
hmtoggle_plus1Invoke a Build from the PIL Transform

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

pm12

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

pm13
hmtoggle_plus1 Enumerate and Export the Ports

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

pm14

2.Export the ports to MxVDev signal dictionary.

3.Save the Harness.
hmtoggle_plus1Create and Run a Test Case

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.

pm15

3.Create a TestCase with the imported Signals:

a.Use the Pick Signals dialog to add Signals to the TestCase:

pm16

b.Create the transitions in the Test Case.

pm17

c.Save the TestCase.

4.Run the TestCase and see the result:

pm18

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