Single-Chip Ethernet Controller Chip W7100A / W7100 Debugger Guide (Part 2)

The previous article talked about driver installation, debugger connection and how to install W7100A / W7100 Debugger. Today we will continue with the introduction of the Debugger menu. I hope it will be helpful to everyone!

Let's first briefly introduce the basic features of W7100 and W7100A. The network microprocessor W7100 provides an all-in-one embedded network solution (embedded 8051 microcontroller + TCP/IP protocol stack + 10/100 high-speed Ethernet MAC/PHY). The W7100A (100Pin package) is 100% compatible with W7100. W7100A is an upgraded version of W7100, adding some new functions. For details, please log in to the official website.

5. Debugger Menu

5.1 Open Project

W7100A / W7100 Debugger program can debug KEIL project files and HEX files. First run W7100A / W7100 Debugger program and open the hex file.

❀Open the project

 

Use the Open Project command to open a project.

Click the file icon in the toolbar, or select Project Menu=>Open or use the shortcut key Ctrl+0 to complete it.

As shown in Figure 5.2, the browser opens the file.

 

 

If the project opened by the user only includes a HEX file, the Debugger will prompt a warning message and only display the 'Assembly window' interface.

 

*Note: When the user opens a project and the following error message appears, the user must delete the

xxx.SRC file, and then select the 'GenerateAssembler SRC File' and 'Assemble SRC File' options to prevent

An error occurred in the W7100A/W7100 Debugger program.

 

For additional details on the solution approach, see Chapter 4, 'KEIL Engineering'.

 

 

❀ Reload Project

Use the Reload command to reload a project. When the loaded project changes, click the Reload toolbar button to reload it. You can also select 'Project'=>'Reload' or use the shortcut key F4 to complete it.

 

❀ Close project

Use the Close command to close a project. Select 'Project' => 'Close' or use the shortcut Ctrl + Q to do so.

*Note: When using W7100A/W7100 Debugger, the user must use the 'stop' command to shut down

Debugger program.

 

5.2 W7100A / W7100Debugger Program Initialization

 

This chapter mainly introduces the initialization process of the iMCU7100EVB Debugger program.

 

❀ Debugger program and development board reset

The debugger and board reset command is used to reset the debugger program and the development board at the same time. All breakpoints that have been set will be moved.

Click the button on the toolbar , or select 'Tool menu'=>'Init Debugger and Board reset' to reset the Debugger program and development board.

 [page]

❀ Reset only the board

The Board reset command can only be used to reset the board. If breakpoints have been set, they will still be retained. Click the button on the toolbar or select 'Debug menu' => 'Boardreset' to reset the board. You can also use the shortcut key F2.

 

❀ Image loading

The Image load command is used to load an image.

Write a HEX image to flash memory for debugging.

 

Click the button or select Debug menu => Image Load menu to perform 'Image Load'. You can also use the shortcut key F3 to complete it.

If the image is written and verified successfully, the message 'Write OK' will be displayed.

Note: If the board image file does not match the current HEX file, the following error message will appear when executing 'Debugger commands' such as 'Continue, Step, Next', etc.

 

 

❀ Debug

The W7100A / W7100 Debugger program provides 'Debug' and 'Tool' menus and toolbar buttons for debugging.

 

❀ Go to the Source line

The Go to Source Line command is used to move the cursor to the desired source line. You can select 'Tool'=>'Go to Source Line' or use the shortcut key Ctrl+G to achieve this function.

 

❀ Search

The Find command is used to search for some words in the source code window. You can select 'Tool' menu => 'Find' or use the shortcut key Ctrl+ F to achieve this function.

 

5.3 Run and Stop

 

This chapter will introduce how to use some commands such as step in, step out, and next.

❀ Continue

The Continue command runs the program until a breakpoint is encountered. Click the button on the toolbar or select Debug menu => Continue, or use the shortcut key F5 to use this command.

In the Continue state, the user cannot use the debug menu unless the Stop command is executed.

 

❀  Stop

The Stop command is used to stop the running program. Click the button in the toolbar or select Debug menu => Stop, or use the shortcut key F6 to execute this command.

Debug commands (search, memory view, breakpoints, etc.) can only be executed in Stop state.

 

❀Step

The Step command is used to run a specified line. If there is a function call, the Step command will enter the related function. After the execution is completed, the Debugger program stops and waits for the next command.

Click the button in the toolbar or select Debug menu => Step, or use the shortcut key F10 to execute this command. If the user only needs to debug the HEX file, the Step command is similar to the Nexti command, executing an instruction description.

 

❀ Next

The Next command is similar to the Step command. The Next command executes a specified line of C code, that is, it executes the command in units of one line. However, if there is a function call, the Next command will not enter the function. After the execution is completed, the Debugger stops and waits for the next command.

Click the button in the toolbar or select Debug menu => Next, or use the shortcut key F10 to execute this command. If the user only needs to debug the HEX file, the Next command is similar to Nexti, executing an instruction description.

 

❀ Stepi

The Stepi command executes only one instruction. If the instruction is a function call, then this command will enter the related function. After the execution is completed, the Debugger stops and waits for the next command.

Click the button in the or select Debug menu => Stepi, or use the shortcut key F7 to execute this command.

 

❀ Nexti

Nexti command executes only one instruction. If the instruction is a function call, this command cannot enter the related function. After execution, the debugger stops and waits for the next command.

Click the button in the toolbar or select Debug menu => Nexti, or use the shortcut key F6 to execute this command.

 

❀ Run to cursor line

The 'Run to cursor line' command runs to the cursor position and stops.

Right click => Select 'Run To Cursor Line(n)' or select Debug menu => Run To Cursor Line.

 

If the cursor position is not set correctly, it may cause the 'Run To Cursor Line' command to continue executing. If this happens, execute the stop command to end the run.

 [page]

5.4 Break Point

 

This chapter will introduce how to set/clear and find breakpoints.

If you use the debugger program, you can set breakpoints by ending the program with the stop command.

 

 

 

That’s all for the second part. I will introduce the last part of this article to you later. Stay tuned!