Unable to install the bundles...

[emiya0306]

VS Code report: "Unable to contact the STM32Cube registry, verify your Internet connection..."

Can I know the registry URL of the STM32Cube bundles registry and test its connection?

[Nawres GHARBI]

Hi @emiya0306 

If you are hidden behind your company security, you probably need to configure a proxy and certificate to be able to access servers and download packages

This is how you will succeed in having full server access with our STM32Cube extension for VSCode.

 

How to Configure the proxy:

• Open settings and type proxy in the search bar

 

 

Put your proxy in this format http://user:pass@Proxy-address:port

How to Configure the certificate:

• Assuming your corporate self signed cert is trusted by your OS, you can now configure VS Code to use the OS cert. Launch VS Code, go to File > Preferences > Settings > Search for "certificates" and check the box for Http > Experimental: System Certificates V2 ".
  IT Controls whether experimental loading of CA certificates from the OS should be enabled
  
  
• Otherwise make sure that the certificates are imported into your OS and trusted in system category. Then, go into VSCode settings, Application, Proxy, and UNCHECK the "System certificates" option. Restart VSCode and RE-CHECK it. Restart again, and it works.

• if you want to do it the Manual way

1. Open a corporate portal home page in browser and download Root CA certificate. This certificate is usually the first one in the hierarchy of 3 certificates available there. Another option is to ask security team to provide you a corporate Root CA certificate file in Base-64 format.
2. Right-click the certificate file and select Install Certificate.
3. Add Windows Environment variable NODE_EXTRA_CA_CERTS with path to this certificate file.
4. Restart Visual Studio Code and try again.

[emiya0306]

Hi @Nawres GHARBI 

I think I don't have any company security, and just install STM32Cube for VSCode at home.

[Julien D]

Hi @emiya0306,

There is an error in the output shown in one of your screenshot, but partially visible because of vscode notifications.

Could you open a vscode terminal, execute the command cube bundle list-online, and paste here the error if any ?

[Julien D]

Everything looks ok from the logs, the failures are due to the fact that our underlying cube command fails to get the list of remote bundles, we have an internal discussion about your case on-going.

In the meantime, you can retry after removing every stm32cube folders:

• C:\Users\41541\AppData\Local\stm32cube
• C:\Users\41541\AppData\Roaming\stm32cube

[emiya0306]

Thanks a lot, I retry the method and it seems not work.

And, if you need more information, please feel free to contact me. ;)

[Niklas-Dahlquist]

Hi,

Could you help us investigate two things, we are a bit suspicious that Your user name could be interpreted wrongly. 

Do you have this as a login name 41541 ?

Can you run  echo $LASTEXITCODE after running cube --verbose bundle list-all-online

 

[emiya0306]

Hi @Niklas-Dahlquist ,

"41541" is my Microsoft Email Account, the full name is "[e-mail]". I run "whoami" in PowerShell, it show "laptop-2n9slqe6\41541".

It works on echo $LASTEXITCODE and cube --verbose bundle list-all-online. 

But if I run STM32Cube: Install prerequisite bundles, it show these reports.

[Julien D]

Seems like you are now able to list the content of the bundle registry, did you changed something (network connection, etc..) on your side which could explain?

What Niklas suggested was to do the echo $LASTEXITCODE once the cube command completes. It allows to print the exit code of the last executed command (usually 0 means success, >0 means a failure).

The second screenshot highlights that there are still some issues with the installation of the required bundles. Could you run the following commands in the suggested order?

cube bundle list
echo $LASTEXITCODE
cube bundle install cube-code-manifest@1.0.3+st.1 --yes
echo $LASTEXITCODE
cube bundle install cmake ninja --yes
echo $LASTEXITCODE
cube bundle list
echo $LASTEXITCODE

 

list: lists the bundles installed on your PC.

--yes: accepts the bundle licences by default (up to you to remove this option to read the licence terms)

[Julien D]

Just sent a PM

[chaaalyy]

Also here: Came back to ST after a (very long) while because the VScode-approach made me curious. But what did i expect after all the experiences from earlier years, even the (everywhere recommended and advertised by ST´s newsletter...) try to install the preview version of the STM32cube extensions failed immediately... Fortunately i didn´t try this on a production machine and used a dedicated testrig...
Just as a hint for the extension-developers: Check your filesizes and SHA256 checksums ;)
I for myself uninstalled everything and don´t waste more time on that early alpha-stage package.

[Julien D]

Thanks @chaaalyy for sharing your experience here and there.

To be exact what you face is likely unrelated to this topic; the bundle registry is currently down, our ISP is working on it. 

[Julien D]

@chaaalyy @Jakob K. The bundle registry service is now online, let us know if something continues to fail. Otherwise apologize for bad experience, the first time it happened with this server location since 2019.

[Jakob K.]

Hi @Julien D. Eventually it worked, seems I chose an unlucky date to try the Cube extensions :( 

Now I am experiencing the  'Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor' message and VS Code's Python Debugger no longer works. The issue has been reported here and there. Can you explain what happens using the ST extensions and is using VS Code profiles the only possible solution?

[Julien D]

@Jakob K. I can’t write more about, excepting that we have an internal ticket for this specific issue. Hopefully we’ll deliver a fix in a next release if something is feasible on our side. 

Until then Profiles are the way to go yes. 

[Julien D]

@Jakob K. The 'Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor'  has been analyzed and fixed, it will be delivered with next release. Apologize for the inconvenience.