Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32


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

Debug Issues in Mac OS X

It’s normal that you don’t find the UDEV things on Mac os, they are only for Linux os.

I don’t know if homebrew has installed enough stuff for stlink for SW4STM32.
Does it declare Stlink V2 and V2-1 ? They don’t have the same USB PID.

Did you create your project with the project wizard selecting the F407 disco board (which embeds an STlink V2) ?
Or you have created a custom board (selecting STLink V2 or V2-1) ?
If you have a project selecting an STlink V2-1 but an STlink V2 on your board, in v1.10.0, it should work anyway.
But it will work only if the 2 USB PIDs of the 2 STLink versions are declared.

I don’t know if there is a change in Mac os Sierra for USB drivers ?
The previous users on this thread were on Mac OS 10.11, not 10.12.

Rgds,
Laurent

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!

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!

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

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