Piers Finlayson

I am hitting a very similar error message with probe-rs 0.30.0, in my application: ``` thread 'tokio-runtime-worker' (28908) panicked at /home/pdf/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/probe-rs-0.30.0/src/architecture/arm/communication_interface.rs:472:18: internal error: entered unreachable code: Did not expect to...

I have worked around this by replacing the panic with _ => return Err( ArmError::Other( format!("Unexpected AP / DP combination {}/{}", ap.ap(), dp_state.debug_port_version) ) ), Arm(Other("Unexpected AP / DP combination...

I have just hit this issue. The docs for 0.15.1 of fuser state: AutoUnmount Automatically unmount when the mounting process exits AutoUnmount requires AllowOther or AllowRoot. If AutoUnmount is set...

To add to this issue, I hit essentially the same symptoms when trying to compile a binary called "async.rs". I figured out the problem due to this issue. For example...

@kevinmehall Thanks for the input. Are you're planning a CreateThreadpoolTimer version and do you have a rough ETA on that? Need to decide what to do with my dependent crate...

It's currently hardcoded - need to allow this to be configurable so otb-iot can report values with simple algorithms applied.

In otbiot designs: - GPIO0 up - GPIO2 up - GPIO4 up - GPIO5 up - GPIO12 up - GPIO13 up - GPIO14 up - GPIO15 down - GPIO16 up

Wemos D1 mini: - GPIO0 up - GPIO2 up - GPIO4 floating - GPIO5 floating - GPIO12 floating - GPIO13 floating - GPIO14 floating - GPIO15 down - GPIO16 floating

Therefore we can set the GPIOs per the otbiot designs.

Note some of these will be overridden when a pin is used for a specific purpose. On otbiot boards this is: - 0/2 (internal I2C bus) - 14 (soft reset)...