Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32


GCC path Enviroment variable

Hi!

Is there a way to change the path of the GCC compiler?. This is defined by a native enviroment variable “openstm32_compiler_path” which points by default to the compiler version contained in a installation folder.

I tried to redefine it but I get the failure in the screnshot.



We would like this variable to point to another folder, so we can keep control of what version of the compiler we are using. Otherwise with a new update of the System Workbench we get a new compiler version and the behaviour of the software could be different

Thanks a lot!

Regards

David

Hi David,

For now, the only way to change the GCC compiler path is to modify the Path setting in your project Properties > C/C++ Build > Settings > Tool Settings > Path and set the absolute path to your compiler. When System Workbench is updated, this setting will not be changed.

Redefining the “openstm32_compiler_path” does not work for now. I did report it to the development team to fix it on a next version.

Regards,
Kevin.

Hi!

I tried this but it does not work. It seems the software does not care this variable (maybe because I am compiling generating automatic make files?).

I even remove the compiler path, leaving it empty, and it continues compiling using the built-in gcc compiler.

Did you do something else appart from changing this setting?

Thanks!

Any updates on this topic?

Thanks in advance!


Hi David,
I faced issues with GCC 5.4.1, so I downloaded and uncompressed the 5_4_2016q3 compiler version from :
https://launchpad.net/gcc-arm-embedded/5.0/5-2016-q3-updateQuestion
Then, right-click on the project >> Properties >> C/C++ Build >> Settings >> MCU Settings
then replace ${openstm32_compiler_path} with the path to the bin folder of the uncompressed 5_4_2016q3 compiler version :
for me it gives :
${openstm32_compiler_path}
replaced with :
C:\Project\STM32\Tools\GCC\gcc-arm-none-eabi-5_4-2016q3-20160926-win32\bin
It is clearly using the new GCC version and it fixes my issue.


 

Newest Forum Posts

  1. Можно ли установить камин на балконе или лоджии? by Grand3kpdErorb, 03:38
  2. reservation car service Seattle by Jamesprede, 2025-05-01 10:06
  3. Last day: drone bonus by Danielrug, 2025-04-19 16:55
  4. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  5. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  6. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  7. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  8. Insightful Perspectives on This Subject by davidsycle, 2025-03-04 05:45
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  10. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05

Last-Modified Blogs