FAQs

Normally, the MxNet folder is located in the MxSuite installation folder.

For example, the following  MxNet files should be included from C:\Program Files (x86)\MicroMax\MxSuite 3.40.3.43830\Harness\MxNet:

dprintf.c

dprintf.h

MxClock.c

MxNet.c

MxNet.h

MxNetEnums.h

MxPacket.h

MxQueue.c

MxQueue.h

MxTypes.h

And the following MxNet files should be included from C:\Program Files (x86)\MicroMax\MxSuite 3.40.3.43830\Harness\MxNet\Trace32\Target:

MxNet_Target.c

MxNet_Target_Config.h

MxVHarness.c

MxVHarness.h

MxVPlatform.h

MxVTypes.h

TransportLayer.c

TransportLayer.h

No, you can create a folder outside and reference that folder to the Trace32 Folder property on the Transform.

No, it can be any name, but make sure it has a Build folder in it.

Yes, the PiL Transform looks inside the Trace32 folder for Trace32 Files and makefile to build.

No, it can be any format but please make sure the file format is supported by TRACE32 and has a PRACTICE script (.cmm) ready with this change.

Yes, of course, but make sure TRACE32 supports your processor family.

Yes, it can be any compiler.

You can use only Lauterbach supported debugger interface devices. For example:

‘Podbus Device Chain’ as shown below:

(Or)

Run in any configuration, as shown below:

The Trace32 installer provides demo samples for most of the hardware.

For example, PiL Sample runs on S32K144 MCU Hardware and demo script can be found at T32 installer location as shown in the image below:

Select the sample demo script file and modify necessary changes, such as .elf file name, watch variables, print statements and so on.

For example, s32k144_sieve_flash.cmm.

Copy the script file to the Build folder. if application runs on debugger (for example, power debug interface) then change the name of the script to ‘DEBUGGER.cmm’ and if the application runs as virtual target (TRACE32 Simulator) then change the name of the script to ‘SIMULATOR.cmm’

No, if you have server-based license, you don’t need RLM. Leave the RLM Installer property on the Transform empty.

The interface between the PIL Transform and MxVDev is defined by the AppIF.c file. If you are using a Simulink model, the file is generated. If you are using the Lauterbach debugger alone, you must create the file. For information about the Port Registration functions used in the AppIF.c file, see Port Registration. This is an example of an AppIF.c file and its included files:

AppIF.c

AppIF.h