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


Error when trying to initiate debug on stm32f1038tx using stlink v2 using OpenSTM32

Warn : Could not determine executable path, using configured BINDIR
console dump

Open On-Chip Debugger 0.10.0-dev-00011-g46c94c8 (2018-09-06-08:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Warn : Could not determine executable path, using configured BINDIR.
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_nsrst_delay: 100
adapter speed: 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : vid/pid are not identical: 0x0483/0x374B 0x0483/0x3748
Info : using stlink api v2
Info : Target voltage: 3.255541
Info : STM32F103C8Tx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting ‘gdb’ connection on tcp/3333
adapter speed: 950 kHz
Error: timed out while waiting for target halted
TARGET: STM32F103C8Tx.cpu - Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer’



Info : device id = 0x20036410
Info : flash size = 64kbytes
adapter speed: 950 kHz
Error: timed out while waiting for target halted
TARGET: STM32F103C8Tx.cpu - Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer’



Error: Target not halted
Error: failed erasing sectors 0 to 2
Error: flash_erase returned -304

debug config

  1. This is an genericBoard board with a single STM32F103C8Tx chip
  2. Generated by System Workbench for STM32
  3. Take care that such file, as generated, may be overridden without any early notice. Please have a look to debug launch configuration setup(s)


source find interface/stlink.cfg

set WORKAREASIZE 0x5000

transport select “hla_swd”

set CHIPNAME STM32F103C8Tx
set BOARDNAME genericBoard

  1. Enable debug when in low power modes

set ENABLE_LOW_POWER 1

  1. Stop Watchdog counters when halt

set STOP_WATCHDOG 1

  1. STlink Debug clock frequency

set CLOCK_FREQ 4000

  1. use hardware reset, connect under reset
  2. connect_assert_srst needed if low power mode application running (WFI...)

reset_config srst_only srst_nogate connect_assert_srst
set CONNECT_UNDER_RESET 1

source find target/stm32f1x.cfg

Hi,

Most probably due to the fact that you didn’t connect reset from STlink.

Without reset, you can try to change the reset config in debugger tab to “software system reset”.

Or connect reset line and retry with your actual config.

Rgds,
Laurent