pyocd / pyocd/pyOCD

Standalone Flash executable

Open
#1,146 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi all,

Is there a way to generate a standalone binary for the flash portion of PyOCD? It looks like in the how_to_build.md there are instructions for building a standalone executable but I see that it is outdated, as the option for building the flash tool on its own has been removed.

We've adopted the DAP-Link project as our debugger/programmer of choice in our Engineering team and my use case is as follows: Our hardware engineers would like to be able to take a .hex file given to them and flash a target at their bench without requiring too much setup (This is mostly a severe allergic reaction to having to open a CL 🙄). The same goes for our clients who are not as technically adept, but would like to be able to update their devices without sending them back to our office.

I would like to create a GUI application that will build the latest PyOCD Flash tool and package it along side our application. (Think J-Flash for the J-Link suite of tools). That way we can send a DAP-Link probe, Installer/Executable and their new Firmware and the end user is able to update without too much hassle.

Is this an existing feature or is it a potential new feature that could be added (again)?

Thanks!

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

Start with docs/how_to_build.md and inspect the current standalone executable instructions, especially the removed option for building the flash tool independently. Clarify whether standalone flash packaging is still supported, then define completion around an agreed build path and corresponding documentation for producing the requested executable.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, cli
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.