Skip to content
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

Pack targets should be preferred over builtin targets when targets of the same name exist in both #1727

Open
yiding opened this issue Oct 3, 2024 · 0 comments

Comments

@yiding
Copy link

yiding commented Oct 3, 2024

Right now, if there's a builtin target that matches the requested target, it is used over any pack targets. This is undesirable as pack targets may provide more functionality than builtin targets (such as having peripherals).

Specifically, I'm concerned with RP2040 target. There's a vendor published pack with contains peripheral SVDs for all the peripherals, which is very convenient when debugging and looking and peripheral registers, e.g. with 'monitor rr ...'.

Both the pack and the builtin registers targets under the name rp2040.

I think pyocd should, when a pack with the same target name as a builtin target is installed, prefer the pack target. The code right now only attempts to load target from a pack if there's no existing target in the list (which initially contains builtin targets).

I'm willing to make the necessary changes if we can nail down the behavior we want to have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant