Connect ST-Link debug probe and drop .elf/.out file. It parses the debug info into a tree of global/static variables with types and addresses. You can read/write addresses in the memory and watch them live in chart view. It can also flash .elf/.hex/.bin files.
I am considering to expand features such as; compiling, debugging, adding serial communication + RTT console, high rate frequency sampling for scope like visualization, shared workspaces, and firmware version management.
This is where I am kind of stuck and don't want to invest more of my time just to create web version of what STM already does with its own tool set.
How much of your day is spent in STM environment, and what would you move to a browser tool like this product? What is missing on this so you end up not visiting/using it anymore?
To be more spesific about how it actually works; a tiny app that runs Python server built on pyOCD, holds the probe and talks to mcuhex over localhost. Distributed binaries for Windows & MacOS are not signed, in case you want to avoid running unsigned binaries, this server can run from the console with Python these platforms including Linux. Application is just the compiled version of the mcuhex-sdk repository.
SDK: https://github.com/omrdk/mcuhex-sdk
It is completely free right now as it is in beta.
Happy to answer any questions and hear out your inputs. Thanks in advance.