Ubuntu环境下使用stlink调试和下载stm32f4-discovery程序
2014-07-24 13:32
489 查看
原创,转载标明出处
首先下载stlink的Linux版本,下载地址。
然后解压到你所指定的路径下,参照其中的README文件进行编译配置。如下:(笔者在此将对关键点进行标注)
按照上边步骤编译配置,就可以调试和下载应用程序。
首先下载stlink的Linux版本,下载地址。
然后解压到你所指定的路径下,参照其中的README文件进行编译配置。如下:(笔者在此将对关键点进行标注)
HOWTO ===== First, you have to know there are several boards supported by the software. Those boards use a chip to translate from USB to JTAG commands. The chip is called stlink and there are 2 versions: . STLINKv1, present on STM32VL discovery kits, . STLINKv2, present on STM32L discovery and later kits. 2 different transport layers are used: . STLINKv1 uses SCSI passthru commands over USB, . STLINKv2 uses raw USB commands. Common requirements(依赖环境) ~~~~~~~~~~~~~~~~~~~ . libusb-1.0 (You probably already have this, but you'll need the development version to compile)
(这个工具只需要执行sudo apt-get install libusb-dev && sudo apt-get install libusb-1.0-0-dev这两个命令即可。) . pkg-config (这个工具一般Ubuntu都会默认安装,注意变量PKG-CONFIG-PATH的设置) IF YOU HAVE AN STLINKv1 ~~~~~~~~~~~~~~~~~~~~~~~ The STLINKv1's SCSI emulation is very broken, so the best thing to do is tell your operating system to completely ignore it. Options (do one of these before you plug it in) *) modprobe -r usb-storage && modprobe usb-storage quirks=483:3744:i or *)1. add "options usb-storage quirks=483:3744:i" to /etc/modprobe.conf *)2. modprobe -r usb-storage && modprobe usb-storage or *)1. cp stlink_v1.modprobe.conf /etc/modprobe.d *)2. modprobe -r usb-storage && modprobe usb-storage IF YOU HAVE AN STLINKv2(我们的开发板支持STLINKv2,所以这里不做配置) ~~~~~~~~~~~~~~~~~~~~~~~ You're ready to go :) COMPILING(编译:下边3个指令即可) ~~~~~~~~~ This project was converted to Autotools by a well meaning individual. The following steps will build the project for you. $ ./autogen.sh $ ./configure $ make USING THE GDBSERVER(使用GDB调试服务) ~~~~~~~~~~~~~~~~~~~ To run the gdb server: (you do not need sudo if you have set up permissions correctly) (此时连上你的开发板,一般都要sudo) $ make && [sudo] ./st-util There are a few options: ./st-util - usage: -h, --help Print this help -vXX, --verbose=XX Specify a specific verbosity level (0..99) -v, --verbose Specify generally verbose logging -s X, --stlink_version=X Choose what version of stlink to use, (defaults to 2) -1, --stlinkv1 Force stlink version 1 -p 4242, --listen_port=1234 Set the gdb server listen port. (default port: 4242) -m, --multi Set gdb server to extended mode. st-util will continue listening for connections after disconnect. -n, --no-reset Do not reset board on connection. The STLINKv2 device to use can be specified in the environment variable STLINK_DEVICE on the format <USB_BUS>:<USB_ADDR>. Then, in your project directory, someting like this... (remember, you need to run an _ARM_ gdb, not an x86 gdb) (重新打开一个终端,找到你编译好的应用程序的目录,就是存在elf文件的地方) $ arm-none-eabi-gdb fancyblink.elf (开启调试) ... (gdb) tar extended-remote :4242 (连上GDB服务) ... (gdb) load Loading section .text, size 0x458 lma 0x8000000 Loading section .data, size 0x8 lma 0x8000458 Start address 0x80001c1, load size 1120 Transfer rate: 1 KB/sec, 560 bytes/write. (gdb) ... (gdb) continue Have fun! Resetting the chip from GDB =========================== You may reset the chip using GDB if you want. You'll need to use `target extended-remote' command like in this session: (gdb) target extended-remote localhost:4242 Remote debugging using localhost:4242 0x080007a8 in _startup () (gdb) kill Kill the program being debugged? (y or n) y (gdb) run Starting program: /home/whitequark/ST/apps/bally/firmware.elf Remember that you can shorten the commands. `tar ext :4242' is good enough for GDB. Setting up udev rules ===================== For convenience, you may install udev rules file, 49-stlinkv*.rules, located in the root of repository. You will need to copy it to /etc/udev/rules.d, and then either reboot or execute $ udevadm control --reload-rules $ udevadm trigger Udev will now create a /dev/stlinkv2_XX or /dev/stlinkv1_XX file, with the appropriate permissions. This is currently all the device is for, (only one stlink of each version is supported at any time presently) Running programs from SRAM(在RAM上运行) ========================== You can run your firmware directly from SRAM if you want to. Just link it at 0x20000000 and do (gdb) load firmware.elf It will be loaded, and pc will be adjusted to point to start of the code, if it is linked correctly (i.e. ELF has correct entry point). Writing to flash(烧写Flash) ================ The GDB stub ships with a correct memory map, including the flash area. If you would link your executable to 0x08000000 and then do (gdb) load firmware.elf then it would be written to the memory. FAQ === Q: My breakpoints do not work at all or only work once. A: Optimizations can cause severe instruction reordering. For example, if you are doing something like `REG = 0x100;' in a loop, the code may be split into two parts: loading 0x100 into some intermediate register and moving that value to REG. When you set up a breakpoint, GDB will hook to the first instruction, which may be called only once if there are enough unused registers. In my experience, -O3 causes that frequently. Q: At some point I use GDB command `next', and it hangs. A: Sometimes when you will try to use GDB `next' command to skip a loop, it will use a rather inefficient single-stepping way of doing that. Set up a breakpoint manually in that case and do `continue'. Currently known working combinations of programmer and target ============================================================= STLink v1 (as found on the 32VL Discovery board) Known Working Targets: * STM32F100xx (Medium Density VL) * STM32F103 (according to jpa- on ##stm32) No information: * everything else! STLink v2 (as found on the 32L and F4 Discovery boards) Known Working Targets: * STM32F0Discovery (STM32F0 Discovery board) * STM32F100xx (Medium Density VL, as on the 32VL Discovery board) * STM32L1xx (STM32L Discovery board) * STM32F103VC, STM32F107RC, STM32L151RB, STM32F205RE and STM32F405RE on custom boards (https://github.com/UweBonnes/wiki_fuer_alex/layout/usps...) * STM32F303xx (STM32F3 Discovery board) * STM32F407xx (STM32F4 Discovery board) * STM32F429I-DISCO (STM32F4 Discovery board with LCD) * STM32F439VIT6 (discovery board reseated CPU) * STM32L151CB (custom board) * STM32L152RB (STM32L-Discovery board, custom board) STLink v2-1 (as found on the Nucleo boards) Known Working Targets: * STM32F401xx (STM32 Nucleo-F401RE board) Please report any and all known working combinations so I can update this!
按照上边步骤编译配置,就可以调试和下载应用程序。
相关文章推荐
- STM32F429-Discovery 使用stlink-1.2.0 在Linux下烧写调试RTEMS
- Ubuntu10.04系统调试TQ2440开发板之一《Ubuntu下搭建TQ2440的程序下载环境》
- Ubuntu下嵌入式开发环境搭建之使用MiniTools下载裸机程序
- ubuntu 配置使用adb安装调试程序
- Ubuntu下用minicom搭建TQ2440的程序下载dnw环境
- ubuntu 使用KindleFire调试Android程序
- ubuntu下使用魅族mx真机调试android程序
- Ubuntu 下使用Eclipse编译、调试嵌入式程序的方法(中)
- STM32F4 Discovery 使用MDK-ARM Debug Viewer调试没有打印信息的原因之一
- linux(Ubuntu)下安装Eclipse 使用CDT调试C/C++程序
- 使用supervivi+DNW下载MDK环境下2440裸机程序到SDRAM中运行
- 在ubuntu10.04成功移植gdbserver及gdbserver使用介绍(用于CCSV5.2远程调试ARM CORTEX-A8程序)
- Ubuntu下搭建TQ2440的程序下载环境
- Ubuntu笔记:系统使用,程序调试报错等
- 国嵌不用jlink那使用什么下载逻辑程序并单步调试的?& h-jtag原理,和jlink区别 & jlink为什么这么贵。
- ubuntu下使用eclipse调试jni无法获取环境变量,本地库(java.library.path,LD_LIBRARY_PATH)等问题的解决。
- Linux/Ubuntu 下使用USBasp下载程序(Atmel AVR or AT89S52 etc)
- 如何在linux环境下调试JAVA程序使用访问timesten:
- 在ubuntu 10.04中使用eclipse在真机上调试程序
- TI-Davinci开发系列之二使用CCS5.2TI Simulator模拟环境调试DSP程序