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 ]  

Problem encountered while flashing code to stm32f103c8t6 using st-link v2

Posted by Charan C on 2016-09-21 08:27 India

Hi, Please help me someone to overcome this problem.
In console I am getting this message

’

Open On-Chip Debugger 0.10.0-dev-00270-g7ec9836 (2016-05-18-14:26)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_assert_srst
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.245003
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Error: timed out while waiting for target halted
TARGET: stm32f1x.cpu - Not halted
in procedure ‘program’
in procedure ‘reset’ called at file “embedded:startup.tcl”, line 478
in procedure ‘ocd_bouncer’

    • Unable to reset target **

shutdown command invoked


’’

Reads: 7967
Link
Posted by lyphotoes on 2016-09-25 05:31

hi, i met the same problem ,and after read this pageQuestion, i had solved .


------------------------------
seems the simplest way to deal with this is to just use

reset_config none separate

Then the reset is done internally over the SWD channel with no pins used.

--------------------------
edit the *.cfg file in the project as below:

# use hardware reset, connect under reset
#reset_config srst_only srst_nogate
reset_config none separate

Link
Posted by Charan C on 2016-09-26 07:11 India

__edit the *.cfg file in the project as below:

  1. use hardware reset, connect under reset
  2. reset_config srst_only srst_nogate

reset_config none separate__


I edited the .cfg file as you mentioned, now problem is solved.

Thank you!

Link