-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transfer Out #3
Comments
I am glad you are up-to-date. Yes, we do option one. How do you want me to proceed? I don't think we can transfer the repo to mcu-debug via github. Should I clone this repo and create a new repo with it under mcu-debug? I will of course add you as a developer. Also, how do I test this extension in a browser? We have 3-4 issues at cortex-debug that I don't want to fix over there. |
If you are an owner of
Great, I can then update the IDs/etc.
What hardware do you have? I can create an example for usage with the Arm Embedded Debugger which works in the browser. |
Yes, I am the owner. Let me know what I need to do on my end. I will probably be notified by Github?
I have an ST F429 Nucleo board that I use for most tests. I also have some Infineon PSoC6 boards (can't remember the exact one) Btw, I want to make Cortex Debug to also work in the Browser but since we launch external programs, not sure it is feasible. I think Arm tools use something like WebUSB |
FYI: I am in the middle of adding a major feature. It is about to go into Preview (Pre-release) mode in the Marketplace. Probably by this weekend. I also have some very large amounts of refactoring to do and things can go a bit unstable. During that time, I will remove the SVD support once the mcu-debug SVD Viewer extension is alive on the marketplace. I plan on making several Preview releases 1.7.x As you know odd numbered minor releases (I have to tag them) are considered Preview by the marketplace and will not be installed unless users subscribe to them. This is how I do Betas I don't see any conflicts with SVD code and most of my changes are in the adapter backend and just one new file in the front-end. |
OK, I'll see what I can craft...
The trouble will be GDB. I've seen examples of running this in a browser, but requires a mini linux runtime to be compiled and deployed adding a lot of overhead.
We do |
An example for the F429 can be seen here: https://github.com/thegecko/f429-example |
Transfer initiated, you should get a notification in GitHub. Once transferred, I'll set up the new package ID ( |
I've been waiting and still have not seen an invite in my mailbox. Where should I be looking. Nothing in Trash or Spam either. |
I believe you see a banner in GitHub |
Just checked and the transfer expires after a day. Tried again and it said I need to have permission to create a repo under the mcu-debug org to make the transfer |
I just cloned your repo and changed the origin. Not quite what I wanted. This does not bring any GitHub settings you may had for this repo |
With reference to Marus/cortex-debug#736 this extension has now been rebased on the original codebase as of Marus/cortex-debug@056c03f
This means all existing SVD functionality to date has been captured including:
cortex-debug
is installed).Note: this support won't work with other debuggers until the support packs switch to a more generic activation event (e.g.
onDebug
), they currently only register whencortex-debug
activates.All previous additions (and some new functionality) have been preserved:
readMemory
andwriteMemory
DAP commands and activating for any debug session)Support for the generic debug tracker was tried over in #4, but does not work due to the tracker not working in a browser environment. The overhead of a separate package and/or extension outweighs a simple VS Code pub/sub tracker IMO.Support for the debug-tracker extension (if installed) has been added in #6
This Cortex-Debug Organisation was created as a temporary home for extracting and managing this extension and the extension should ideally be transferred out.
I'm keen to continue to maintain the extension and see two options for a new home:
This option aligns with other extensions being extracted from
cortex-debug
There is interest from Eclipse, companies in the Embedded Special Interest Group and the CDT Cloud Project leads to support this, which may be a better maintenance option with more resourcing.
The text was updated successfully, but these errors were encountered: