Debugging under VS Code failed

[dze.1]

Hi,

I followed exactly the instructions of ST's youtube tutorial "Get started with STM32Cube for VS Code: from installation to debugging". (https://www.youtube.com/watch?v=aWMni01XGeI)

Everything went perfect, the demo builds without problems.

When it comes to debugging, VS Code gives me the error "Failed to install missing pack. "STMicroelectronics.stm32u3xx_dfp.1.0.0"

Additional the is the same error as extension notification, see below.

I tried Ctrl+Shift+P + Restore STM32Cube CMake projects configuration, but to no avail.

Same thing happens with other STM32 CMake projects.

What did I miss?

Thank You in advance

[Julien D]

Hi @dze.1,

You can try to install manually the missing pack from vscode terminal with the command cube pack install STMicroelectronics.stm32u3xx_dfp.1.0.0 and check if there is any relevant error.

[dze.1]

Hi,

thanks for reply.

I should mention I'm using STM32Cube for Visual Studio Code 3.4.11 as recommended in the tutorial.

Neither cube pack install STMicroelectronics.stm32u3xx_dfp.1.0.0 nor STM32Cube: pack install STMicroelectronics.stm32u3xx_dfp.1.0.0 succeeded.

Such a command seems not to exist. I have attached all other available STM32 extension commands below.

But STM32Cube: Synchronize pack list runs without error. But again to no avail.

Thanks.

 

[KnarfB]

This command is to be entered in the terminal, not in the command palette:

hth

KnarfB

[dze.1]

Hallo KnarfB,

thank you so much. My fault. I'm new with VS Code (worked for years with CubeIDE).

There seems to be a problem with certificates. May be an IT problem.

Is there a solution to download the packs manually and place them into the expected folder? Since I have CubeIDE and CubeMX heavily in use, the packs shall be already on my machine. May be just a copy is sufficient.

Thank you very much.

Dirk

[KnarfB]

The packs are new with STM32Cube for Visual Studio Code 3.x pre-release. Switching back to 2.x should work.

hth

KnarfB

[Julien D]

This is indeed an IT issue, all what you should need is to define NODE_EXTRA_CA_CERTS system variable to point to a bundle CA certificates file. Your local IT must be in a position to share this file with you. 

[dze.1]

Hallo Julien,

thank you very much for this indication.

After getting the certificates and the CA bundle file from my local IT and applying it (set NODE_EXTRA_CA_CERTS systems variable to the bundle file and the certificates), the result looks like this:

Failed to download with request ..., reason: write EPROTO F8290000:error:0A000152:SSL routinesfnlr:final_renegotiate:unsafe legacy renegotiation disabled

I gues much more IT problems - surely on my side.

[Julien D · Accepted solution]

Looks like you have a custom openssl install in c:\ws\deps\openssl

If this install is required for something else you may need to set its openssl.cnf to

openssl_conf = openssl_init

[openssl_init]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
Options = UnsafeLegacyRenegotiation

 I can't try this on my side though.

[dze.1]

Hallo Julien,

I have no openssl installed.

However, I did complain to my company IT again. They solved the problem now. Some server side internal IT stuff I have no insight to. Now it works.

Thank you very much for your help and patience.

Dirk