Mathias Brossard
Mathias Brossard
Try with another probe, check your connections, check that the target is powered on. "No ACK Received" and "DP IDCODE read failed" are errors I typically see when the probe...
Some of the changes mentioned by @gbryant-arm are in #367.
I merged https://gitlab.com/arm-research/security/icecap/icecap/-/merge_requests/22 and rebased this PR.
You don't need to add commits to re-run CI, you can restart the failing jobs in "Actions".
> > You don't need to add commits to re-run CI, you can restart the failing jobs in "Actions". > > Unfortunately this clobbers the log and hides the old...
> It should be noted we're still seeing unknown CI failures in IceCap, but this PR at least fixes some of the known reasons. More fixes can always come later....
bad3596 can be dealt separately in #416. But I don't want to assume it is the only contributor to CI instability. As @geky pointed out f5087dc (now 66d5d48) failed in...
As @nspin implies, I was also going to suggest moving all crates into a `crates/` sub-directory after the next release. As far as my workspace-related work is concerned there hasn't...
Yes #312, but also #306.
The `http` part of `io-utils` is only used by `veracruz-server`, so with some refactoring, the runtime workspaces should not require `reqwest` (et al.).