pyocd / pyocd/pyOCD

From Pack to built-in targets

Open
#983 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Can PyOCD now generate built-in targets in a. Pack file?(Extract the algorithm from the.pack to make the target built-in)。

The advantage is that pyocd can be small enough when I want to package it as an exe; a .pack file is just too big。

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.

Research direction

The issue names no files or tests. Start by tracing how pyOCD reads a .pack file and creates targets, then determine how the algorithm could produce built-in targets instead. Done means supported targets work without the large .pack file and packaging pyOCD as an executable is smaller.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.