Graduate

Solved

unable to find STM32H7 in Vs code project setup

Forum|Forum|4 months ago
October 24, 2025
10 replies
858 views

Hi I am trying to configure a project in Vs code.

1) Created/Generated a project using STM32CubeMX.

2) in vs code extensions added

3) by using open folder latest created project loaded

4) on pop-up Debug option selected

5) Then when it comes to device selection unable to find STM32H7 Series, eval board numbers in the list.

Note : STMCUFinder path, cubemx paths configured . please check below images

This topic has been closed for replies.

Best answer by Julien D

@Jagan1, do you confirm working behind a proxy?

If so, you have to set NODE_EXTRA_CA_CERTS environment variable (system wide) to reference your corporate CA bundle file.

V

vincent_grenet

ST Employee

@Jagan1
Please let's skip this quick pick and focus on the red text field. Has any device completion appeared when you start typing STM32...?
If not, could you please try running the following command in the VSCode integrated terminal:

cube pack sync

Does the process complete successfully? If not, please share the trace.

J

Jagan1Author

Graduate

Hi @vincent_grenet , Other boards/devices showing only STM32H series missing.

unable to sync also .

J

Julien DAnswer

ST Employee

@Jagan1, do you confirm working behind a proxy?

If so, you have to set NODE_EXTRA_CA_CERTS environment variable (system wide) to reference your corporate CA bundle file.

J

Jagan1Author

Graduate

i am not sure if i am using proxy.

is there any other solution.

J

Julien D

ST Employee

Better to confirm this before going one way or the other.

Could you paste the following line into your PowerShell terminal integrated in VSCode ?

It should print the certificate information you see from developer.st.com domain.

$cert = [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
$tcp = New-Object Net.Sockets.TcpClient('developer.st.com', 443)
$ssl = New-Object Net.Security.SslStream($tcp.GetStream(), $false, ({$true}))
$ssl.AuthenticateAsClient('developer.st.com')
$ssl.RemoteCertificate | Format-List *

Then past the output here.

J

Jagan1Author

Graduate

Hi,

Highlighted ones masked.

if need i can share personally

Handle : Number
Issuer : CN="zscaler.xxxxxx.com (t) ", OU=Security Operations, O=xxxxxx Technologies, S=Location, L=Location, C=US
Subject : OU=Zscaler Inc., O=Zscaler Inc., CN=www.st.com

J

Julien D

ST Employee

No this is already good enough to highlight the fact that your behind a proxy doing SSL inspection.

Then NODE_EXTRA_CA_CERTS is required to point to your Zscaler root CA certificates.

If you can navigate to https://developer.st.com/ without troubles it likely means that such certificates are already trusted into your Windows certificate manager.

capture picked from the internet

You could try export them (Zscaler*) in base-64 encoded X.509 format, and gather all exported files into a .crt file respecting this kind of format:

Then reference this file with NODE_EXTRA_CA_CERTS

J

Jagan1Author

Graduate

J

Julien D

ST Employee

Ok, it is denied but at least you have the lock meaning connection is secured, so you can proceed with the rest of my previous message.

J

Jagan1Author

Graduate

Hi, fallowed same steps, only one Zscaler is there in certmgr and exported, still same issue.

>> Restarted vs code

PS C:\Users\JNEKKALAPUDI\Documents\stm\test_gen\test5> setx NODE_EXTRA_CA_CERTS "C:\Users\JNEKKALAPUDI\Documents\stcertificate.cer"

SUCCESS: Specified value was saved.
PS C:\Users\JNEKKALAPUDI\Documents\stm\test_gen\test5> cube pack sync
Syncing metadata information C:/Users/JNEKKALAPUDI/AppData/Local/stm32cube/packs
Snapshot is already up to date
Syncing online metadata information C:/Users/JNEKKALAPUDI/AppData/Local/stm32cube/packs
Checking pidx https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx... (1/1)
Failed to download with request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate, retrying...
Failed to download with request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate, retrying...
Failed to download with request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate, retrying...
Failed to download with request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate, retrying...
Failed to download with request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate, retrying...
Maximum number of retries reached: request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate
Downloading https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed: FetchError: request to https://developer.st.com/st-pack-server/api/v1/pidx/STMicroelectronics.pidx failed, reason: unable to get local issuer certificate (1/75)
Syncing completed in 0.964s
PS C:\Users\JNEKKALAPUDI\Documents\stm\test_gen\test5>

J

Julien D

ST Employee

AFAIR there should be at least 2 certificates, the Zscaler Root CA and the Zscaler Intermediate Root CA, as shown in this screenshot (again picked on the Internet):

J

Jagan1Author

Graduate

only one is there.

J

Julien D

ST Employee

only one is there.

I wonder from where you get this screenshot. If from the Windows cert manager then I think it is expected since you only view the selected certificate. But if you get the certificate by clicking on the lock from a browser you may get more certificates in the chain.