Is there a RISC-V port of pyOCD? #1224
-
Is anybody working on or aware of a riscv port of pyOCD? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
+1 question/request |
Beta Was this translation helpful? Give feedback.
-
Would be nice to have but I guess we need to make that happen :-) |
Beta Was this translation helpful? Give feedback.
-
There is not. At the moment pyocd only supports Arm M-profile cores and CoreSight based devices. (A-profile and maybe R-profile cores will come at some point, although nobody's really asking for it.) You're welcome to submit changes to support RISC-V! Now that pyocd is an independent project (as of Sep 2020) and not owned by Arm, we can support other architectures. I won't and can't implement it myself, because I'm Arm employee and that would violate my employment contract (competing interests). However, I will be happy to work on structural changes and provide guidance and recommendations for others. (And to be clear, I'd like to see it happen.) Be aware that the current pyocd design needs to be changed to support multiple architectures. In the background, I've actually been planning how a multi-architecture pyocd design would look, and the changes will be made (most of these changes are also needed for A-profile), but it's still quite a ways off. Another thing to keep in mind is that any additions need to be well supported with a maintainer (can't be me, for above reasons) and follow the pyocd design principles of being (or attempting to be 😉) easy to use while supporting a wide range of devices, and taking advantage of the RISC-V ecosystem. |
Beta Was this translation helpful? Give feedback.
There is not. At the moment pyocd only supports Arm M-profile cores and CoreSight based devices. (A-profile and maybe R-profile cores will come at some point, although nobody's really asking for it.)
You're welcome to submit changes to support RISC-V! Now that pyocd is an independent project (as of Sep 2020) and not owned by Arm, we can support other architectures. I won't and can't implement it myself, because I'm Arm employee and that would violate my employment contract (competing interests). However, I will be happy to work on structural changes and provide guidance and recommendations for others. (And to be clear, I'd like to see it happen.)
Be aware that the current pyocd design nee…