STM32F407 Keil MDK调试教程：异常处理与SerialWireViewer应用

需积分: 9 34 浏览量更新于2024-07-15 收藏 1.35MB PDF 举报

本篇文档是关于在Keil环境下进行STM32F407 Discovery板的调试指南，适用于使用ARM® Keil™ MDK工具包的用户。主要内容涵盖了以下几个关键知识点： 1. **Keil环境介绍**：文档首先明确了版权信息，指出此教程适用于2014年的ARM Limited及其关联公司，并介绍了使用的是STMicroelectronics的Cortex™-M4处理器，配合Keil MDK工具套件，尤其是μVision®集成开发环境（IDE）。 2. **目标平台与支持**：实验对象是STMicroelectronics的STM32F407 Discovery评估板，它配备有内置的ST-Link V2 Debug Adapter，这使得在Keil MDK中进行调试更为方便。文档特别提到了Keil MDK对STARM处理器的广泛支持，包括通过Keil Device Database查阅完整列表。 3. **调试功能与SWV配置**：重点讲解了Serial Wire Viewer (SWV) 的使用，这是一种在硬件中用于实时观察嵌入式系统内部数据流的工具。通过SWV，开发者可以深入理解处理器的工作状态，包括异常中断处理和堆栈跟踪。 4. **学习目标**：在完成本教程后，读者将能够熟练地在Keil MDK环境中操作Cortex-M4处理器，包括设置断点、单步执行、查看寄存器值和内存映射等基本调试技巧。 5. **限制条件**： Keil MDK-Lite是免费版本，但代码大小限制为32KB。大部分Keil示例都应在这一限制范围内运行，对于更大的项目，可能需要购买完整版MDK。 6. **Linux支持**：对于运行在Linux环境的STM32处理器，包括Android和裸金属应用，ARM DS-5™提供了相应的支持，有兴趣的开发者可访问ARM官网获取更多信息。本文档为想要利用Keil MDK工具对STM32F407 Discovery进行调试的开发人员提供了一个详尽且实用的指南，涵盖从环境设置到高级功能的全面教学。无论是初学者还是经验丰富的工程师，都能从中找到所需的知识和技能提升点。

STMicroelectronics Discovery STM32F407 Lab with ARM

Keil™ MDK toolkit www.keil.com/st

6) Blinky example program using the ST Discovery board:

We will connect a Keil MDK development system using real target hardware using the built-in ST-Link V2 debug adapter.

1. Start µVision by clicking on its desktop icon. Connect your PC to the board with a USB cable to CN1.

2. Select Project/Open Project. Open the file C:\Keil\ARM\Boards\ST\STM32F4-Discovery\Blinky\Blinky.uvproj

3. By default, the ST-Link is selected. If this is the first time you have run µVision and the Discovery board, you will

need to install the USB drivers. See the configuration instructions on page 4 in this case.

4. Compile the source files by clicking on the Rebuild icon. . You can also use the Build icon beside it.

5. Program the STM32 flash by clicking on the Load icon: Progress will be indicated in the Output Window.

6. Enter Debug mode by clicking on the Debug icon. Select OK if the Evaluation Mode box appears.

Note: You only need to use the Load icon to download to FLASH and not for RAM operation if it is chosen.

7. Click on the RUN icon. Note: you stop the program with the STOP icon.

The LEDs on the STM32F4 Discovery board will now blink in succession.

Press the USER button and they will all come on.

Now you know how to compile a program, program it into the STM32 processor Flash, run it and stop it !

Note: The board will start Blinky stand-alone. Blinky is now permanently programmed in the Flash until reprogrammed.

7) Hardware Breakpoints:

The STM32F4 has six hardware breakpoints that can be set or unset on the fly while the program is running.

1. With Blinky running, in the Blinky.c window, click on a darker grey block in the left margin on a line in main() in the

while loop. Between around lines 80 through 91 will suffice.

2. A red circle will appear and the program will stop.

3. Note the breakpoint is displayed in both the disassembly and source windows as shown below:

4. You can set a breakpoint in either the Disassembly or Source windows as long there is a gray rectangle indicating the

existence of an assembly instruction at that point.

5. Every time you click on the RUN icon the program will run until the breakpoint is again encountered.

