MON390: COMMUNICATING WITH TARGET AFTER GO COMMAND

Information in this article applies to:

• C51 All Versions

QUESTION

Does the µVision Debugger expect to be able to communicate with a target system running MON390 after the GO command is issued (while the program is running) if the Stop Execution with Serial Break option is disabled?

ANSWER

Normally, the µVision Debugger does not communicate with the target after the GO command unless you issue a Stop command or click on the stop button. In that case, the debugger sends data to the target system and expects to receive a response (no matter what state the Options - Debug - Monitor Settings - Stop Execution with Serial Break check box is in).

The monitor is able to stop program execution provided that the serial interrupt on the target is configured and is enabled.

• If the serial break/serial interrupt on the target system is enabled, this halts program execution and returns control to the debugger.
• If the serial break/serial interrupt on the target system is disabled, this does not halt program execution and µVision hangs.

If you don't enable serial break, you can still halt a running program by hitting reset on the target system. This initiates communication with the debugger and prevents the debugger from hanging.

Of course, if serial break is enabled, the Stop command in µVision halts the program.

SEE ALSO

• MON51: SHARING SERIAL PORT WITH USER APPLICATION
• MON51: ERROR 26 (CANNOT WRITE INTERRUPT VECTOR)
• MON51: CONNECTION TO TARGET SYSTEM LOST

Last Reviewed: Thursday, September 16, 2004