Abov E-OCD II User manual

Global Top Smart MCU Innovator, ABOV Semiconductor
www.abovsemi.com
E-OCD II Debugger
User’s Manual
Version 1.0.2

Contents E-OCD II User’s Manual
2
Contents
1Introduction ....................................................................................................................................4
1.1 E-OCD II The Chip and Onboard Debugging Solution .......................................................4
1.1.1 Software Requirements ..........................................................................................4
1.1.2 Hardware Requirements.........................................................................................4
1.2 Software Installation ............................................................................................................5
1.3 Hardware Driver Detection................................................................................................11
1.3.1 Human Interface Devices .....................................................................................11
2E-OCD II Interface Hardware .......................................................................................................14
2.1 E-OCD II Interface.............................................................................................................14
2.1.1 Features of E-OCD II H/W....................................................................................14
2.1.2 E-OCD H/W Connection.......................................................................................15
2.1.3 Hardware Connection/Disconnection Procedures ...............................................16
2.1.4 E-OCD II Interface Connection.............................................................................16
2.1.5 E-OCD II Interface Disconnection ........................................................................17
2.1.6 E-OCD II Power Out to Target System .................................................................17
3Debugger Software (for Microsoft Windows) ...............................................................................18
3.1 Debugger Software Features ............................................................................................18
3.1.1 Common Features ................................................................................................19
3.2 Menu Descriptions.............................................................................................................21
3.2.1 File ........................................................................................................................22
3.2.2 View ......................................................................................................................23
3.2.3 Emulation..............................................................................................................28
3.2.4 Break/Configure....................................................................................................33
3.2.5 Power Out (3.3V or 5.0V) .....................................................................................42
3.2.6 Test .......................................................................................................................44
3.2.7 Window .................................................................................................................46
3.2.8 Help ......................................................................................................................47
3.2.9 Toolbar ..................................................................................................................47
3.3 Child Windows...................................................................................................................48
3.3.1 Child Window Alignment.......................................................................................48
3.3.2 Code Dump View..................................................................................................51
3.3.3 Code Disassemble View.......................................................................................54
3.3.4 XDATA Dump View ...............................................................................................56
3.3.5 IDATA (IRAM) Dump View ....................................................................................59
3.3.6 SFR Dump View ...................................................................................................61
3.3.7 Registers View......................................................................................................62
3.3.8 Source View..........................................................................................................65
3.3.9 Global Variable View.............................................................................................68
3.3.10 Local Variable View ..............................................................................................74
4Keil Plug‐in ...................................................................................................................................76
4.1 Basic Features ..................................................................................................................76
4.1.1 Getting Started .....................................................................................................77
4.1.2 User Guide ...........................................................................................................77
4.2 Keil Plug-in Setup..............................................................................................................78
4.2.1 Bind PK51.............................................................................................................78
4.2.2 Add Flash Control to Your Project ........................................................................79
4.2.3 Add Debugger Control to Your Project .................................................................80
5IAR 8051 GUI (Compiler and Debugger) .....................................................................................81

UM_E-OCD II Debugger Manual (201109, 표준 문서 영문화 완료).docx
Contents
3
5.1 Basic Features ..................................................................................................................81
5.2 USB Kernel Driver Installation...........................................................................................81
5.3 ABOV’s SDK DLL Connections.........................................................................................82
5.4 IAR Project Settings ..........................................................................................................83
5.5 Download Hex File ............................................................................................................85
5.6 Cautions for Debugging ....................................................................................................87
5.7 SDK DLL Compatibility According to IAR Versions ...........................................................89
6Appendix: E-OCD II Isolator Interface..........................................................................................90
Revision history .....................................................................................................................................91

Introduction E-OCD II Debugger User’s Manual
4
1Introduction
1.1 E-OCD II The Chip and Onboard Debugging Solution
E-OCD II is short for ‘Enhanced On-Chip Debugger’. E-OCD II is a debugger tool for ABOV 8bit MCU.
E-OCD II is MCU debugging control via 2pin or 3pin (added RunFlag) OCD interface. E-OCD II is
dedicated to onboard programming and debugging via serial interfaces (DSCL, DSDA). E-OCD II
debugger supports all of ABOV’s M8051 devices.
In particular, the E-OCD II adds protection circuitry to the input and output ports for tough board-level
manufacturing lines for added durability and safety. E-OCD II is advanced function for USB driver,
Power out, low level detection more than OCD II. Power out function only supports 50mA current
consumption environment.
1.1.1 Software Requirements
The following operating systems must be used to install and run the E-OCD II debugger. Both 32-bit
and 64-bit versions are available.
Microsoft Windows Vista
Microsoft Windows 7
Microsoft Windows 8 & 8.1
Microsoft Windows 10
If you wish to carry out a full installation of the software, up to 20MB of hard disk space is required.
1.1.2 Hardware Requirements
The following are the minimum hardware requirements for installing and running the E-OCD II
debugger.
USB port
Performance is based on the following factors:
Processor performance
USB port performance
The E-OCD II debugger is not affected by the USB version (V1.0, V1.1, V2.0, or higher).

