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

Forum List Topic List

[ prev topic ]  

MacOS stm32f3discovery: impossible to load

Posted by kboo on 2017-07-09 18:23

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

Reads: 6390
Link
Posted by MSchultz on 2017-07-12 02:38

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.

Link
Posted by MSchultz on 2017-07-12 02:41
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.
Link
Posted by kboo on 2017-07-14 11:42

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

Capture d’écran 2017-07-14 à 11.42.30.jpg (616.32 Kb)
Link

Posted by kboo on 2017-07-14 12:33

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

Link