Merge recent upstream changes

[iCMDdev]

Hello,

I'd appreciate if you could merge recent changes in upstream OpenOCD. I am particularly interested in commit openocd-org/openocd@22e1e1b, as it fixes a bug which prevented later LLDB versions (e.g. LLDB 21) from connecting to the debug server.

I'm not sure what the general method of merging upstream changes is in this repo, but I've seen that in #146 @P33M advised the author to submit the patch to upstream, and then ping them (note: this is not related to that PR).

Thanks!

[P33M]

@tom-van could you nominate a point on upstream master that would be considered known-good?

Also, when's the next release / 1.0.0 version of OpenOCD expected to land?

[iCMDdev]

Also, when's the next release / 1.0.0 version of OpenOCD expected to land?

I am not sure, though one of the OpenOCD maintainers said (in the patch review on Gerrit, for the commit I linked) that they will tag 1.0.0 asap.

[tom-van]

... though one of the OpenOCD maintainers said (in the patch review on Gerrit, for the commit I linked) that they will tag 1.0.0 asap.

asap is getting somewhat long as lot of important patches getting dust instead of reviews.

The good point is that the upstream OpenOCD has mostly merged the newest RISC-V code from https://github.com/riscv-collab/riscv-openocd
But it also means that the original RISCV DM over ADI DAP set of patches no longer applies. I have the updated version, I used it for the new RISC-V target code testing. My intention was to publish it as soon as RISC-V target code gets into more stable state (after 1.0 release)

In the meantime please look at minor issue #143 (comment)
and review it in gerrit
9272: gdb_server: preserve gdb monitor command output from Tcl events | https://review.openocd.org/c/openocd/+/9272