Checkpoints

As stated, Trace32 software must be installed in your machine.

If you haven’t installed Trace32 software, refer to Download and Setup Trace32 software.

1.Run ‘rlm.exe’ (located at rlm installation directory, for example, C:\Reprise\rlm.v12.2BL2-x64_w3.admin\) and see license server. Ensure that it starts without any issues as shown here:

2.Close the application after verification.

Open MxTrans-It and click on the Build verb:

It should invoke command prompt, make a build, and generate the executable (.elf).

Check the executable at <Trace32 folder>/Build location.

Failure to generate executable (.elf) may be because of following reasons:

Commands

See the Commands property on the PIL Transform (as shown below):   First, check the make path. Does make.exe exist at the location specified in the text box? If not, browse to the location where it does. Next, does the makefile have the commands it needs as parameters to have a successful build to generate an executable? In our sample, we are using the compiler and make utility provided by S32 Design Studio, so the above Build settings are wrapped up into a command and executed in windows command prompt as follows: set Path=C:\NXP\S32DS_ARM_v2018.R1\utils\msys32\usr\bin&;make all;GCC_LOC="C:\NXP\S32DS_ARM_v2018.R1\Cross_Tools\gcc-arm-none-eabi-4_9\bin";ARM_EWL2_LOC="C:\NXP\S32DS_ARM_v2018.R1\S32DS\arm_ewl2";MXNET_LOC="C:\Program Files (x86)\MicroMax\MxSuite 3.40.3.43613\Harness\MxNet"; The above can be re-written as: set Path=C:\NXP\S32DS_ARM_v2018.R1\utils\msys32\usr\bin make all GCC_LOC=”C:\NXP\S32DS_ARM_v2018.R1\Cross_Tools\gcc-arm-none-eabi-4_9\bin” ARM_EWL2_LOC=”C:\NXP\S32DS_ARM_v2018.R1\S32DS\arm_ewl2” MXNET_LOC="C:\Program Files (x86)\MicroMax\MxSuite 3.40.3.43613\Harness\MxNet"; What is the purpose of each statement? set Path=C:\NXP\S32DS_ARM_v2018.R1\utils\msys32\usr\bin Appends the Path environment variable with the make location, so that next commands work; that means make.exe can work from any working directory. make all Calls make.exe and specifies where to start in the makefile. ‘all’ in our example (as shown below): GCC_LOC=C:\NXP\S32DS_ARM_v2018.R1\Cross_Tools\gcc-arm-none-eabi-4_9\bin Passes the compiler location to the makefile as shown below: ARM_EWL2_LOC=C:\NXP\S32DS_ARM_v2018.R1\S32DS\arm_ewl2 Like the GCC_LOC, this passes "include" file locations to the compiler so that they are used during the compilation as shown below: MXNET_LOC="C:\Program Files (x86)\MicroMax\Mx-Suite 3.40.3.43613\Harness\MxNet" Source code running on the target directly can’t communicate with the Transform. The Transform should be able to access its port information during run time. To achieve this, MxSuite uses a protocol/agent: MxNet written in ‘c’ language running inside the Transform as a client and in the target as a server by establishing a UDP client-server communication:   Build the target with MxNet code (the Server) available at the MxSuite installer location (for example, C:\Program Files (x86)\MicroMax\MxSuite 3.40.3.43613\Harness\MxNet). Pass this location to the makefile as a command line argument, which is used at build to generate the executable. For example, here its location is passed in the MXNET_LOC variable: MXNET_LOC="C:\Program Files (x86)\MicroMax\MxSuite 3.40.3.43613\Harness\MxNet" The above variable is used in the makefile’ as shown below:

1.Run rlm.exe (located in the rlm installation directory, for example: C:\Reprise\rlm.v12.2BL2-x64_w3.admin\). Do not close the window. You should see something similar to this:

2.Next, Launch the T32Start application by clicking on the Configuration.ts2 file. Then, select Configuration and click on Start as shown below:

3.You should be able to see ‘TRACE32 PowerView for ARM’ is up and running as shown below:

Click to expand.

4.Close TRACE32 PowerView, T32Start, and rlm.exe.

Use for this check point only if you have hardware and the power debug interface device.

1.Run rlm.exe (located in the rlm installation directory, for example, C:\Reprise\rlm.v12.2BL2-x64_w3.admin\). Do not close the window. You should see something similar to the image below:

2.Be sure the Power Debug interface is connected to the PC via USB.

3.Be sure the LEDs on Power Debug Interface are as follows:

•POWER – RED LED is ON

•SELECT – RED LED is Blinking

•RUNNING – LED is OFF

4.Launch the T32Start application by clicking on the Configuration.ts2 file. Then, select Configuration2 and click on Start as shown below.

You should see ‘TRACE32 PowerView for ARM 0 [Power Debug USB 3 @]’ is up and running with a notification ‘FLASH programming completed successfully’ as shown below:

Click to expand.

5.This time you should be able to see ‘TRACE32 PowerView for ARM 0 [Power Debug USB 3 @]’ is Up and ‘running’ with a notification ‘FLASH programming completed successfully’ as shown below:

6.Make sure the LEDs on Power Debug Interface are as follows:

•POWER – RED LED is ON

•SELECT – RED LED is ON

•RUNNING – RED LED is ON

7.Close TRACE32 PowerView, T32Start, and rlm.exe.

When you open the MxSuite project, it should make a build and run the TRACE32 application for you as shown in the image below:

Click to expand.

If not, the highlighted properties may be missing or incorrect. Verify the Transform path properties. (This image is for the PiLCruiseControl Sample, other projects may show different Transforms.)

Click to expand.