|
|||||||||||||
Technical Support On-Line Manuals µVision User's Guide ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Creating FunctionsCreate, modify, and compile debug functions using the built-in debug function editor. When in debug mode, open the editor with the menu Debug — Function Editor. You are asked to enter a file name or the editor opens the initialization file specified in the field Options for Target — Debug — Initialization File. The content of this file is processed each time a debugging session is started.
Where
Use the command INCLUDE during a debugging session to read and process the file. Debug functions defined in this file are available right away in the debugging process. Debug commands are executed while the file is parsed. For example: >INCLUDE MYFUNCS.INI Note
See also:
| ||||||||||||
|
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.