Setting The Resource Conflict Detection Mode; Setting The Reserved Memory Access Detection Mode - Texas Instruments TMS320C6000 Technical Reference Manual

Setting the Resource Conflict Detection Mode

4.1

Setting the Resource Conflict Detection Mode

CPU Resource Conflict Detection is a feature that allows you to find any resource problem with the use of
CPU registers and functional units. If you are confident that there is no resource conflict problem in the
code, this feature can be turned off to further enhance simulation speed.
This feature can be configured through Code Composer Studio Setup by setting one of the following
options from the Detect CPU Resource Conflicts entry in the processor properties window:
• Yes. The simulator detects all resource conflicts and flags them as errors to you. Whenever an error
occurs, the simulation is halted and control returns to you. You can then choose to correct the error,
reset the program and run again; or to proceed. If you proceed, a precautionary error message is
displayed, click on the Run option to resume simulation.
Note: YES is the default mode. If nothing is specified in the base configuration file (see
Section
• No. The simulator does not detect any resource conflicts.
• Create Log. The simulator detects all resource conflicts but does not flag them as errors to you.
Instead, they are written to a file. To specify the file location, use the Log File entry.
• Log File : Fully qualified filename. If no filename is specified, the errors generated in File mode are
logged in a file named resource_errors.log, located in the CCStudio\drivers directory.
Whenever the Code Composer Studio IDE is re-invoked, the error log file is overwritten. However, if
multiple errors occur during one or more runs in one invocation of CCStudio, all errors are written to
the file.
4.2

Setting the Reserved Memory Access Detection Mode

By default, the detection of reserved memory access is enabled on all simulators. This feature can be
configured through Code Composer Studio Setup by setting one of the following options from the Detect
Reserved Memory Access entry in the processor properties window:
• Yes. The simulator halts whenever the program accesses a reserved memory location. It displays an
error indicating the nature and address of the access. This is the default choice.
• No. The simulator does not report any reserved memory accesses. In this mode, writes to the reserved
memories have no effect, while reads return 0.
Note: Any debug accesses to reserved memory locations (through Memory Windows) will not
cause errors. Debug writes will have no effect and debug reads will always return 0.
• Create Log. The simulator routes all error messages to a file without halting simulation. To specify the
file to save the errors into, use the Log File entry.
• Log File: Fully qualified filename. If no filename is specified, the errors generated in File mode are
logged in a file named res_mem_access_errors.log, located in the CCStudio\drivers directory.
Whenever the Code Composer Studio IDE is re-invoked, the error log file is overwritten. However, if
multiple errors occur during one or more runs in one invocation of CCStudio, all errors are written to
the file.
36 Configuring the Simulator
4.11), simulators come up in this mode of execution.
www.ti.com
SPRU600I – April 2007
Submit Documentation Feedback