OpenOCD installation Issue

mstsai · June 15, 2019, 4:00pm

Hi!

I am trying to install espressif32 platform on PlatformIO on Visual Studio Code on Win10.
However, I got the follow error messages,

PackageManager: Installing tool-openocd-esp32 @ ~1.1000.20180920
Downloading [####################################] 100%
Unpacking [#########################-----------] 71%
Unpacking…
Warning! Package Mirror: [Errno 22] invalid mode (‘wb’) or filename: ‘C:\Users\mstsai\.platformio\packages\_tmp_installing-gfoqhr-package\share\openocd\scripts\target\1986\xd0\xb2\xd0\xb51\xd1\x82.cfg’
Looking for another mirror…
Error: Could not install ‘tool-openocd-esp32’ with version requirements ‘~1.1000.20180920’ for your system ‘windows_amd64’.

Please try this solution → Redirecting...
The terminal process terminated with exit code: 1

I downloaded the file, tool-openocd-esp32-darwin_x86_64-1.1000.20180920.tar.gz, and checked it. I found that the filename of a file in share/openoce/scripts/target/ has rather strange characters, i.e., 1986ве1т.cfg.
I think this is the reason that causes the failure of the installation.
How do I resolve this problem?

Thanks.

maxgerhardt · June 15, 2019, 8:51pm

Strictly speaking this is the Mac OS version but also it appears on every platform. Seems like the unpacking logic in the core cannot handle special UTF8 or Unicode characters. @ivankravets?

mstsai · June 16, 2019, 5:10am

I tried manual installation the package. I created a folder named, tool-openocd-esp32, in .platformio\packagesand and extracted the file into that folder.
Executed ‘pio run’ on terminal. I still got the same error messages!!

ivankravets · June 23, 2019, 8:25pm

@valeros could you reproduce this issue with PIO Core 3.0 or PIO Core 4.0?

eziya · June 23, 2019, 11:07pm

Hello, l got the same issue.
I’ve updated all but it doesn’t solve the issue.
I got same error messages of invalid mode or file name.
I’m using windows 10 professional 64bit edition and vscode.

PIO Plus (https://pioplus.com) v2.5.2
PackageManager: Installing tool-openocd-esp32 @ ~1.1000.20181026
Downloading  [####################################]  100%
Unpacking  [#########################-----------]   71%  00:00:08
Unpacking...
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\KIKI\\.platformio\\packages\\_tmp_installing-gzjlhl-package\\share\\openocd\\scripts\\target\\1986\xd0\xb2\xd0\xb51\xd1\x82.cfg'
Looking for another mirror...
Downloading  [####################################]  100%
Unpacking  [#########################-----------]   71%  00:00:06
Unpacking...
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\KIKI\\.platformio\\packages\\_tmp_installing-tyx1jq-package\\share\\openocd\\scripts\\target\\1986\xd0\xb2\xd0\xb51\xd1\x82.cfg'
Looking for another mirror...
Error: Could not install 'tool-openocd-esp32' with version requirements '~1.1000.20181026' for your system 'windows_amd64'.

Please try this solution -> http://bit.ly/faq-package-manager
The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

maxgerhardt · June 24, 2019, 4:45pm

@ivankravets @valeros You need to test this on a PC without kyrillic language packs installed, the problem here is unpacking the file called 1986ве1т.cfg (ref)

ivankravets · June 24, 2019, 6:29pm

All packages were updated. Please re-run pio update or try to install again.

maxgerhardt · June 24, 2019, 6:32pm

Works for me on a german Win10 x64

PackageManager: Installing tool-openocd-esp32 @ 1.1000.20190624
Downloading  [####################################]  100%
Unpacking  [####################################]  100%
tool-openocd-esp32 @ 1.1000.20190624 has been successfully installed!

eziya · June 25, 2019, 12:31pm

Hello, @ivankravets

I still have an issue.
к1879xб1я.cfg, This file causes error.

Processing esp32doit-devkit-v1 (framework: arduino; platform: espressif32; board: esp32doit-devkit-v1)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PackageManager: Installing tool-openocd-esp32 @ ~1.1000.20190624
Downloading  [####################################]  100%
Unpacking  [################################----]   90%  00:00:02
Unpacking...
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\KIKI\\.platformio\\packages\\_tmp_installing-8ipa7j-package\\share\\openocd\\scripts\\target\\\xd0\xba1879x\xd0\xb11\xd1\x8f.cfg'
Looking for another mirror...
Downloading  [####################################]  100%
Unpacking  [################################----]   90%  00:00:02
Unpacking...
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\KIKI\\.platformio\\packages\\_tmp_installing-bf_csv-package\\share\\openocd\\scripts\\target\\\xd0\xba1879x\xd0\xb11\xd1\x8f.cfg'
Looking for another mirror...
Error: Could not install 'tool-openocd-esp32' with version requirements '~1.1000.20190624' for your system 'windows_amd64'.

Please try this solution -> http://bit.ly/faq-package-manager
The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

maxgerhardt · June 25, 2019, 1:15pm

Can you remove all _tmp_* folders and retry?

eziya · June 25, 2019, 1:52pm

Thanks @maxgerhardt

It works like a charm

Dr.Q · September 11, 2019, 12:39am

I had exact same issue installing openocd for stm32

I tried

remove platformio and delete all files in my c:\user\name\.platformio
re-install platformio

But No success.

So I manually download the package from here

Searched openocd files and downloaded file with name tool-openocd-windows_amd64-2.1000.190422.tar.gz

I extracted the file and copy paste into the package folder under .platformio folder

Now it is working!

deltaphi · August 9, 2020, 8:49am

Hello PlatformIO-Experts,

I just experienced this issue with the latest release tool-openocd-windows_amd64-2.1000.200628 for stm32.

I had no problem using the previous release (2.1000.190707), which is one release newer than what @Dr.Q reported having problems with.

My system is a german Windows 10 Pro by Lenovo. I’m not aware of ever having done anything with kyrillic language packs. When removing tool-openocd from my packages folder (or deleting the packages folder altogether) and rerunning my “upload” command in PlatformIO, I get the following error message:

Processing bluepill (platform: ststm32@~6.1.1; board: bluepill_f103c8; framework: libopencm3)
-------------------------------------------------------------------------------------------------------------------------------------------------- 
PackageManager: Installing tool-openocd @ ~2.1000.0
Downloading  [####################################]  100%
Unpacking  [#######################-------------]   64%
Unpacking...
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\Damian\\.platformio\\packages\\_tmp_installing-bun2ao-package\\scripts\\target\\1986??1?.cfg'
Looking for another mirror...
Downloading  [####################################]  100%
Unpacking  [#######################-------------]   64%
Unpacking...
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\Damian\\.platformio\\packages\\_tmp_installing-kgt7ew-package\\scripts\\target\\1986??1?.cfg'
Looking for another mirror...
Error: Could not install 'tool-openocd' with version requirements '~2.1000.0' for your system 'windows_amd64'.

Please try this solution -> http://bit.ly/faq-package-manager

This can reliably be reproduced so long as the package tool-openocd is not available to PlatformIO.

Extracting the tarball tool-openocd-windows_amd64-2.1000.200628.tar.gz manually using 7-Zip 19.00 (2019-02-21) also gives a strange warning message: 7zip wants to overwrite the file tool-openocd-windows_amd64-2.1000.200628\@PaxHeader with .\.\\n@PaxHeader. Note the weird newline in the second path! It actually shows up as a line break in the UI, not as the escape sequence I have here. Curiously, 7zip File Manager does not show the existence of a file named @PaxHeader in the tarball. However, after extracting finishes, the file is present.

If I rename the extracted folder to tool-openocd and move it to my packages folder, PlatformIO will happily upload to my bluepill board. However, teaching all users to apply this workaround which itself leads to another confusing error message does not really scale. Is it possible to make auto-installation of tool-openocd work again on windows?

Thanks!
Damian

ndias · August 10, 2020, 2:37pm

@Dr.Q / @deltaphi 's solutions also worked on my side. I’m glad to find it here. Thank you!!!

christandlg · August 11, 2020, 9:06am

@Dr.Q/@deltaphi 's solution did not work for me. I have downloaded tool-openocd-windows_x86-2.1000.200628.tar and extracted it to C:\Users\username\.platformio\packages (noticing the same 7zip warning that @deltaphi has seen) and renamed the folder. The directory structure looks good to me, but the PackageManager still attempts to install tool-openocd and fails.
grafik

ndias · August 12, 2020, 3:37pm

Hi @christandlg,

I haven’t tried the version tool-openocd-windows_amd64-2.1000.200628.tar.gz. I just tried the tool-openocd-windows_amd64-2.1000.190707.tar.gz version as @deltaphi mentioned. I extracted the files on %userprofile%\.platformio\packages\tool-openocd folder.
I tried it on two different PCs and it worked on both.

Good luck on your side.

christandlg · August 12, 2020, 6:51pm

hi @ndias,
I was able to fix the problem by copying over the tool-openocd package from a different computer where the update worked without issues.

jryan · August 16, 2020, 7:40am

Just to confirm that I had the issue with the VScode IDE running on windows 8.1 enterprise.

Manual download of tool-openocd-windows_amd64-2.1000.200628.tar.gz and extract into the tool-openocd folder as above worked for me.

Original error when VS code attempted download was
Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\jryan\\.platformio\\packages\\_tmp_installing-8dezjz-package\\scripts\\target\\1986??1?.cfg'

Folder \tool-openocd-windows_amd64-2.1000.200628.tar\scripts\target\ contains two files with ? in their name 1986??1?.cfg and ?1879x?1?.cfg

Perhaps a simple rename would solve the issue?

manuelbl · August 23, 2020, 8:40pm

I’ve run into this issue as well. I’ve opened an issue on GitHub:

github.com/platformio/platformio-core

Fails to install package tool-openocd on Windows

opened 08:36PM - 23 Aug 20 UTC

closed 09:29AM - 25 Aug 20 UTC

manuelbl

bug registry

### Configuration **Operating system**: Windows 10 **PlatformIO Version** …(`platformio --version`): 4.3.4 ### Description of problem PlatformIO is unable to install the package *tool-openocd* on Windows. The package is needed for uploads or for debugging. #### Steps to Reproduce 1. Delete package from `C:\Users\username\.platformio\packages` 2. Execute an upload (e.g. if *st-link* is specified as *upload_protocol* for an *stm32* project) ### Actual Results The installation and the upload fails ``` Warning! Package Mirror: [Errno 22] invalid mode ('wb') or filename: 'C:\\Users\\username\\.platformio\\packages\\_tmp_installing-8dezjz-package\\scripts\\target\\1986??1?.cfg' ``` Also see the error reports in https://community.platformio.org/t/openocd-installation-issue/8199/12 (posts since about Aug 10, 2020). ### Expected Results The package installs successfully and can be used for upload and debugging. ### Additional info The problem might depend on the selected locale / language. My Windows machine has a mixture of English (United States) and Switzerland. Other users reports problems with German settings. The core of the problem likely are the Cyrillic filenames *1986ве1т.cfg* and *к1879xб1я.cfg* in OpenOCD (see https://sourceforge.net/p/openocd/code/ci/master/tree/tcl/target/). The *tar* file format has no robust and standardized way for representing such filenames across all platforms. If the *tar* file is created with UTF-8 encoding, the same encoding must be used for decoding. Otherwise the current encoding is used to decode the filenames, resulting in problems. On my Mac, there was no problem unpacking the file. So as a workaround, I downloaded the file https://bintray.com/platformio/dl-packages/download_file?file_path=tool-openocd-windows_amd64-2.1000.200628.tar.gz on my Mac, unpacked it, copied to Windows, renamed it to `tool-openocd` and put it in the right place.