kopia lustrzana https://github.com/stlink-org/stlink
General Project Update
- [doc] Updated list of supported devices - [doc] verify udev-rules (Closes #764) - Removed old issue-templates. - Updated BSD-3 license file.pull/913/head
nightwalker-87
rodzic
afd7f5b8d0
commit
d3c11fbef6
|
|
@ -1,32 +0,0 @@
|
|||
# Bug Report
|
||||
|
||||
Thank you for giving feedback to the stlink project.
|
||||
|
||||
In order to allow developers and other contributors to isolate and target your respective issue, please take some time to fill out the check boxes below by setting a 'x' into the checkboxes ( [x] ) and edit each item appropriate to your specific problem.
|
||||
|
||||
- [ ] Programmer/board type: e.g Stlink/v1, Stlink/v2, Stlink/v2-onboard
|
||||
- [ ] Programmer firmware version: e.g STSW-LINK007 2.27.15
|
||||
- [ ] Operating system: e.g Linux, Mac OS X, Windows (with specific version)
|
||||
- [ ] Stlink tools version and/or git commit hash: e.g v1.1.0/git-c722056
|
||||
- [ ] Stlink commandline tool name: e.g `st-info`, `st-flash`, `st-util`
|
||||
- [ ] Target chip (and optional board): e.g STM32F402VG (STM32Fxxx Discovery)
|
||||
|
||||
Futher we kindly ask you to describe the detected problem as detailled as possible and to add debug output if available, by using the following template:
|
||||
|
||||
Commandline-Output:
|
||||
|
||||
```
|
||||
OUTPUT/ERROR of the commandline tool(s)
|
||||
```
|
||||
|
||||
Expected/description:
|
||||
|
||||
`short description of the expected value`
|
||||
|
||||
|
||||
**NOTICE: The bug report may be closed without notice when not enough information is provided!**
|
||||
|
||||
|
||||
Thank you for your support.
|
||||
|
||||
The stlink project maintainers
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
# Feature Request
|
||||
|
||||
Thank you for giving feedback to the stlink project.
|
||||
|
||||
In order to allow developers and other contributors to isolate and target your respective issue, please take some time to fill out the check boxes below by setting a 'x' into the checkboxes ( [x] ) and edit each item appropriate to your specific problem.
|
||||
|
||||
- [ ] Programmer/board type: e.g Stlink/v1, Stlink/v2, Stlink/v2-onboard
|
||||
- [ ] Programmer firmware version: e.g STSW-LINK007 2.27.15
|
||||
- [ ] Operating system: e.g Linux, Mac OS X, Windows (with specific version)
|
||||
- [ ] Stlink tools version and/or git commit hash: e.g v1.1.0/git-c722056
|
||||
- [ ] Stlink commandline tool name: e.g `st-info`, `st-flash`, `st-util`
|
||||
- [ ] Target chip (and optional board): e.g STM32F402VG (STM32Fxxx Discovery)
|
||||
|
||||
Futher we kindly ask you to describe the detected problem as detailled as possible and to add debug output if available, by using the following template:
|
||||
|
||||
Commandline-Output:
|
||||
|
||||
```
|
||||
OUTPUT/ERROR of the commandline tool(s)
|
||||
```
|
||||
|
||||
Expected/description:
|
||||
|
||||
`short description of the expected value`
|
||||
|
||||
|
||||
**NOTICE: This feature request may be closed without notice when not enough information is provided!**
|
||||
|
||||
|
||||
Thank you for your support.
|
||||
|
||||
The stlink project maintainers
|
||||
|
|
@ -1,32 +0,0 @@
|
|||
# Support question
|
||||
|
||||
Thank you for giving feedback to the stlink project.
|
||||
|
||||
In order to allow developers and other contributors to help you with your question, please take some time to fill out the check boxes below by setting a 'x' into the checkboxes ( [x] ) and edit each item appropriate to your specific problem.
|
||||
|
||||
- [ ] Programmer/board type: e.g Stlink/v1, Stlink/v2, Stlink/v2-onboard
|
||||
- [ ] Programmer firmware version: e.g STSW-LINK007 2.27.15
|
||||
- [ ] Operating system: e.g Linux, Mac OS X, Windows (with specific version)
|
||||
- [ ] Stlink tools version and/or git commit hash: e.g v1.1.0/git-c722056
|
||||
- [ ] Stlink commandline tool name: e.g `st-info`, `st-flash`, `st-util`
|
||||
- [ ] Target chip (and optional board): e.g STM32F402VG (STM32Fxxx Discovery)
|
||||
|
||||
Futher we kindly ask you to describe the detected problem as detailled as possible and to add debug output if available, by using the following template:
|
||||
|
||||
Commandline-Output:
|
||||
|
||||
```
|
||||
OUTPUT/ERROR of the commandline tool(s)
|
||||
```
|
||||
|
||||
Expected/description:
|
||||
|
||||
`short description of the expected value`
|
||||
|
||||
|
||||
**NOTICE: This support question may be closed without notice when not enough information is provided!**
|
||||
|
||||
|
||||
Thank you for your support.
|
||||
|
||||
The stlink project maintainers
|
||||
48
LICENSE.md
48
LICENSE.md
|
|
@ -1,29 +1,29 @@
|
|||
Copyright (c) 2011 The stlink project (github.com/texane/stlink) contributors.
|
||||
All rights reserved.
|
||||
Copyright (c) 2011 The "Capt'ns Missing Link" Authors. All rights reserved.
|
||||
BSD 3-Clause License
|
||||
|
||||
Copyright (c) 2020, The stlink project (github.com/texane/stlink) & "Capt'ns Missing Link" authors.
|
||||
All rights reserved.
|
||||
|
||||
Redistribution and use in source and binary forms, with or without
|
||||
modification, are permitted provided that the following conditions are
|
||||
met:
|
||||
modification, are permitted provided that the following conditions are met:
|
||||
|
||||
* Redistributions of source code must retain the above copyright
|
||||
notice, this list of conditions and the following disclaimer.
|
||||
* Redistributions in binary form must reproduce the above
|
||||
copyright notice, this list of conditions and the following
|
||||
disclaimer in the documentation and/or other materials provided
|
||||
with the distribution.
|
||||
* Neither the name of Martin Capitanio nor the names of its
|
||||
contributors may be used to endorse or promote products derived
|
||||
from this software without specific prior written permission.
|
||||
1. Redistributions of source code must retain the above copyright notice, this
|
||||
list of conditions and the following disclaimer.
|
||||
|
||||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
||||
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
||||
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
||||
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
||||
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
||||
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
||||
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
||||
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
||||
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
||||
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
||||
2. Redistributions in binary form must reproduce the above copyright notice,
|
||||
this list of conditions and the following disclaimer in the documentation
|
||||
and/or other materials provided with the distribution.
|
||||
|
||||
3. Neither the name of the copyright holder nor the names of its
|
||||
contributors may be used to endorse or promote products derived from
|
||||
this software without specific prior written permission.
|
||||
|
||||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
|
||||
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
|
||||
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
|
||||
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
|
||||
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
|
||||
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
|
||||
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
||||
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
|
|
|
|||
|
|
@ -243,6 +243,7 @@ Tested boards [incl. STLink programmers]:
|
|||
| 0x471 | STM32L4**Q5**xx |
|
||||
|
||||
Tested boards [incl. STLink programmers]:
|
||||
* Nucleo-L432KC [v2-1]
|
||||
* Nucleo-L452RE [v2-1]
|
||||
* Nucleo-L476RG [v2-1]
|
||||
* Nucleo-L496ZG [v2-1]
|
||||
|
|
|
|||
|
|
@ -170,6 +170,55 @@ Upon reset, the board LEDs should be blinking.
|
|||
|
||||
HOWTO
|
||||
=====
|
||||
|
||||
## Verify if udev rules are set correctly (by Dave Hylands)
|
||||
|
||||
To investigate, start by plugging your STLINK device into the usb port. Then run lsusb. You should see an entry something like the following:
|
||||
|
||||
```
|
||||
Bus 005 Device 017: ID 0483:374b STMicroelectronics ST-LINK/V2.1 (Nucleo-F103RB)
|
||||
```
|
||||
|
||||
Note the bus number (005) and the Device (017). You should then do:
|
||||
`ls -l /dev/bus/usb/005/017` (replacing 005 and 017 appropriately).
|
||||
|
||||
On my system I see the following:
|
||||
|
||||
```
|
||||
crw-rw-rw- 1 root root 189, 528 Jan 24 17:52 /dev/bus/usb/005/017
|
||||
```
|
||||
|
||||
which is world writable (this is from the MODE:="0666" below). I have several files in my `/etc/udev/rules.d` directory. In this particular case, the `49-stlinkv2-1.rules` file contains the following:
|
||||
|
||||
```
|
||||
# stm32 nucleo boards, with onboard st/linkv2-1
|
||||
# ie, STM32F0, STM32F4.
|
||||
# STM32VL has st/linkv1, which is quite different
|
||||
|
||||
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374b", \
|
||||
MODE:="0666", \
|
||||
SYMLINK+="stlinkv2-1_%n"
|
||||
|
||||
# If you share your linux system with other users, or just don't like the
|
||||
# idea of write permission for everybody, you can replace MODE:="0666" with
|
||||
# OWNER:="yourusername" to create the device owned by you, or with
|
||||
# GROUP:="somegroupname" and mange access using standard unix groups.
|
||||
```
|
||||
|
||||
and the idVendor of 0483 and idProduct of 374b matches the vendor id from the lsusb output.
|
||||
|
||||
Make sure that you have all 3 files from here: https://github.com/texane/stlink/tree/master/etc/udev/rules.d in your `/etc/udev/rules.d` directory. After copying new files or editing excisting files in `/etc/udev/ruled.d` you should run the following:
|
||||
|
||||
```
|
||||
sudo udevadm control --reload-rules
|
||||
sudo udevadm trigger
|
||||
```
|
||||
|
||||
to ensure that the rules actually take effect. Using the trigger command means that you shouldn't need to unplug and replug the device, but you might want to try that for good measure as well.
|
||||
|
||||
If the VID:PID of your device doesn't match those in any of the 3 files, then you may need to create a custom rule file to match your VID:PID.
|
||||
|
||||
|
||||
## Using the gdb server
|
||||
|
||||
To run the gdb server:
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue