Update openocd install for windows

[hazelutf8]

It seems the preferred method for installing openocd on windows has changed?

First of all, thanks a lot to the author for the nice step-by-step guide for both Linux and Windows, both from command-line and with Visual-Studio Code!

It seems the recommended way to install openocd it to first install npm then install xpm and then have it install openocd?

Is this is correct?

Some of my own installation notes (command line use only):
https://github.com/hazelutf8/blue-pill-notes

With some style guidance, I would be open to submitting a PR for this issue.

[lupyuen]

Hi: Thanks for the feedback :-)

Nowadays I prefer to make the installation automated and foolproof, so my latest OpenOCD installation script downloads the Windows build of OpenOCD from the Eclipse project...

https://github.com/lupyuen/stm32bluepill-mynewt-sensor/blob/nrf52/scripts/install-windows.sh#L31-L39

Also I'm not really keeping this repo up to date any more... I find Bare Metal Rust quite hard to program, it changes too often and it lacks drivers for sensors and networks. Nowadays I'm building Blue Pill Rust apps on top of the Apache Mynewt RTOS, which has lots more useful features...

https://medium.com/@ly.lee/rust-rocks-nb-iot-stm32-blue-pill-with-quectel-bc95-g-on-apache-mynewt-ef62a7e28f7e?source=friends_link&sk=aaa21371f68a07c543066b6b89a760f0

That article has some outdated code. You may refer to my latest Rust article, which is based on nRF52 instead of Blue Pill...

https://medium.com/@ly.lee/coding-nrf52-with-rust-and-apache-mynewt-on-visual-studio-code-9521bcba6004?source=friends_link&sk=bb4e2523b922d0870259ab3fa696c7da

If you look at the installation instructions, I have chosen to bundle OpenOCD into the release download (stm32bluepill-mynewt-sensor.7z in the link below). It makes installation even easier...

https://github.com/lupyuen/stm32bluepill-mynewt-sensor/releases/tag/v10.0.0

I still think that Rust is the best option for embedded development, though the learning curve is steep. That's why I'm experimenting with Visual Rust programming...

https://blog.usejournal.com/visual-embedded-rust-programming-with-visual-studio-code-1bc1262e398c?source=friends_link&sk=222de63e45993aacd0db5a2e4b1f33c7

[hazelutf8]

When looking at the repository the script gets OpenOCD from, the last windows binary build by gnu-mcu-eclipse was 2019-04-22, and as of 2019-09-27 builds moved to the xPack project.

I did a little digging, and found the release binaries now live at openocd-xpack, with the latest windows binary build: https://github.com/xpack-dev-tools/openocd-xpack/releases/download/v0.10.0-13/xpack-openocd-0.10.0-13-win32-x64.zip

But it looks like your script is already getting the ARM toolchain from xpm/xPack.
Would you want a PR to either change the URL to the newer xpack-openocd releases, or to use the xpm installation command for OpenOCD just like the ARM toolchain does?

[lupyuen]

Since I'm not really spending time to maintain this repo (sorry for the slow response)... I suppose I can trust you to submit the right PR and I'll gladly approve it :-)

If you have any idea how I should maintain this moving ahead, lemme know :-)