pyocd cannot connect to target with pre-reset, but MDK can do

Open
#1,494 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
embedded-iot

Research direction

Start by reproducing the connection failure on the LPC860 with pyOCD 0.34.3 on Windows 10, using the reported pre-reset option, and compare the result with the MDK pre-reset behavior. Done means pyOCD connects to the sleeping target and discovers its cores instead of reporting "No cores discovered".

Written by the indexing model from the issue text.

Description

Our device LPC860 entered sleep mode.
Normally pyocd cannot connect to target and report error No cores discovered.

If adding option -M pre-reset, pyocd still cannot connect to device.
But MDK can do with pre-reset settings.

image

pyocd: 0.34.3
Windows 10 platform

Dominant language
Python
Stars
1.5k
Forks
560
Avg merge
1h 41m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pyocd/pyOCD

All issues in pyocd/pyOCD

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.