J-Link could start core error
Open
Nobody has claimed this yet.
probe/jlink
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
Sometimes the J-Link driver will report that it could not start the CPU core when pyocd disconnects.
Example error from running test/basic_test.py on a Nordic nRF5340-DK using the J-Link OB:
0011878:ERROR:jlink:Could not start CPU core. (ErrorCode: -1)
It's not clear what the cause of this is, whether it's a bug in pyocd (likely) or something in the target state.
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
Reproduce the error by running test/basic_test.py with a Nordic nRF5340-DK using the J-Link OB, then inspect the J-Link driver behavior when pyOCD disconnects. The cause is not identified in the issue, so done would require determining whether pyOCD or the target state causes the CPU-core start failure and documenting or fixing that cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100