Thank you for the explanations. Indeed, this makes sense only when the gdb
client and server are running on different machines.
---
** [tickets:#232] semihosting_fileio read return wrong number of read bytes**
**Status:** new
**Milestone:** 0.9.0
**Created:** Sun Apr 21, 2019 04:18 PM UTC by h
That's for the project maintainers to decide, I'm not one of them.
---
** [tickets:#232] semihosting_fileio read return wrong number of read bytes**
**Status:** new
**Milestone:** 0.9.0
**Created:** Sun Apr 21, 2019 04:18 PM UTC by hogthrob
**Last Updated:** Sun Apr 21, 2019 09:48 PM UTC
**Owne
If you mean the comments in semihosting_common.c, the SEMIHOSTING_SYS_READ
case, they do not refer to the gdb client protocol, but to the arm semihosting
protol (I contributed that file, and the large comment blocks were copied from
the arm semihosting pdf file).
As for the SF behaviour, no com
I confirm that for partial reads the SEMIHOSTING_SYS_READ call should return
the number of remaining bytes, and the regular (not the fileio) case does this.
However I do not have experience with the fileio use case. Your patch seems ok,
but I'd like someone more experienced to confirm this.
Pe
> I'd imagine that this is covered already somewhere.
and if it is not, it probably should be; even if we do not love Windows (or
exactly because of this) the OpenOCD documentation should also document how to
use it on Windows, to avoid such questions..
---
** [tickets:#214] Error: The speci
> Would it be safe to wait for the "accepting '%s' connection on tcp/%s" style
> messages
I guess so, but only as long as these messages are issued by all openocd
distributions, i.e. the changes are present in the master.
---
** [tickets:#147] How to know when OpenOCD is fully ready?**
**Sta
