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


how the variable of openstm32_compiler_path been set?

Hi,
For some reason I want to try alternative toolchain, likely different version of gcc for embedded arm, openOCD.
By searching around, it seems like the most easiest way is to change openstm32_compiler_path to point to new installed alternative version of GCC.
So, the question is, where and how the original openstm32_compiler_path been set? How I can change it?

Thanks for help.
-BNow

Hello,

I don’t really answer your questions but there is a new version available.
You can update the plugins, menu Help => Check for Updates, to version 1.11.0.

The gcc arm tools have been updated to the release 5.4 of 2016q2. (gcc exe at 5.4.1 version)

Also, you can choose the eclipse option to directly show new version available :
In menu Window => Preferences => Install/Update => Automatic Updates => Tick “Direcly show update wizard” option (the last one).
This option is not available before eclipse Luna version.

Rgds,
Laurent

Hi Laurent,
Thanks for your information. I will try to update.
But I’m be more intrested to, how I can be flexible to chose between version of toolchain? I wouldn’t be swiching toolchain backing forth on daily basis, but in some situation, I want to compare and test.
Any thought or suggestion?
Thanks,
-BNow


Eclipse variables such as openstm32_compiler_path can be changed by opening the property dialog (Project -> Properties) then selecting C/C++ Build -> Build Variables

Make sure to check the “Show System Variables” option on the bottom of the dialog.

I tried editing the variable mentioned above (which was marked as a “ECLIPSE DYNAMIC VARIABLE”) to point to a different location for the ARM GCC tools, the override was accepted, and shows in the Build Variables dialog with the changed value, but it did not appear to “take”; the AC6-bundled tools were still used.

It is possible that you might have to edit the PATH (same dialog) since the path to the AC6-provided toolchain appears here as well. I did not take my own experimentation that far.

I had reached the same point but can’t move further more.
I suspect that the “ECLIPSE DYNAMIC VARIABLE” means the eclipse will supply the value of variable at the moment it needed. So that is why seems changing the value doen’t do any thing.
I was wondering if AC6 guys could help on this?


 

Newest Forum Posts

  1. reservation car service Seattle by Jamesprede, 2025-05-01 10:06
  2. Last day: drone bonus by Danielrug, 2025-04-19 16:55
  3. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  4. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  5. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  6. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  7. Insightful Perspectives on This Subject by davidsycle, 2025-03-04 05:45
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  9. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  10. Build a project in "release" mode by tang, 2025-02-20 10:36

Last-Modified Blogs