Filter
Top Products
Appendix D Notes on High-performance Embedded
Workshop
1. Note on Moving Source File Position after Creating Load Module
When the source file is moved after creating the load module, the [Open] dialog box may be
displayed to specify the source file during the debugging of the created load module. Select the
corresponding source file and click the [Open] button.
2. Source-Level Execution
⎯ Source file
Do not display source files that do not correspond to the load module in the program
window. For a file having the same name as the source file that corresponds to the load
module, only its addresses are displayed in the program window. The file cannot be
operated in the program window.
⎯ Step
Even standard C libraries are executed. To return to a higher-level function, enter Step Out.
In a for statement or a while statement, executing a single step does not move execution to
the next line. To move to the next line, execute two steps.
3. Operation During Accessing Files
Do not perform other operations during downloading the load module or saving in the [Verify
Memory], [Save Memory], or [Trace] window because this will not allow correct file
accessing to be performed.
4. Watch
⎯ Local variables at optimization
Depending on the generated object code, local variables in a C source file that is compiled
with the optimization option enabled will not be displayed correctly. Check the generated
object code by displaying the [Disassembly] window.
If the allocation area of the specified local variable does not exist, displays as follows.
Example: The variable name is asc.
asc = ? - target error 2010 (xxxx)
⎯ Variable name specification
When a name other than a variable name, such as a symbol name or function name, is
specified, no data is displayed.
Example: The function name is main.
main =
A variable that is allocated to register cannot be selected for monitoring.
137