Hello, I noticed that there is a conflict in the remote bitbang protocol.
Consider the commands "SWD write 0 0" and "Sleep for 1 microsecond".
Both use the 'd' character. I am pretty sure this is an error, question
is, what should we replace it with?
Marek Vrbka
I did some investigation on the CH32V series. It seems that they have their own
custom protocol completely unrelated to ARM SWD. I have seen it referred to as
RVSWD. To complicate things even further, their CH32V003 uses a different
single transport protocol.
---
**[tickets:#378] SWD support
---
**[tickets:#414] Semihosting message redirection TCP server gets the input data
flushed before it can be used**
**Status:** new
**Milestone:** 0.11.0
**Labels:** semihosting
**Created:** Wed Sep 06, 2023 03:38 PM UTC by Marek Vrbka
**Last Updated:** Wed Sep 06, 2023 03:38 PM UTC
**Owner
**Labels:** semihosting
**Created:** Wed Sep 06, 2023 03:38 PM UTC by Marek Vrbka
**Last Updated:** Wed Sep 06, 2023 03:38 PM UTC
**Owner:** nobody
Consider that the debugged target is repeatedly making READC semihosting call
after `arm semihosting_redirect tcp all` has been run. Target stops on
---
**[tickets:#442] SEMIHOSTING_SYS_REMOVE does not take `arm semihosting_basedir`
into account**
**Status:** new
**Milestone:** 0.11.0
**Created:** Fri Nov 22, 2024 01:37 PM UTC by Marek Vrbka
**Last Updated:** Fri Nov 22, 2024 01:37 PM UTC
**Owner:** nobody
The `arm semihosting_basedir
**Milestone:** 0.11.0
**Created:** Fri Nov 22, 2024 01:37 PM UTC by Marek Vrbka
**Last Updated:** Fri Nov 22, 2024 01:37 PM UTC
**Owner:** nobody
The `arm semihosting_basedir` allows to set a "working directory" for the
purposes of semihosting. The remove semihosting syscall does not ta
ram_exited` - would return true if the
semihosting exit already happened
* `arm semihosting_exit_code` - returns exit code (from
`SYS_EXIT_EXTENDED`)
Would you be in favor of this proposal? I welcome any comments.
Thank you,
Marek Vrbka
