Skip to main content
Aug 21, 2023 7:55 PM UTC
Question

STM32 VS Code Extension (No compiler found in cache file)

I am trying to get the STM32 VS Code Extension working on my macOS (Ventura 13.2.1). I have installed STM32CubeCLT and STM32CubeMX. I can compile my project successfully using the build command command. However when I press on the debug icon on the bottom toolbar, I get an error saying that "No compiler found in cache file Source Make Tools (Extension)" (See attached screenshot). I have examined the build/debug/build/CMakeCache.txt file and everything looks ok at first glance. Any insight or solutions as to what is going on would be welcomed.

This topic has been closed for replies.

25 replies

Associate II
Nov 27, 2024 1:37 PM UTC

I have the exact same issue. 
Windows 11, newest version of vscode, STM32 VS Code extension, etc.

Did you ever got this to work?

 

Edit; Oh, I see the user account is not active anymore. Anyways, perhaps ST employees can support. 

ST Technical Moderator
Nov 27, 2024 1:51 PM UTC
In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Associate II
Nov 28, 2024 7:38 AM UTC

Hi @Imen.D 
Thanks for your reply. 
I have followed the guide in the article, without luck. I still have the following two issues:

"No compiler found in cache file Source Make Tools (Extension)" when pressing the "debug" icon. Also next to the debug icon, on the right, when pressing "launch" the compiled .elf file is prompted to be opened. I am not quite sure how to proceed just with the .elf file (already tried to associate the .elf file with CubeProgrammer but nothing happens).

 

Finally I have the issue where choosing the "Upgrade ST Link firmware" option leads to the:

"Error whilst trying to update STLink Firmware" error. I can still in the terminal do the STLink firmware update though. 

ST Technical Moderator
Nov 28, 2024 8:34 AM UTC

It’s recommended to upgrade STLink FW prior to initiating the debug process.

Execute the command "stlinkupgrade" in the VSCode terminal. This resolves the issue in this post: Error whilst trying to update STLink Firmware - STMicroelectronics Community

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Associate II
Nov 28, 2024 2:09 PM UTC

Hi again @Imen.D 

Unfortunately you forgot to read my message that you were commenting to. I do not have the issue you linked to.

Here is goes again:

I have followed the guide in the article, without luck. I still have the following two issues:

"No compiler found in cache file Source Make Tools (Extension)" when pressing the "debug" icon. Also next to the debug icon, on the right, when pressing "launch" the compiled .elf file is prompted to be opened. I am not quite sure how to proceed just with the .elf file (already tried to associate the .elf file with CubeProgrammer but nothing happens).

Finally I have the issue where choosing the "Upgrade ST Link firmware" option leads to the:

"Error whilst trying to update STLink Firmware" error. I can still in the terminal do the STLink firmware update though. 


I already updated ST link firmware via the terminal and can do debug. The issue is the shortcuts that are not working. Ie. pressing the debug icon and the "Upgrade ST LInk firwamre" button in the extension page.

ST Technical Moderator
Nov 29, 2024 9:23 AM UTC

Hi @userst,

Thank you for rising this issue. 

We were able to reproduce the problem, and it was escalated internally for fix via the internal ticket: 195217.

Thank you for your contribution and for taking time to report this with details.

(PS: ticket 195217 is an internal tracking number and is not accessible or usable by customers).

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Javier1
Principal
Jan 6, 2025 3:31 PM UTC

Same issue here :(.
For me it was working last month, no apparent software update was made

im going to try to reinstall CPPtools: https://github.com/microsoft/vscode-cmake-tools/issues/2121#issuecomment-919353745

hit me up in https://www.linkedin.com/in/javiermuñoz/
MM1
Associate II
Feb 17, 2025 2:24 PM UTC

Hey there,

I am running into the same issue. has it been resolved yet?

Greetings Marcus

Explorer
Mar 10, 2025 5:03 PM UTC

I can also confirm that I am having the same problem.

ST Employee
Mar 11, 2025 8:44 AM UTC

Hello @3subzero3, @MM1, @Javier1, @userst 

Are you all using a MacOS? 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Explorer
Mar 11, 2025 2:41 PM UTC

I am on a Mac (Sequoia 15.3)

Senior III
Mar 11, 2025 1:15 PM UTC

same issue here on Windows 10

Senior III
Mar 13, 2025 8:34 AM UTC

I've tried with a brand new project on the NUCLEO-F401RE board and it has the same issue

Do we have an ETA as this is a pretty bad bug basically making the use of VScode impossible @Sarra.S @Imen.D 

Senior III
Apr 7, 2025 10:15 AM UTC

Hei @Sarra.S @Imen.D do we have an update on this?

Visitor II
May 15, 2025 10:59 PM UTC

Here is the solution for anyone still having this problem to "No compiler found in cache file Source Make Tools (Extension)". I don't know why ST would choose this response to outdated firmware on the ST-LINK. Your ST-LINK firmware needs to be updated. You can get it here, https://www.st.com/en/development-tools/stsw-link007.html?dl=redirect

 

I had this exact same issue with my NUCLEO-H563ZI, upgraded the firmware and it's working as expected. If you have a cloned ST-LINK it might not work, haven't tested it though.