How Can the eTPU Code Size be Increased? (Freescale ASH WARE)

Note; the underlying eTPU address space supports 32K, but Freescale populates the various microcontrollers with the size of memory that they feel is required for each specific intended application. The default on the eTPU Simulator was recently increase from 12K to 16K to reflect the MPC5554's latest size.

The Build Batch Script File.

Various build parameters are specified in the build script. This file is run when the simulator or debugger is initially launched and this file "tells" the simulator how big memory is along with varius other parameters.

To tell which build script is loaded, look under "files" in the "configuration" window. To view the configuration window, in the "view" menu, select "configuration".

To load a "different" build batch file, in the "files" menu, select, "MtDt build script, run."

Modifying the Build Batch Script File

Although the user can modify any build batch script file simply by editing it, one should NOT DO SO. Why? Because every time a new version of the simulator is installed, all installed build batch script files are overwritten. So, to avoid a situation in which a modified version of the build batch file is overwritten ASH WARE has established a file naming conventions. All ASH WARE generated build batch file names begin with the letters, "ZZZ". If you want to use your own file, simply remove the "ZZZ" from the name.

Modifying the memory size

The memory size is specified within the build batch file with the add_mem_block(...); script command such as the following.

// Generate a 12K Code Block
add_mem_block("eTpu1", 0, 0x2fff, "Code", ETPU_CODE_SPACE);

To change this to 16K, modify the third term to 0x3FFF (instead of 0x2FFF)

// Generate a 16K Code Block
add_mem_block("eTpu1", 0, 0x3fff, "Code", ETPU_CODE_SPACE);