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

Forum List Topic List

You are viewing a reply to Debug Issues in Mac OS X  

Debug Issues in Mac OS X

Posted by danieljodeci on 2016-10-11 06:10

stlink does declare stlink v2 which is what my stm32discovery board is using.

I did create my own project with the project wizard selecting stm32f4discovery board, which I believe should embed sn STLink V2, although i’m not sure how to verify which version of stlink is embedded in my project.

also, how can i verify that my usb PIDs of my stlink version matches with my device?

Thanks!

Reads: 2245
Link
Posted by danieljodeci on 2016-10-11 07:02

Nevermind my last question, seems I have figured it out.

Solution was to change my stm32f4discovery.cfg file to use stlink-v2-1.cfg instead of stlink-v2.cfg.

Figured this out after finding my PID in the system report window within the About This Mac preference, and seeing that it did not match with the current PID configuration.

Thanks for your time and all the help Laurent!

Link
Posted by LaurentL on 2016-10-11 11:21

Hi Daniel,

Glad to hear it works fine finally.

In fact, you have the newer F407 disco and the name is different with the Stlink V2-1, it should be written STM32F407-DISC1 on the board.
Old F407 Discovery named STM32F4-discovery has a STLink V2.

So you have chosen the wrong board in SW4STM32.

I thought it would work specifying Stlink V2 or V2-1 in v1.10.0 version. I will check that again.

I re-read your post, you modified the cfg file but it’s not the right solution, because if you get an old F4-discovery, it would not work.
So, the solution is to change your board to STM32F407-DISC1 which has the cfg with STLink V2-1.

Rgds,
Laurent

Link
Posted by danieljodeci on 2016-10-11 19:14

Yup you were right. Thought I might have been using the wrong board configuration. Ok so I changed the stm32f4discovery.cfg back to how it was, and created a new project with stm32f407-disc1 and it still works.

Awesome!
Thank you

Link

 

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

  1. System Workbench for STM32