6. You can also click on Single Step (Step In) , Step Over and Step Out .

TIP: If single step (Step In) doesn’t work, click on the

Disassembly window to bring it into focus. If needed, click on a

disassembly line. This tells µVision you want to single step at the

assembly level rather than at the C source level.

TIP: A hardware breakpoint does not execute the instruction it is

set to. ARM CoreSight breakpoints are no-skid. These are rather

important features for efficient software development.

Remove all the breakpoints when you are done for the next

exercise by clicking on them again.

TIP:

You can delete the breakpoints by clicking on them or

selecting Debug/Breakpoints (or Ctrl-B) and selecting Kill All.

Click on Close to return.

TIP:

You can view the breakpoints set by selecting

Debug/Breakpoints or Ctrl-B.

STMicroelectronics Discovery STM32F407 Lab with ARM

Keil™ MDK toolkit www.keil.com/st

8) Call Stack + Locals Window:

Local Variables:

The Call Stack and Local windows are incorporated into one integrated window. Whenever the program is stopped, the Call

Stack + Locals window will display call stack contents as well as any local variables belonging to the active function.

If possible, the values of the local variables will be displayed and if not the message <not in scope> will be displayed. The

Call + Stack window presence or visibility can be toggled by selecting View/Call Stack window.

1. Run and Stop Blinky. Click on the Call Stack + Locals tab.

2. Shown is the Call Stack + Locals window.

The contents of the local variables are displayed as well as

names of active functions. Each function name will be

displayed as it is called from the function before it or from

an interrupt or exception.

When a function exits, it is removed from the list.

The first called function is at the bottom of this table.

This table is active only when the program is stopped.

3. Click on the Step In icon or F11:

4. Note the function different functions displayed as you step through them. If you get trapped in the Delay function,

use Step Out or Ctrl-F11 to exit it faster.

5. Click numerous times on Step In and see other functions.

6. Right click on a function name and try the Show Callee Code and Show Caller Code options as shown here:

7. Click on the StepOut icon to exit all functions to return to main().

TIP: If single step (Step In) does not work, click on the Disassembly window to

bring it into focus. If needed, click on a disassembly line to step through

assembly instructions. If a source window is in focus, you will step through the

source lines instead.

TIP: You can modify a variable value in the Call Stack & Locals window when the program is stopped.

TIP: This is standard “Stop and Go” debugging. ARM CoreSight debugging technology can do much better than this. You

can display global or static variables updated in real-time while the program is running. No additions or changes to your code

are required. Update while the program is running is not possible with local variables because they are usually stored in a

CPU register. They must be converted to global or static variables so they always remain in scope.

If you have a ULINKpro and ETM trace, you can see a record of all the instructions executed. The Disassembly and Source

windows show your code in the order it was written. The ETM trace shows it in the order it was executed. ETM provides

Code Coverage, Performance Analysis and Execution Profiling.

Changing a local variable to a static or global normally means it is moved from a CPU register to RAM. CoreSight can view

RAM but not CPU registers when the program is running.

Call Stack:

The list of stacked functions is displayed when the program is stopped as you have seen. This is useful when you need to

know which functions have been called and what return data is stored on the stack.

TIP: You can modify a local variable value when the program is stopped.

TIP: You can access the Hardware Breakpoint table by clicking on Debug/Breakpoints or Ctrl-B. This is also where

Watchpoints (also called Access Points) are configured. You can temporarily disable entries in this table.

Selecting Debug/Kill All Breakpoints deletes Breakpoints but not Watchpoints.

剩余32页未读，继续阅读

shengsg

粉丝: 4
资源: 8

STM32F407 Keil MDK调试教程：异常处理与SerialWireViewer应用

apnt_198_uvsock.zip

apnt209.pdf

请详细列出STM32f103的定时器2的输入捕获功能的使用代码。

举例详细解释 netstat -apnt产生的结果

解释 netstat -apnt

安全-密码相关技术学习路线导图

Selenium工具用于web应用程序的端到端自动化测试

line_profiler-2.1.2-cp35-cp35m-win_amd64.whl

课程设计-1-最优配对.doc

学生综合考评管理系统.zip

最新资源