Ryan Summers

I have to agree with @hargoniX on this - when we force device driver crates to conform to some strictly defined interface, it can make it hard to adopt. For...

@isundaylee In your first point, you mention that the data isn't set on the wire because the computer hasn't opened the serial port, but this depends on what is implementing...

Just to add to this discussion - we're working on an MQTT implementation on top of smoltcp which uses a TCP socket as the underlying transport mechanism. From our point...

@dnadlinger From a higher-level perspective, this means the layer _above_ the TCP socket then has to keep state about the half-a-packet it sent (if the high-level protocol doesn't support invalid...

@huming2207 You can use cargo-embed with GDB enabled to flash the device and automatically load the ELF into GDB when you start it up. While the GDB stub doesn't load...

> Unfortunately `arm-none-eabi-gdb` shipped by Arm doesn't support Python, which means you can't even use the Python extensions without swapping to a different gdb build. I've been using `gdb-multiarch` from...

I found this issue after some confusion when `writeln!(uart, "Hello World")` worked fine to print over the UART, but `uart.write("Hello World");` seemed to spew out garbage (although both functions seemed...

I believe I may be able to clarify the issue a bit here. The problem appears to arise on Windows agents, but not on *nix agents. Example pipeline ``` pipeline...

Using `\\` as the path separator in the pipeline does not make the problem go away on a Windows agent. I can reliably upload using the above pipeline on Linux,...

Perhaps the windows vs. *nix agents upload is a different issue then.