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

Open issues for planned features? #1

Closed
fmckeogh opened this issue Mar 12, 2019 · 2 comments
Closed

Open issues for planned features? #1

fmckeogh opened this issue Mar 12, 2019 · 2 comments

Comments

@fmckeogh
Copy link
Contributor

I’d like to contribute but don’t really know what needs doing, I don’t suppose you could open some issues for missing features/bug fixes?

@Yatekii
Copy link
Member

Yatekii commented Mar 13, 2019

Cool that you want to contribute!

At the moment we are basically reading and implementing the ADI v5.2 spec.
We are experimenting with what works best and what path we want to follow.
There is a lot of things (API related) that are not optimal yet and need improvements.
Basically what works is basic reading of memory locations (ROM and RAM).
Writing RAM works; not so much for ROM tho. ROM is a bit tricky, as it is different for each and every chip.
Also, we have not ventured into debug capabilities like setting breakpoints, halting, stepping, etc.
If you have something specific you would like to implement or you have general suggestions on the code, you are very welcome to just drop a PR. If you wanna make sure it's OK beforehand, just ask real quick on that specific thing. But we basically accept any reasonable contribution as we are still at the very beginning.

@therealprof has a an also very basic implementation of a REPL, where he tries out the ergonomics of the probe-rs API and we reiterate if it sucks. You can have a look here: https://github.com/therealprof/probemeister

edit: I for example am working on reworking, how we do device enummeration. Up until now, we basically only supported the STLink in basic fashion. But more probe support means more folks and also, @therealprof would rather use a DAPLink and has an implementation for that in the makings. So we need to generalize probe discovery.
Before I worked on target discovery via ROMtables, but there seems to be some issue related to the STLink, so I put this on halt for now.
Just to give you a general idea what we are working on atm.

You can also find us on mozilla#rust-embedded if you want to chat. Hope to find you there soon; otherwise GH issues is ok too ;)

@Yatekii
Copy link
Member

Yatekii commented May 21, 2019

Ok, so we made huge progress and can now fully read ROM tables with a DAPlink.
We also have preliminary support for DebugPort features.
Furthermore I am close to properly flashing a ROM image into the flash =)

So if you still got too much time and interest, feel free to pick one of the v 0.1.0 milestone issues :)

As usual, questions can be asked on GH or IRC.

@Yatekii Yatekii closed this as completed Oct 7, 2019
evanrichter referenced this issue in evanrichter/probe-rs Jul 19, 2020
remove possible runtime panics from riscv code. addresses probe-rs#190
bors bot pushed a commit that referenced this issue Jan 4, 2021
bors bot pushed a commit that referenced this issue Feb 15, 2021
bors bot pushed a commit that referenced this issue Mar 1, 2021
Tiwalun pushed a commit that referenced this issue Jan 13, 2023
Tiwalun pushed a commit that referenced this issue Jan 13, 2023
Update the README to include `libudev-dev`
Yatekii added a commit that referenced this issue Jan 13, 2023
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

2 participants