STM32F4开发实战：使用Keil MDK与SWV调试

5星 · 超过95%的资源需积分: 9 30 浏览量更新于2024-07-25 收藏 1.58MB PDF 举报

"STM32F4discovery开发工具Keil使用方法" 本文将详细介绍如何使用Keil MDK工具套装来开发基于STM32F4的项目，特别是结合STMicroelectronics Cortex™-M4处理器和内建的ST-Link V2调试适配器。Keil MDK是一个强大的集成开发环境（IDE），它包括了μVision IDE，适用于各种ST ARM处理器，如STM32F4系列。首先，Keil MDK提供了对STM32F4系列处理器的全面支持，并且包含了大量的示例代码，可以在μVision IDE中进行项目创建和设备选择。通过选择“Project”菜单下的“Select Device for target...”，用户可以从完整的ST ARM处理器列表中选择合适的型号。在教程中，特别提到了Serial Wire Viewer (SWV)的使用，这是一个用于调试Cortex-M系列处理器的工具，它允许开发者观察和分析处理器内部的运行情况，如程序计数器、寄存器状态等。同时，ST-Link V2是STM32 Discovery板上内置的调试适配器，可实现与开发环境的无缝连接，方便进行硬件调试。对于初学者，Keil还提供了一个免费的评估版本——Keil MDK-Lite，该版本虽然限制了代码大小不能超过32K字节，但大多数Keil示例代码都能在这个限制内编译运行。如果需要解除这个限制，只需添加有效的许可证号码即可升级为完整商业版。此外，Keil MDK还包括了完整的RTX实时操作系统（RTOS）源代码，这使得在STM32F4平台上实现多任务调度和管理变得更加简单。RTX是一个功能强大的RTOS，广泛应用于嵌入式系统，它在所有MDK变种中都可用。对于那些需要在STM32处理器上运行Linux、Android或裸机程序的开发者，ARM的DS-5工具套件提供了支持。通过本教程的学习，开发者将掌握使用Keil MDK与STM32F4 Discovery板进行项目开发的基本技能，包括IDE的使用、SWV调试和ST-Link V2的连接，以及如何利用Keil提供的资源进行高效的嵌入式系统开发。

STMicroelectronics Discovery STM32F407 Lab with ARM

Keil™ MDK toolkit www.keil.com

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 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 the preceding page 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 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 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. This is a rather

important feature. Earlier versions of µVision required a double

click to set a breakpoint and displayed as a square.

7. Remove all the breakpoints when you are done for the

next exercise.

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

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) doesn’t work, click on the Disassembly window to

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

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.

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 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.

剩余31页未读，继续阅读

supereally

粉丝: 0
资源: 5

STM32F4开发实战：使用Keil MDK与SWV调试

STM32F4 Discovery BSP源码：Keil开发环境指南

STM32F4DISCOVERY开发板使用手册

STM32F4DISCOVERY开发板用户手册

STM32F4DISCOVERY开发板使用向导_CN_stm32_stm32f4discovery_开发板_

stm32f4-discovery-keil-sdio-fatfs-master.zip

STM32F4-Discovery_I2C.zip_I2C STM32F4_keil stm32_stm32_stm32f4 I

STM32F4-Discovery_UART.zip_farz86_keil stm32_keil stm32f4_stm32F

STM32F4DISCOVERY

STM32F4discovery examples

STM32F4 discovery 学习笔记

最新资源