<ksvr[m]>
Anyone has experience with the probe-rs rustyprobe hardware?
<ksvr[m]>
I am looking for a debug probe without breaking the bank, looks like a solid option ??
xnor has quit [Ping timeout: 240 seconds]
xnor has joined #rust-embedded
thejpster[m] has joined #rust-embedded
<thejpster[m]>
I have one, it's nice
<thejpster[m]>
but price wise nothing beats a Raspberry Pi Pico with a couple of jumper wires
<dngrs[m]>
The st-link clone shade
M9names[m] has joined #rust-embedded
<M9names[m]>
i like my probes to work with all targets.
<M9names[m]>
for price/perf i think mcu-link is the best value but the form factor isn't great, you'll need a breakout to use anything that doesn't have a 10-pin arm connector, and it requires the target to provide Vtarg to power it's buffers.
<M9names[m]>
the muse-lab HS stuff isn't bad (once you rebuild/reflash daplink to use HS)
<M9names[m]>
the st-link clones aren't very fast if you aren't running st-link firmware
SosthneGudon[m] has joined #rust-embedded
<SosthneGudon[m]>
<adamgreig[m]> If they're interested the usual process would be to volunteer to join the libs team to help maintain it
<SosthneGudon[m]>
I've mainly been keeping an eye on new PR to be able to ensure that my existing open PRs are kept up to date and hopefully get a 0.9.1 out at some point but if the crate needs help in maintainance I could help yes.
<dngrs[m]>
<M9names[m]> the st-link clones aren't very fast if you aren't running st-link firmware
<dngrs[m]>
they're generally not very good but I find them acceptable, the most annoying part is indeed that they don't work with e.g. the rp2040. I have flashed a DAP probe firmware onto a usb-c pill for that as I never managed to get rp2040 based probe firmware to work, for whatever reason (maybe I just very consistently messed up the wiring? can't rule it out 😬)
<M9names[m]>
could also have cooked one of the IO pins? rp2040 pads aren't as robust as they old stm32f1's
<dngrs[m]>
possible, yeah, I think that happened in at least one case
<M9names[m]>
thejpster did one in, i have done it too. plenty of other pins to choose from on a pico though, so it's not so critical
<zeenix[m]>
<SosthneGudon[m]> I've mainly been keeping an eye on new PR to be able to ensure that my existing open PRs are kept up to date and hopefully get a 0.9.1 out at some point but if the crate needs help in maintainance I could help yes.
<zeenix[m]>
Awesome! adamgreig: could you kindly point Sosthène Guédon to docs on how to volunteer to join the libs team?
<zeenix[m]>
I would volunteer myself too but i really don't have sufficient contributions in
<dirbaio[m]>
if you want to see progress happen the best way is to volunteer
<dirbaio[m]>
there's no minimum amount of contributions required
<dirbaio[m]>
* better than pushing others to volunteer :P
<dirbaio[m]>
there's no minimum amount of contributions required
<Ralph[m]>
dirbaio[m]: can i volunteer to push others? 😝
<zeenix[m]>
dirbaio: you mean anyone can just get maintenance rights just by volunteering?
<dirbaio[m]>
I mean, if it's someone who just came out of the shadows with no history the answer would probably be "who are you lol"
<dirbaio[m]>
but it's not your case
<zeenix[m]>
I did what I could, that didn't require maintainer rights and Sosthène Guédon too. Just that things like releases can't happen without maintainers
<dirbaio[m]>
and even if you're a team member, your PRs need approval from another team member
<zeenix[m]>
Right, I guess both I and Sosthène Guédon should both apply and then we can help eachother out
<zeenix[m]>
dirbaio: I might be misreading but I don't see an email address for libs team on the WG page
<zeenix[m]>
I guess we just create an issue or PR on the repo?
<thejpster[m]>
You open an RFC on the wg repo, once you’re pretty sure the existing team members are likely to say yes.