beautypg.com

3 start-up messages, 4 hardware check at start-up – Epson S5U1C62000A User Manual

Page 134

background image

122

EPSON

S5U1C62000A MANUAL

(S1C60/62 FAMILY ASSEMBLER PACKAGE)

CHAPTER 9: DEBUGGER

9.3.3 Start-up Messages

When Debugger db62 starts up, it outputs the following message in the [Command] window. (Refer to
the next section for details about windows.)

Debugger for E0C62 Ver x.x Copyright (C) SEIKO EPSON CORP. 199x

Connecting COMx with xxxxx baud rate...done

Parameter file: XXXXX.par

Chip name: E0C62XX

Map....................................done

Initialize.............................done

>

9.3.4 Hardware Check at Start-up

If the debugger is invoked, it first performs the tests and initializing operations as follows:

(1) The debugger first checks to see that the ICE is connected to the system and that communication is

possible without any problems. The following message is displayed in the [Command] window.

During test

Connecting COMx with xxxxx baud rate...

When terminated normally

Connecting COMx with xxxxx baud rate...done

When an error is encountered

Connecting COMx with xxxxx baud rate...Error

The Error indicates that communication between the personal computer and ICE is not functioning
properly. In this case, verify the following:

• A standard RS-232C cable is used
• The COM port is correct
• The baud rates on both sides are matched
• The ICE's power is turned on
• The ICE remains reset

(2) When the connection test terminates normally, the debugger checks the contents of the parameter file

and initializes the ICE.

When terminated normally

Parameter file: XXXXX.par

Chip name: E0C62XX

Map....................................done

Initialize.............................done

>

When an error is encountered

Parameter file: XXXXX.par

Chip name: E0C62XX

Map....................................Error

Initialize.............................Error

>

If an error occurs in the above initialization process, temporarily quit the debugger. Check the cause
of the error and repair it before restarting the debugger.