Registering a new target
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
I've defined a new (CoreSightTarget subclass) target and successfully tested it by following the instructions in adding_new_targets.md to add it to the list of builtin targets
Is there a way to import the new target source file without changing the contents of pyocd/target/builtin?
It would be nice if I could just point to this new file in the pyocd.yaml file in a similar way you can point to a CMSIS pack
e.g.
target:
- <path_to>/target_<device>.py
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 adding_new_targets.md and the pyocd.yaml target configuration, then inspect how target files under pyocd/target/builtin are registered. Done means a user can point pyocd.yaml at an external CoreSightTarget source file without modifying the builtin-target directory, with the behavior covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100