On 17 Apr 2023, at 14:47, Kristof Mulier kristofmulier@users.sourceforge.net wrote: We have prepared two projects for this demonstration: • f303-working: This project works with all the OpenOCD versions - up to and including OpenOCD 0.12.0 • f303-failing: This project works with OpenOCD 0.10.0, but not with OpenOCD 0.11.0 and 0.12.0. This approach is a bit unusual; since you have a binary that can be flashed with all versions and one that fails with the latest two versions, assuming that all other...
Thank you!
libmangle should include <malloc.h> conditionally
I also faced MAX_PATH issues, with GCC failing during CMake builds (which usually create deep folder hierarchies); removing the limit in Windows did not help, which made me think that there must be a limit somewhere in mingw or gcc, or both.
cosmetics
Thank you for the explanations. Indeed, this makes sense only when the gdb client and server are running on different machines.
That's for the project maintainers to decide, I'm not one of them. From my point of view, the patch seems ok. However I never used OpenOCD semihosting via the GDB client and I don't know how to test it.
That's for the project maintainers to decide, I'm not one of them. From my point of view, the patch seems ok. However I never used OpenOCD semihosting via the GDB client and don't know how to test it.
That's for the project maintainers to decide, I'm not one of them. From my point of view, the patch seems ok. However I never used OpenOCD semihosting via the GDB client and don't know how to test it.
That's for the project maintainers to decide, I'm not one of them. From my point of view, the patch seems ok.
That's for the project maintainers to decide, I'm not one of them.
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 comments, I moved everything to GitHub several years ago. As for using Gerrit to contribute patches to OpenOCD,, there are some explanations somewhere on the OpenOCD site, it is basically a git thing, you push...
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. Perhaps you can also explain in a few words how this works. Is the call forwarded to the gdb client? What is this call returning for partial reads? Anyway, if the maintainers aggree on this patch, I suggest you...
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..
Avoid null target->semihosting references.
log.h: add ERROR_TIMEOUT_REACHED
mips_m4k.c: Fix build with --disable-target64
target/target.c: free semihosting member
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting
Rework/update ARM semihosting