X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=README;h=bb06f60a96bf236dd3b3364271d6034d7b3639e1;hb=e919d94870667af422a8116b3f3a0fd0ffe16742;hp=28caaf87822977e0ea611ed918f9017a7c185838;hpb=8542b23c6e899fbb0ecc7f6de27eed8133988003;p=fw%2Fstlink diff --git a/README b/README index 28caaf8..bb06f60 100644 --- a/README +++ b/README @@ -1,11 +1,3 @@ -IMPORTANT SHORT TERM NOTICE: -If you are targetting F1 devices, with either stlinkv1 or v2 hardware, you -_need_ to use karlp's libwork2 branch. - -If you are targetting F4, you _need_ to use texane's master - -If you are targetting F2 or L1, please let us know how it goes! - HOWTO ===== @@ -22,8 +14,9 @@ called stlink and there are 2 versions: Common requirements ~~~~~~~~~~~~~~~~~~~ -libusb-1.0 (You probably already have this, but you'll need the +. libusb-1.0 (You probably already have this, but you'll need the development version to compile) +. pkg-config IF YOU HAVE AN STLINKv1 ~~~~~~~~~~~~~~~~~~~~~~~ @@ -110,6 +103,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 === @@ -127,3 +121,26 @@ 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: +* STM32F100xx (Medium Density VL, as on the 32VL Discovery board) +* STM32L1xx (STM32L Discovery board) +* STM32F107RC, STM32L151RB, STM32F205RE and STM32F405RE on a custom boards + (https://github.com/UweBonnes/wiki_fuer_alex/layout/usps...) +* STM32F407xx (STM32F4 Discovery board) + +Please report any and all known working combinations so I can update this! +