This section describes how to enable this debugging facility, operation of its various functions, and points for caution on using the FAA debugging facility when the selected microcontroller incorporates an FAA.
Some descriptions include reference to the state of the FAA in the following ways, which are similar to the state indicators in the Main window.
[FAA] category on the [Connect Settings] tabbed page of the [Property] panel |
Making the above setting enables selecting the FAA as the target for debugging on the status bar or in the [Debug Manager] panel of the Main window.
[Download] category on the [Download File Settings] tabbed page of the [Property] panel |
Making the above settings enables selecting the FAA as the target for debugging and allows debugging operations such as stepped execution at the FAA source level with the FAA source code displayed in the [Editor] panel and address information displayed in the address column.
When the FAA is selected as the target for debugging, each facility behaves as described below.
When the execution of a program is started or stopped, only execution by the FAA is started or stopped. |
However, when [Yes] is selected for the [Stop FAA when stopping] property in the [Break] category on the [Debug Tool Settings] tabbed page, you can specify whether the FAA is or not to be stopped when the CPU is stopped. |
If a clock signal is not being supplied to the FAA or its operation is prohibited by the FAA setting of the operation enable bit (SYSC.ENB), starting execution of the program is not possible. Other forms of debugging operation such as step execution also become impossible. |
You can specify the spaces for display in the [Memory 1] to [Memory 4] panels by making the following settings. |
[Memory] category on the [Debug Tool Settings] tabbed page of the [Property] panel |
The [Watch n] panels are displayed in accordance with the [FAA memory space] property.
A label is displayed in accordance with the memory space (instruction code space or data space) to which the label belongs.
Only those SFRs which are accessible by the FAA are displayed.
The FAA pointer and the FAA address are displayed in the address field.
A list of CPU registers is displayed in the [CPU Register] panel according to the CPU selected as the target for debugging.
The time from the start to the end of execution by the FAA as the target for debugging is displayed in the [Event] panel or the status bar. |
Measuring the time executed by the FAA starts when the execution is started by the CPU or the debugger. |
If FAA debugging is not in use, the FAA is handled in a similar way to other peripheral IP modules. In this case, FAA debugging is not available. |
Programs for the FAA cannot be downloaded by using a debugger. Transfer those programs in the instruction code area by the program of the CPU. |
Do not proceed with debugging of the FAA during execution of a CPU program that includes operations with the WIND register. |
When the tracing and timer functions of the CPU are enabled, the target for debugging cannot be changed during the execution of a program in the simulator. |
Since the CPU and FAA are not run in synchronization by the simulator, the Run-Break times for the CPU that include the ranges where the CPU starts execution of the FAA are not correct. |