Wiznet W7100A User manual

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.11
W7100A / W7100 Debugger Guide
W7100A / W7100
Debugger Guide
Version 1.1
© 2012 WIZnet Co., Inc. All Rights Reserved.
For more information, visit our website at http://www.wiznet.co.kr

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.12
W7100A / W7100 Debugger Guide
Table of Contents
1 Driver installation for the Debugger ................................................................ 3
2 Connect the Debugger................................................................................. 5
3 Installation of the W7100A / W7100 Debugger.................................................... 7
4 KEIL Project............................................................................................. 8
5 Debugger menu........................................................................................14
5.1 Open project...............................................................................14
5.2 Initialize the W7100A / W7100 Debugger .............................................16
5.3 Run and Stop...............................................................................18
5.4 Break Point.................................................................................20
6 Search & Variable Window...........................................................................24
6.1 Search Window ............................................................................24
6.2 Local Variable Window ...................................................................26
6.3 Global Variable Window..................................................................26
6.4 Symbol window............................................................................26
6.5 Register window...........................................................................27
7 Memory window.......................................................................................28
7.1 IData Memory Window....................................................................29
7.2 External Data Memory Window .........................................................29
7.3 Code Memory Window....................................................................30
7.4 Flash Memory Window....................................................................30
7.4.1 Code Memory Domain ...........................................................30
7.4.2 Data Memory Domain............................................................31

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.13
W7100A / W7100 Debugger Guide
1Driver installation for the Debugger
Connect the Debugger and PC with USB cable, and then the ‘new hardware search window’ will open
as figure 1.1 below.
Select ‘Automatically setup the software (I)’ and click the Next (N) button.
[Fig.1.1] The new hardware search window 1
If it is not automatically installed, select the ‘Install from a list or specific location (Advanced) and set
our attached driver as below.
[Fig.1.2] The new hardware search window 2
Wait for searching the device driver of the Debugger. When the device driver installation is completed,

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.14
W7100A / W7100 Debugger Guide
click the END button to finish.
[Fig.1.3] Completing the new hardware searching #2

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.15
W7100A / W7100 Debugger Guide
2Connect the Debugger
This section will explain how the Debugger is connected with iMCU7100EVB. Connect the
Debugger to the DTAG of IMCU7100EVB.
[Fig.2.2] iMCU7100EVB
[Fig.2.2] W7100A / W7100 Debugger
Connect the other DTAG cable between the Debugger and iMCU7100EVB. The red line of
DTAG cable must be connected to line number 1 of iMCU7100A DTAG socket. Also connect the
USB cable between the Debugger and PC. Next, insert the power cable to the IMCU7100EVB,
and push the EVB reset button as figure 2.1. Then, push the debugger reset button of the
Debugger. Confirm the LED5 (RUN LED) after pushing these reset button.
DTAG
LED5
USB
Reset
Button
Reset
DTAG

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.16
W7100A / W7100 Debugger Guide
If the Debugger successfully recognizes the W7100A / W7100, the LED5 (RUN LED) will turn
on. But if the LED5 is not turned on, it means that W7100A / W7100 is not recognized. Check
the connecting cable or try to reset the IMCU7100EVB and the Debugger. The LED5 should be
turned on before using the W7100A / W7100 Debugger.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.17
W7100A / W7100 Debugger Guide
3Installation of the W7100A / W7100 Debugger
In this section, the installation of W7100A / W7100 Debugger is explained. First, run the
W7100A / W7100 Debugger install file.
[Fig.3.1] The W7100A / W7100 Debugger install file
Then the installation of iMCU7100EVB debugger is started. Push the Next button to setup.
[Fig.3.2] Setup the W7100A / W7100 Debugger
[Fig.3.3] End of debugger installation

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.18
W7100A / W7100 Debugger Guide
4KEIL Project
Projects that are supported by the W7100A / W7100 debugger are as below.
Keil uVision2 project
Keil uVision3 project
Only hex file (Restricted symbol function)
※The W7100A / W7100 Debugger don’t support the KEIL µVision4 or upper version project. But user
can easily convert the µVision4 to µVision3 project as shown in the figure 4.1 to use the W7100A /
W7100 debugger.
<Fig.4.1> Save Project to µVision3 format
※Caution on W7100A / W7100A Lock function
The W7100A / W7100A has the memory lock function. If the lock was set, user cannot use
the W7100A / W7100 debugger because it cannot read anything from W7100A / W7100A
memory. So user should unlock to use the W7100A / W7100 debugger properly. It is easy to
unlock using the WizISP program. As shown in the figure 4.2, clear the check box and click the
“Lock” button. Whole memory will be erased after the unlocking so user should re-write the
firmware again.
Please refer to the Wiz ISP user manual for more detailed information about WizISP. WizISP
program and user manual are available on the WIZnet website.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.19
W7100A / W7100 Debugger Guide
<Fig.4.2> Unlock the W7100A / W7100A using WizISP program
The W7100A / W7100 debugger cannot recognize multi directory structure of KEIL project
so all project file and source file must be placed in same directory to use W7100A / W7100
debugger. And the ‘make hex file’ option and ‘make symbol’ option should be activated in
the KEIL project. If they are not activated, the W7100A / W7100 debugger cannot find the hex
file to load. Also, an error message could appear even if it finds the hex file.
Since the W7100A / W7100 debugger use slower clock than normal running clock, running
speed under the debugging mode is very slow. So we recommend that don’t use a delay
function or something like that.
First, open the KEIL project.
Click ‘Project’ => ‘Options for Target ‘Target name’ menu.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.110
W7100A / W7100 Debugger Guide
[Fig.4.3] Open the KEIL project
Check the ‘Create HEX File’ option from the ‘Output’ tap as figure 4.2.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.111
W7100A / W7100 Debugger Guide
[Fig.4.4] Output tap of the ‘Options for Target’ window
Select the ‘Listing’ tap and check the ‘Symbols’ option of the ‘C Compiler Listing’ region.
[Fig.4.5] Listing tap of the ‘Options for Target’ window
Also check the ‘Symbols’ option of the ‘Assembler Listing’ region. The ‘Assembler Listing’ is optional.
Click the ‘OK’ button to finish, and compile the KEIL project.
Confirm the HEX file in the project directory after compiling.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.112
W7100A / W7100 Debugger Guide
[Fig.4.6] Hex file of the KEIL project
If the KEIL project includes the assembly code such as xxx.SRC file, the ‘Generate Assemble
SRC File’ and ‘Assembler SRC File’ options must be checked.
First, open the Options for File ‘xxx.c’ that uses the Assemble code.
[Fig.4.7] Open the Options for File ‘xxx.c’

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.113
W7100A / W7100 Debugger Guide
Then, check the ‘Generate Assembler SRC File’ and ‘Assemble SRC File’ options.
[Fig.4.8] Setting the Options for File ‘xxx.c’

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.114
W7100A / W7100 Debugger Guide
5Debugger menu
5.1 Open project
The W7100A / W7100 debugger can debug the KEIL project or the hex file. To debug the
KEIL project or the hex file, run the W7100A / W7100 debugger and open the hex file.
Open Project.
The Open Project command is used to open a project.
Click the icon of the toolbar. It can also be done by clicking Project Menu => Open or
pushing the short key Ctrl + O
The file open browser is opened as figure 5.2 ‘File open browser.’
[Fig.5.3] Open project

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.115
W7100A / W7100 Debugger Guide
[Fig.5.2] File open browser
If the user opens the project that is consisted only with a HEX file, the Debugger will show
a caution message. And it shows only ‘Assembly window’.
[Fig.5.3] Complete opening the project

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.116
W7100A / W7100 Debugger Guide
*Note: When the user open the project and have the error message like shown below, the user must
delete the xxx.SRC file in project directory, and check both the ‘Generate Assembler SRC File’ and
‘Assemble SRC File’ options to avoid error on the W7100A / W7100 debugger.
For a more detailed solution, please refer to section4 ‘KEIL Project’.
[Fig.5.4] Open error message
Reload project
The Reload command is used to reload a project. When the loaded project is changed, click
the reload toolbar button to reload the project. It can also be done by clicking ‘Project’
=> ‘Reload’ or pushing the short key F4.
Close project
The Close project command is used to close a project. Select ‘Project’ => ‘Close’ or push
the short key Ctrl + Q.
*Note: While using the W7100A / W7100 debugger, the user must use the ‘stop’ command in
order to close the debugger.
5.2 Initialize the W7100A / W7100 Debugger
This section is for initialization of the debugger and iMCU7100EVB
[Fig.5.5] Initialize menu
Debugger and board reset
The Debugger and board reset command is used to reset the debugger and board
simultaneously. If breakpoints were set, all initialized breakpoints will be removed.
To reset, click the button on the toolbar, or select ‘Tool menu’ => ‘Init Debugger and
Board reset’ menu. Then the Debugger and board will reset.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.117
W7100A / W7100 Debugger Guide
Board reset only
The Board reset command only is used to reset the board only. If breakpoints were set, they
will be maintained. To reset the board, click the button of the toolbar or select the
‘Debug menu’ => ‘Board reset’. It can also be done by short key F2.
Image load
The Image load command is used to load an image.
Write the HEX image for debugging to the Flash memory.
Click the button or select Debug menu => Image Load menu to execute ‘Image Load.’
It can also be done by short key F3.
If the image writing and verifying is successful, ‘Write OK’ message will show.
Note: If there is a mismatch between the board image file and present HEX file, the error
message is shown when execute the ‘Debugger commands’ such as ‘Continue, Step, Next’.
[Fig.5.6] Load image mismatch
Debugging
The W7100A / W7100 Debugger serves ‘Debug’ and ‘Tool’ menu and Toolbar button for
debugging.
[Fig.5.7] Deugging menu
Go to Source Line
The Go to Source Line command is used to move the cursor to the wanted source line. To use this
function, select the ‘Tool’ menu => ‘Go to Source Line’ or use short key Ctrl + G.
Find
The Find command is used to find some words on the source window. To use this function, select the
‘Tool’ menu => ‘Find’ or use short key Ctrl + F.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.118
W7100A / W7100 Debugger Guide
5.3 Run and Stop
This section will explain how to use commands like step in, out, next, and more
Continue
The Continue command runs the program until the Break point is met. To use this command,
click the button on the toolbar or select the Debug menu => Continue. It can also be
done by short key F5.
During the Continuing state, user cannot use the debugging menu. In order to use the
debugging menu, execute the Stop command.
Stop
The Stop command is used to stop the running program. To use this command, click the
button on the toolbar or select the Debug menu => Stop. It can also be done by short
key F6.
The debugging commands (Search, memory view, break point, etc.) are executed only in the Stop state.
Step
The step command is used to run only one specific line among all lines. The Step command is executed
in units of one line of the C code. If there is a Function call, the Step command will enter into the
related Function. After the execution, the debugger is stopped and waits for the next command.
To use this command, click the button on the toolbar or select the Debug menu => Step. It
can also be done by short key F11. If the user has only the HEX file to debug, the
Step command executes one instruction, just like the Stepi command.
Next
The Next command is basically the same as the Step command. The Next command is executed in units
of one line of the C code. But if there is a Function call, the Next command does not enter into the
Function. After the execution, the debugger is stopped and waits for the next command.
To use this command, click the button on the toolbar or select the Debug menu => Next. It
can also be done by short key F10. If the user has only the HEX file to debug, the
Step command executes one instruction, just like the Nexti command.
Stepi
The Stepi command executes only one instruction. If the instruction is a Function call, the command
enters into the related Function. After the execution, the debugger is stopped and waits for the next
command.
To use this command click the button on the toolbar or select the Debug menu => Stepi. It
can also be done by short key F7.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.119
W7100A / W7100 Debugger Guide
Nexti
The Nexti command executes one instruction. But the command does not enter into the related
Function even if the instruction is a Function call. After its execution, the debugger is stopped and waits
for next command.
To use this command click the button or select the Debug menu => Nexti.
It can also be done by short key F6.
Run to cursor line
The ‘Run to cursor line’ command executes the code until the cursor on the debugger source window is
met.
To use this command, select the push the mouse right button => select ‘Run To Cursor Line(n)’ or
select the Debug Menu => Run To Cursor Line.
[Fig.5.8] Run To Cursor Line command
Sometimes the ‘Run To Cursor Line’ command continues when the cursor is not properly set.
If that is the case, execute the Stop command to stop it.

© Copyright 2012 WIZnet Co., Inc. All rights reserved. Ver. 1.120
W7100A / W7100 Debugger Guide
5.4 Break Point
This section will explain how to set/clear and find breakpoints. The breakpoint can be set
only when the debugger is not being used. If the user was using the debugger, use the Stop
command to stop in order to set the breakpoint.
[Fig.5.9] Break point of the debugger
Set break point
To set the breakpoint
1. Click the shadowed region aside of the source window
2. Locate the cursor and click the button on the Toolbar
3. Locate the cursor and click the Debug Menu => ‘Set Break’
4. Double click the C code line in the source window
5. Double click the Assembly code line in the Assembly window
6. Locate the cursor in the Assembly window and click the on the Assembly Toolbar
7. Short key F9
Set the breakpoint and execute the Continue command. Then the debugger will run until it
meets the breakpoint and will stop at the checked breakpoint. After that, the user can use