You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the socket feature does not work properly when setting up a RTT channel in the BinaryLE format. According to wireshark, it does not even attempt to establish a connection. The String format works fine.
Also, for me the cargo-embed console display of BinaryLE RTT data is not line wrapped. For reference, I am sending 8 byte messages in one call to the rtt_target UpChannel.
To Reproduce
Steps to reproduce the behavior:
Configure UpChannel 1 with NoBlockSkip on both ends, and set socket to localhost + some port, then listen on it with e.g. netcat.
2.) Run cargo-embed in a project that sends 8byte messages as rtt data on channel 1.
Expected behavior
You will see that there is no attempt at connecting the socket. Also the cargo-embed interface for channel 1 will not line-wrap the binary data.
Desktop (please complete the following)
OS: Linux (Arch)
Target: RPI Pico (RP2040)
Debugger: Raspberry PI debug probe
probe-rs version: master (0.23)
The text was updated successfully, but these errors were encountered:
Describe the bug
It seems like the socket feature does not work properly when setting up a RTT channel in the BinaryLE format. According to wireshark, it does not even attempt to establish a connection. The String format works fine.
Also, for me the cargo-embed console display of BinaryLE RTT data is not line wrapped. For reference, I am sending 8 byte messages in one call to the rtt_target UpChannel.
To Reproduce
Steps to reproduce the behavior:
2.) Run cargo-embed in a project that sends 8byte messages as rtt data on channel 1.
Expected behavior
You will see that there is no attempt at connecting the socket. Also the cargo-embed interface for channel 1 will not line-wrap the binary data.
Desktop (please complete the following)
The text was updated successfully, but these errors were encountered: