Default USB Interface backend

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
embedded-iot

Research direction

Start by reviewing pull request #1156 and the USB backend reports in issues #1032 and #1144, with the release discussion in issue #1155 for context. Done means the proposed default pyusb fallback behavior is agreed and the remaining commented-out raise or warning handling is resolved.

Written by the indexing model from the issue text.

Description

Hey @flit :-)

I have noticed that a lot of internals changed, also the USB backend handling, we can discuss proposed major release number bump here https://github.com/pyocd/pyOCD/issues/1155.

The initial problem report on USB backend problems were repoted here: https://github.com/pyocd/pyOCD/issues/1032, https://github.com/pyocd/pyOCD/issues/1144.

I have added BSD detection support here https://github.com/pyocd/pyOCD/pull/1153 and modified default error message here https://github.com/pyocd/pyOCD/pull/1154.

I would like to propose pyusb as the default fallback on platforms that are not on the list. That should bring support to USB Interfaces on "unknown" platforms with a backend that is known to be most versatile and platform independent. If pyusb is not present or cannot be used on an unknown platform we will know that directly.

My proposition can be found here https://github.com/pyocd/pyOCD/pull/1156 and is open to discussion :-) We have to remove commented out raise line and maybe replace it with some sort of warning instead :-)

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.