Tommy Murphy

First thing to do in such circumstances is usually to collect and upload a verbose openocd -d3 log for analysis. It will usually shed a bit more light on the cause of the problem. If necessary, read the OpenOCD user documentation to see how to collect such a log.

I ran a live distro of Ubuntu 22.04.5 on VirtualBox (host OS Windows 10) and Firefox connected to https://openocd.org/ fine. I presume that the issue is something local to your own setup and probably needs the sort of diagnostic information mentioned above. What happens if you run a clean/live distro Ubuntu 22.04?

What do you mean by "vendor packed version etc"?

Yes - SDI is a WCH (proprietary?) 2-wire debug interface so presumably this OpenOCD (which is also old) is a custom/modified version from WCH or somebody else doing work with WCH RISC-V MCUs and questions about it should be directed to them. Not really sure why this was posted in an issue thread originally about Microchip SoftConsole OpenOCD? Seems completely off topic?

could you recommend a website where I could download this application for Windows 10? https://openocd.org/pages/getting-openocd.html

You're using a very old version of OpenOCD - a build from 2023. You should try again using a more recent build. And your script is using deprecated commands which should ideally also be corrected. If the problem persists then you should capture and upload a verbose openocd -d3 log, clarify exactly how you're running the tool and what scripts you are using. Screenshots aren't really a great idea - not everybody can easily use them and they can't be searched/analysed easily.

First step in such circumstances is almost always to capture and provide a verbose openocd -d3 log for the relevant debug session.

Does this repo contain anything of relevance? https://github.com/ArteryTek/openocd