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


MacOS stm32f3discovery: impossible to load

Hello,
I’m working on a mac book pro 13 2017 (up to date on sofware and hardware). try to upload an empty software to my stm32f3discovery with SystelWorkbench AC6 from this web site, when I ‘run’ the COM led change color from red to green, but I have this error:

Wrong device detected, check your project and the board(s) connected
Open On-Chip Debugger 0.10.0-dev-00302-gc211ca5-dirty (2017-07-03-10:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 950 kHz
adapter_nsrst_delay: 100
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v28 API v2 M v18 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 2.903616
Warn : UNEXPECTED idcode: 0x2ba01477
Error: expected 1 of 1: 0x0bb11477
in procedure ‘program’
in procedure ‘init’ called at file “embedded:startup.tcl”, line 473
in procedure ‘ocd_bouncer’
** OpenOCD init failed **
shutdown command invoked

Could you help me, do you have any tutorial that works for MacOS?

Thank you

Based on the console output you’ve provided, it appears that you do not have your project configured to build for the right target MCU.

Navigate to Project -> Properties -> C/C++ Build -> Settings -> Target

Verify that the ‘board’ setting matches the board or MCU device you’re using.

There should be a pre-configured “board” definition for the STM32F3 Discovery, but I can’t say for certain because I’ve never tried selecting it.

In any event, the debugger is refusing to start up because the “idcode” of your target MCU does not match what the debugger is expecting to see.

I should mention that it is also obvious from the console output that the debugger is successfully communicating with the discovery board STLink, and is also successfully ‘contacting’ the target MCU, so I think it’s fairly safe to say that this is not a matter of mac (in)compatibility.

Thank you for your answers, so it means it is just a matter of configuration.... or a sofware bug maybe?
So I check again, on my board it is written:


what should I do/try?

Thank you


oh! I saw in Run configuration the target was wrong... so I delete again my project completely and make a new one with the good configuration and it works now ! cool, now I just erase the demo and I need to learn developping on stm32f3discovery


Thank you again


 

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