E-OCD II Debugger User’s Manual Introduction
5
1.2 Software Installation
The installer program can be downloaded from the ABOV website. It is recommended that the latest
version of the E-OCD II software be used because ABOV constantly adds newer devices and features.
Both 32-bit and 64-bit versions are available. To check the operating system details of the PC, open
the Control Panel and click on the System icon. The OS details can be identified as shown below.
1.2.1 Microsoft Windows 10
Figure 1-1 How to distinguish 32-bit & 64-bit operating systems for Windows 10

Introduction E-OCD II Debugger User’s Manual
6
To install the E-OCD II software, perform the following:
1) Execute the installer.
The 32-bit installer file name starts with ‘Setup32_’keyword.
The 64-bit installer file name starts with ‘Setup64_’keyword.
2) [64-bit systems only] Once the warning message below message box, click ‘Yes’.
Figure 1-2 User Account Control Message Box
3) Once the dialog box shown below opens, click ‘Next’.
Figure 1-3 InstallShield Wizard

E-OCD II Debugger User’s Manual Introduction
7
4) Read the license agreement. If agree, select I accept the items of the license agreement on
the license agreement dialog box and click ‘Next’.
Figure 1-4 License Agreement
5) Enter the ‘User Name’and ‘Company Name’and click ‘Next’.
Figure 1-5 Enter the User Name and Company Name

Introduction E-OCD II Debugger User’s Manual
8
6) Select ‘Complete’and click ‘Next’.
Figure 1-6 Select a Setup Type
7) Click ‘Install’.
Figure 1-7 Begin the Installation

E-OCD II Debugger User’s Manual Introduction
9
8) Wait until all the application components are installed.
Figure 1-8 Installing
9) Click Finish to complete the installation.
Figure 1-9 InstallShield Wizard Complete

Introduction E-OCD II Debugger User’s Manual
10
Note the installation folder path. This information is needed when you install the hardware
driver.
32-bit: C:\Program Files\ABOV Semiconductor\OCD II_debugger32
64-bit: C:\Program Files (x86)\ABOV Semiconductor\OCD II_debugger64

E-OCD II Debugger User’s Manual Introduction
11
1.3 Hardware Driver Detection
1.3.1 Human Interface Devices
E-OCD II USB type is HID (Human Interface Devices). Windows of Microsoft support HID USB Driver.
So when E-OCD II debugger is connected to computer, HID USB Driver is installed to the computer
and user can use E-OCD II debugger automatically.
To check E-OCD II connection, follow the procedure:
1) Go to Device Manager to check HID connection.
Figure 1-10 System Information

Introduction E-OCD II Debugger User’s Manual
12
2) Find Human Interface Devices in list.
Figure 1-11 Device Manager : HID
3) Check HID properties to confirm E-OCD II Hardware Vendor ID
Figure 1-12 Device Manager : HID Properties

E-OCD II Debugger User’s Manual Introduction
13
4) Select Hardware Ids in Detail Tap of HID properties.
Figure 1-13 HID-compliant Device Properties
5) E-OCD II Hardware vendor ID is 0x1A29. If VID_1A29 is searched, E-OCD II is connected
properly.
Figure 1-14 HID-compliant Device Properties : Hardware Ids

E-OCD II Interface Hardware E-OCD II Debugger User’s Manual
14
2E-OCD II Interface Hardware
2.1 E-OCD II Interface
The E-OCD II interface supports ABOV 8-bit MCUs that use either the OCD or OCD II interface logic.
So, the user can perform debugging for both OCD and OCD II-compatible MCU series using this
hardware.
2.1.1 Features of E-OCD II H/W
The E-OCD II interface is the most cost-efficient debugging solution for the MCUs developed by
ABOV
Semiconductor Co., Ltd. The E-OCD II interface is a sophisticated debugging tool. It is s more flexible
and faster than the OCD interface with the following features:
Support Devices for ABOV’s 8bit MCUs
Support MC95/96 and A95/96 series devices
E-OCD II supports Debugging and on-board programming
E-OCD II Serial supports ISP via serial interface (DSCL, DSDA)
10-pin external connector for Debugging and programming
USB HID transmission is applied to Hardware of E-OCD II.
Include two interface lines: SCLK and SDATA, and one option line: RTIME (run time
measuring)
Can measure the exact operating time of the target MCU down to the microsecond range -
In this case, RTIME must be connected.
Cover the full range of the target device’s operating frequency
Supply power to the target MCU available.
Power out current consumption limit 50mA
Target system operating voltage : 3V ~ 6V
Low Level transmission 1.0V ~ 5.5V
E-OCD II can debug full range of the target device’s operating frequency.
Enhanced protection circuitry for external I/O ports
512Byte expanded memory is added
Level Shift IC is added at DSCL, DSDA port for Low Level transmission
Support function for Power Out to Target B/D.
ESD Protection is advanced(2000V Human-Body, 200V Machine, 1000V Charged Device)

