Keil (mdk-arm) use Tutorial (iii) _ Online debugging

As I am directly using (Open the existing software engineering), if you need to download the above demo reference software engineering only line. The project by default is to use hardware online debugging, followed by each point to tell.

1. Compile + Debug

Open Software engineering, compile-and- debug

The compilation proposal here uses the build Target (the 2nd button) to compile the project (such as animation), that is, using the shortcut key F7. Translate (the 1th button) is the compilation of the currently active file. Rebuild all target files (the 3rd button) is to recompile all of the destination file (s).

Online debugging and classification: software on-line debugging and hardware on-line debugging; Because the cost of hardware is cheaper now, generally we use hardware on-line debugging, that is, software download directly to the chip, we check the running status.

2. Reset + Full speed operation

Reset , full speed operation

Reset , so that the program resets to the initial;

Running F5at full speed, we can break the point in a lot of places and let the program run to the breakpoint location, and the program stops.

3. Single-Step commissioning

"Single-Step debugging" is the one-point button, the program runs a step. A function is entered in the encounter.

Click the icon button, or press the shortcut key F11.

(This cancels the above breakpoint)

4. Progressive Commissioning

Step-by-line debugging, that is, every point of the button, the program runs a line. The function encountered does not enter.

Click the icon button, or press the shortcut key F10.

5. Jump out of debugging

"Out of debugging" is to pick out the function debugging, that is, every point once the button, the program jumps out of a function until the outermost function (main function).

Click the icon button, or press the shortcut key Ctrl + F11.

6. Run To Cursor

"Run to Cursor" to place the cursor somewhere, click the button (or Ctrl + F11), the program execution to the position of the cursor will stop (if the program can be executed to the position of the cursor).

7. Jump to Pause Line

This function is effective when the program stops running, the main function is that we open a lot of files, do not know where to turn the program, click the Change button to know our program paused in that position.

8. Debug Window

The "Debug window" is a window that can be viewed while debugging, unlike a window that is normally in edit mode. The options under the View menu are small at the time of editing, but in debug mode there are many more options, which are the windows that are viewed during debugging (see).

Let's focus on a common debugging window.

A. Memory window, which is the window where we view the variable

B. The System peripheral window, which is the Peripheral Register Value View window

Ⅳ, description

The above is based on the mdk-arm in the Keil development tool to summarize, Keil C51, etc. may be different in some places. The function of each tool needs to be practiced by itself, and long-term use can be used to achieve the point of flexible use, do not recommend rote memorization.

The above summary is for reference only, if has the wrong place, please understanding.

Keil (mdk-arm) use Tutorial (iii) _ Online debugging