Debug Probe Selection via Config File
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
When multiple debug probes are connected, one has to select the probe to use for every command invocation, as described in the docs section Selecting the debug probe: either enter the probe number interactively, or specify the UID via a command line flag --uuid=UID/--probe=UID.
Is it possible to specify the probe to use via a key in the pyocd.yaml config file? I'd imagine something like this:
target_override: stm32g491cetx
probe: 002F00325553500820393256
If this should not be possible possible yet, I'd be happy to implement it, if someone could point me in the right direction 😃
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the documented “Selecting the debug probe” section and the existing --uuid/--probe command-line options. Inspect how pyocd.yaml settings are loaded and how probe selection is passed to commands. Done means a probe UID can be specified in pyocd.yaml and is used when multiple probes are connected, with the command-line behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, embedded-iot
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100