1.5 KiB
| name | about | title | labels |
|---|---|---|---|
| Feature Request | Suggest an idea for this project | [feature] $YourTitle | code/feature-request |
Thank you for giving feedback to the stlink project.
NOTE: In order to offer sufficient and the best possible support, please read /CONTRIBUTING.md and follow the given instructions before submitting a ticket.
Bug reports and/or feature requests will be deleted, if they violate our contribution guidelines and if no issue-template is used! Thank you for your support.
- I made serious effort to avoid creating duplicate or nearly similar issue
In order to allow developers to isolate and target your respective issue, please take some time to select the check boxes below and fill out each of the following items appropriate to your specific request.
- Programmer/board type: [enter here] (e.g STLINK /V1, /V2, /V2-onboard, /V2-clone, /V3)
- Operating system an version: [enter here] (e.g Linux, macOS, Windows)
- stlink tools version and/or git commit hash: [enter here] (e.g v1.6.1/git-d0416149)
- stlink commandline tool name: [enter here] (e.g
st-info,st-flash,st-trace,st-util) - Target chip (and board, if applicable): [enter here] (e.g STM32F103C8T6 (NUCLEO-F103RB))
Further we kindly ask you to describe the detected problem as detailed 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