E-OCD II Debugger User’s Manual E-OCD II Interface Hardware
15
Two LEDs for ‘Power’and ‘Debug Run’
Not support hot plugging
Note : The target system must not be powered during insertion or release of the OCD interface
2.1.2 E-OCD H/W Connection
Figure 2-1 Cable Side View
Table 2-1 Pin Assignment
Pin No.
Name
Function
1
Not Used
-
2
VCC Detect
Detects the target system’s power and interface voltage level.
3
Not Used
-
4
GND
System grounding
5
RunFlag
Connect RunFlag pin of 94/97series Device.
6
SCLK
Serial clock of the OCD interface.
7
Not Used
-
8
SDATA
Serial data of the OCD interface.
If the target system’s output is very noisy, it is
recommended to add a small capacitance to this line.
9
Not Used
-
10
Not Used
-

E-OCD II Interface Hardware E-OCD II Debugger User’s Manual
16
Figure 2-2 E-OCD II Debugger
2.1.3 Hardware Connection/Disconnection Procedures
As mentioned before, the E-OCD II interface does not support hot plugging—which may damage the
interface permanently.
What is hot plugging :
Hot plugging is plugging in or out a hardware device while the target system is powered.
2.1.4 E-OCD II Interface Connection
The E-OCD II interface supports both the OCD and OCD II interfaces. But since the OCD and OCD II
interface protocols are not compatible with one another, the target protocol must be selected first.
Even if the target MCU uses the OCD or OCD II interface, it does not enter debug mode if the
procedure below is not correctly followed:
1) Power off the target system.
2) Connect the E-OCD II interface to the target system.
3) Connect the E-OCD II interface to PC.
4) Launch the debugger software.
5) Select the target Devices series in the debugger software.
6) Wait until initialization of the E-OCD II interface is complete.
7) Power on the target system

E-OCD II Debugger User’s Manual E-OCD II Interface Hardware
17
2.1.5 E-OCD II Interface Disconnection
The target system must be powered off before disconnecting the OCD interface to avoid damage to
the interface module.
2.1.6 E-OCD II Power Out to Target System
E-OCD II can Power out to target system two types of voltages(3.3V, 5.0V). User can select the
output voltage using a switch on E-OCD II. And then push the power button icon on OCD debugger
program.
1) Select power voltage 3.3V or 5.0V on E-OCD II switch
2) Target Power OFF
3) Push the button icon on OCD Debugger program.

Debugger Software (for Microsoft Windows) E-OCD II Debugger User’s Manual
18
3Debugger Software (for Microsoft Windows)
3.1 Debugger Software Features
The debugger supports both the OCD and OCD II interface. As the OCD and OCD II interface
protocols differ from each other, you must first select the target MCU series. Debugger software
support three kinds of ABOV debugger type(E-OCD II, OCD, OCD II debugger).
Figure 3-1 Debugger Program
1) The ‘power icon’is black off when the E-OCD II is first connected to the PC
Figure 3-2 Toolbar : Power Icon
2) When the ‘power icon’is selected, the icon color is changed and the power voltage is output
- The output voltage can be changed with E-OCD II switch (3.3V or 5.0V)
Figure 3-3 Toolbar : Power Icon

E-OCD II Debugger User’s Manual Debugger Software (for Microsoft Windows)
19
3) The dialog window for the warning about current is shown.
Figure 3-4 Warning Message
4) Device is recognized successfully if it has a good connection with target board.
Figure 3-5 Device Recognition
3.2 Common Features
The debugger software supports the MC9x/A9x series developed by ABOV Semiconductor Co., Ltd.
The following features are provided, regardless of whether the OCD or OCD II interface is used:
Detect the target device automatically
Use symbolic debugging
- Source file view
- Global/Local variables view
- Each device’s SFR (special function register) names
Display various target memories
- CODE, XDATA, IDATA, and SFR
- Users can edit these data sets directly in the debugger
Display code data in a disassembled format
Support line assembly
Support break toggling
Calculate code checksum

Debugger Software (for Microsoft Windows) E-OCD II Debugger User’s Manual
20
Support the following emulation methods :
- Real-time emulation
- Step emulation (source line level or code level)
- Emulation abortion
Save and load the most recent debugging environment automatically.
Support all OCD device series
- When connected with an OCD device, the OCD II interface functions in the same manner
as the OCD interface.
Support all OCD II device series—which support a maximum of 12 breaks
- Four of them are fixed as program counter breaks.
- The other eight breaks can be used either as program counter breaks or combined or
individual event breaks:
a. Signed and unsigned supported
b. Big endian and little endian supported
Support displaying run-time data monitoring. The values of a global variable are updated
automatically during emulation.
Support measuring the target device’s operating frequency
Support trimming the device’s internal OSC frequency
Support emulation time measurement
Note : The RTIME pin must be connected to measure the emulation time.