cancel
Showing results for 
Search instead for 
Did you mean: 

stm32cube VS Code Project Setup STM32F100 device not found

Marky_Mark
Associate II

I have followed all the instructions to creating a project in MXCube and importing it into VS Code, however there is no option to select STM32F100VBT6 (Or any MCU in the F1 series for that matter). Is the STM32F1 series not supported? 

2025-10-29 17_19_03-Project Setup (RWA_cube) - Untitled (Workspace) - Visual Studio Code.png

1 ACCEPTED SOLUTION

Accepted Solutions
Cartu38 OpenDev
Lead III

@Marky_Mark STM32F1 like any STM32 device of portfolio is fully supported.

Cartu38OpenDev_0-1761804772341.png

Is your issue related to https://community.st.com/t5/stm32cubeide-for-visual-studio/unable-to-find-stm32h7-in-vs-code-project-setup/td-p/850426 ?

Could you try running the following command in the VSCode integrated terminal:

cube pack sync

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

View solution in original post

6 REPLIES 6
Cartu38 OpenDev
Lead III

@Marky_Mark STM32F1 like any STM32 device of portfolio is fully supported.

Cartu38OpenDev_0-1761804772341.png

Is your issue related to https://community.st.com/t5/stm32cubeide-for-visual-studio/unable-to-find-stm32h7-in-vs-code-project-setup/td-p/850426 ?

Could you try running the following command in the VSCode integrated terminal:

cube pack sync

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

Hello @Cartu38 OpenDev , thank you for your reply. I've ran the command you mentioned and here is what it looks like: 

2025-10-30 10_28_20-Project Setup (RWA_cube) - Untitled (Workspace) - Visual Studio Code.png

My issue does seem to be similar to that one and likewise after following all the instructions from that thread (including exporting the certificates and referencing them to the NODE_EXTRA_CA_CERTS) there is no change in the behaviour of VS code. Neither of our issues have been solved unfortunately despite both of them being flagged as "solved" here 

Marky_Mark
Associate II

It worked finally after I appended and referenced the contents of the reply to the following:

$hostname = "developer.st.com"
$tcp = New-Object Net.Sockets.TcpClient($hostname, 443)
$ssl = New-Object Net.Security.SslStream($tcp.GetStream(), $false, ({$true}))
$ssl.AuthenticateAsClient($hostname)
$cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $ssl.RemoteCertificate

$chain = New-Object System.Security.Cryptography.X509Certificates.X509Chain
$chain.Build($cert) | Out-Null

foreach ($element in $chain.ChainElements) {
    Write-Host "----- Certificate -----"
    Write-Host "Subject: $($element.Certificate.Subject)"
    Write-Host "Issuer: $($element.Certificate.Issuer)"
    Write-Host "NotBefore: $($element.Certificate.NotBefore)"
    Write-Host "NotAfter: $($element.Certificate.NotAfter)"
    Write-Host "Thumbprint: $($element.Certificate.Thumbprint)"
    Write-Host ""
    $base64 = [Convert]::ToBase64String($element.Certificate.RawData)
    $pem = "-----BEGIN CERTIFICATE-----`n"
    $pem += ($base64 -split "(.{1,64})" | Where-Object { $_ -ne "" }) -join "`n"
    $pem += "`n-----END CERTIFICATE-----`n"
    Write-Output $pem
}

solved

Marky_Mark
Associate II

Thank you!