Fujitsu F2MC-8FX Series User Manual page 59

2.2.4.1 If the monitor debugger cannot be controlled
It may become unable to control the monitor debugger (I.e., communications between the host
system and the target fails.), due to, such as the application program unexpected behavior. In such
cases, restart the debugger using the following procedure.
① Select "Debug (D)", － "Abort".(Alternatively, click the Run Stop button.)
② Click the "Abort(A)" button in the abort dialog. Note: MCU cannot be reset at this time.
This dialog may be displayed several times, but ignore it.
③ If the warning "Cannot abort" is displayed, click "OK"
④ Close the debugger and reset the target system.
⑤ Restart the debugger.
2.2.4.2 Debugger prohibitions
① Do not operate resources that use the monitor debugger (IO ports P10, P11, P12).
② Do not operate the PLLC and SYCC registers by using the debugger.
③ Do not set break points in the monitor program.
④ Do not single step thorough within API FGM_WDTON process.
2.2.4.3 Debugger limits
① The initial values for the SP register changes.
② The startup time changes after the reset cancellation.
③ Forced breaks are disabled when UART/SIO interrupts are prohibited.
④ The response time of clock 2 system products (with sub-clock inputs) is lengthened.
⑤ Code breaks are disabled during step-in operations.
⑥ Add four bytes to the stack area for the monitor program.
⑦ Make sure to combine use with the "flash security function" also.
⑧ Use the flash programmer when changing the password.
⑨ A reset occurs after an object has been loaded.
59
AN07-00200-03E