Tommy Murphy

Do you need to build it yourself? Could you use the xPack Project binary builds from @ilg-ul? If you really do need to build it yourself then you could use...

> Hi, I am facing the same issue. While extracting the binaries from https://github.com/xpack-dev-tools/openocd-xpack/releases/download/v0.10.0-15/xpack-openocd-0.10.0-15-linux-x64.tar.gz. this, I am not able to get **riscv** target. > And for ./configure option, it is...

If you get an error then you are not following @ilg-ul's instructions for running his xPack Project docker based openocd build scripts correctly. Please review the instructions again and if...

> In future, I would like to switch to a stable release-grade > toolchain from the upstream, once such build exists. Would you consider using a crosstool-NG build of the...

I mean build the tools once (or whenever there are "significant" changes to the upstream repos - gcc, gdb/binutils, newlib etc.) and then use those toolchain binaries. Not doing a...

Ok - no worries. Just a suggestion. As you say, any reputable third party toolchain that is regularly maintained updated should do and I know that Liviu's xPack Project version...

I have used Liviu's (@ilg-ul ) xPack docker scripts to build the riscv-openocd fork successfully many times for many years so you must be doing something wrong, E.g. use them...

I think if you specify the master rather than riscv branch then it tries to pull (and build?) lots more than just openocd - e.g. a full riscv toolchain, qemu...

This is simply down to how sifive are naming/arranging their branches. I don't think that you can infer what master should do here from what it does elsewhere (e.g. in...

For what it's worth I used to work for Microchip on SoftConsole so have some knowledge of what you're working on here. However I'm a bit confused. I presume that...