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


You are viewing a reply to Project TARGET setting issues  

Project TARGET setting issues

France

Hello MSchultz,

My first guess is you should be able to proceed the way you want if updating target MCU you’re setting a board name too (even a dummy one but not empty one ! ). Sounds to me Apply / Ok is only considering target update if some board material (back even dummy one) is specified.

Please have a try and let us know if it works ok for you.

Br,
cartu38

Thank you for looking into this.

I can’t seem to find or remember what one has to do to create a new BOARD definition. I know I did this once before, but I found it by accident.

How do I go about creating a new board definition associated with a given MCU/target? I don’t need the whole process explained step-by-step (I can figure that out myself smile) I just need to know where to look for the “create new board” function.

France

Hello,

As far as I’m aware about the only way Thanks UI to create a new board is to create a new project. New project wizard is only integrated way to get right UI pop-up.

Such said there’s a handmade way to add a new board.
1) Locate your local System Workbench board repository (by default (if windows) = C:\Users\AppData\Roaming\Ac6\SW4STM32\board_def)
2) Add per custom board an .xml file, naming such file in sync. with board name you’re expecting (lower case file name is mandatory)
3) Such .xml (myboard.xml here) file looks like attached file (board id field has to be lower case – board name supports capitals – mcu id has to be lower case) :
4) Once done just restart System Workbench … your added board(s) should be seen as part of current db !


But back to your primary usage sounds to me strict new board creation is not mandatory (but you can ! … up to you). “Strict” stands for adding a board to system workbench db having capability to reuse it from one project to another and/or from one workspace to another. If my understanding is right you’re “only” looking to play with multiple build configurations within a project what’s not requiring such db update. Quick way for you is just to set per build configuration a unique “dummy” board name (typing it within board combo) within build settings target tab (see snapshot attached to such reply).


Back Thanks to share your trials outcomes it will help us !

Br,
cartu38


 

Newest Forum Posts

  1. Монтаж камина с грилем в Москве - установка и барбекю by KpddomErorb, 2025-05-10 18:28
  2. SPI on Nucleo_STMH533RE by royjamil, 2025-05-04 20:13
  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. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  9. Build a project in "release" mode by tang, 2025-02-20 10:36
  10. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35

Last-Modified Blogs