X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=README;h=5ed9dbf31b89c2effe081d05e5c70d57d591a4f8;hb=5a8f637a5c1c19f73d987e5526236beeed7bf850;hp=58bd3ca2ae26236cd83c28fd9a38b13e19c93d26;hpb=24128597e1ec3fa8aa042aa80db8582d20a14bb6;p=fw%2Fstlink diff --git a/README b/README index 58bd3ca..5ed9dbf 100644 --- a/README +++ b/README @@ -1,15 +1,92 @@ HOWTO ===== -First, load the sg kernel module. -# modprobe sg - -To run the gdb server, do (you do not need sudo if you have set up -permissions correctly): -$ make -C build && sudo ./build/st-util 1234 /dev/sg1 - -Then, in gdb: -(gdb) target remote :1234 +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) +. pkg-config + +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 +~~~~~~~~~~~~~~~~~~~~~~~ + +You're ready to go :) + +COMPILING +~~~~~~~~~ +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 +~~~~~~~~~~~~~~~~~~~ +To run the gdb server: (you do not need sudo if you have set up +permissions correctly) + +$ 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 :. + +Then, in your project directory, someting like this... +(remember, you need to run an _ARM_ gdb, not an x86 gdb) + +$ arm-none-eabi-gdb fancyblink.elf +... +(gdb) tar extended-remote :4242 +... +(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! @@ -18,27 +95,29 @@ 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:1111 -Remote debugging using localhost:1111 +(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 :1111' is good enough +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, 10-stlink.rules, located +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/stlink file, which will point at appropriate -/dev/sgX device. Good to not accidentally start debugging your flash drive. +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 ========================== @@ -58,6 +137,7 @@ If you would link your executable to 0x08000000 and then do (gdb) load firmware.elf then it would be written to the memory. + FAQ === @@ -75,3 +155,40 @@ 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: +* STM32F030F4P6 (custom board) +* 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) +* STM32F030R8T6 (STM32 Nucleo-F030R8 board) +* STM32F072RBT6 (STM32 Nucleo-F072RB board) +* STM32F103RB (STM32 Nucleo-F103RB board) +* STM32F334R8 (STM32 Nucleo-F334R8 board) + +Please report any and all known working combinations so I can update this!