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


Connect to custom board STM32L053 - STLINK-V2 - SWD

Hi Kevin,

thanks for quick reply: I made what you suggested without more results but
here is the console log which is interresting:

Open On-Chip Debugger 0.9.0-dev-00101-g3a546c5 (2015-03-06-16:35)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : This adapter doesn’t support configurable speed
Info : STLINK v2 JTAG v21 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.218397
Info : stm32lx.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : accepting ‘gdb’ connection on tcp/3333
Info : STM32L flash size is 64kb, base address is 0x8000000
undefined debug reason 7 - target needs reset
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1015). Workaround: increase “set remotetimeout” in GDB
Error: timed out while waiting for target halted
TARGET: stm32lx.cpu - Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer’

in procedure ‘reset’
Error: timed out while waiting for target halted
TARGET: stm32lx.cpu - Not halted
in procedure ‘reset’
in procedure ‘ocd_bouncer’

in procedure ‘reset’

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


Something wrong in my connection ? That’s unlikely as it is ok with stlink-32 utility.
Do you have an idea how to halt the µc ?

Thanks and regards,
Sylvain

Workaround: increase “set remotetimeout” in GDB

Any pointers on why this happens and were we “set remotetimeout” in GDB with System Workbench?

I found the setting, just add the variable to the GDB tab on he project

Could you describe in detail where you entered this variable? I can not dismantle this warning.

Edit

when I use command in Debugger Console: “show remotetimeout”
I received answer: “Timeout limit to wait for target to respond is 2.”

Why in the message:
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (4517). Workaround: increase “set remotetimeout” in GDB
is the information about 1000ms?