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 two short videos (registration required) highlighting:

System Workbench for STM32

Forum List Topic List

[ prev topic ]  

Connect to custom board STM32L053 - STLINK-V2 - SWD

Posted by SyUm75 on 2015-05-04 17:13

Hi ST world,

I have issues connecting to a STM32L053 using openstm32.

The connection configuration is: STLINK-V2 // SWD

I’ve created a project with appropriate parameters and tried many configuration for the debug configuration (changing Mi protocol)

But I only could get this error at debug session start (stopping at 93 %):

””“”“”“””
Error in final launch sequence
Failed to execute MI command:
load C:\projects\micropos_proto1\Debug\micropos_proto1.elf

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Error erasing flash with vFlashErase packet
””“”“”“””

What did I do wrong ? Any ideas ?

For note, it’s possible to connect to my board using STLINK32 utility and flash/verify of the binary I want to debug was succesful.

Thanks and regards,
Sylvain

Reads: 75523
Link
Posted by tang on 2015-05-04 17:31

Hi Sylvain,

Can you verify that no debug session has been already launched. Go to the Debug perspectie (Windows > Open Perspective > Debug (or Other... > Debug)) then terminate every opened sessions.

Can you also check in the task manager if an openocd.exe is still runnning in background ? If it is, kill the openocd process.

Then relaunch the debug. If the same error is displayed, please copy the openocd process output (on the Debug perspective, select the openocd process under your debug session, the output should be displayed on the console view).

Regards,
Kevin.

Link
Posted by antish on 2016-09-20 07:28

Hi Kevin,

Had the same issue. And killing the process openocd.exe solved the problem.

Thanks
Antish

Link

Posted by SyUm75 on 2015-05-04 18:20

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

Link
Posted by brymat on 2015-05-05 00:00

Sylvain,

Ran into this same problem today with the STM32L051 (Funny coincidence). I modified the custom .cfg file in the following way:

  1. reset_config srst_only srst_nogate

reset_config srst_nogate

I had noticed the NRST line was toggling with the ST-LINK Utility but not with the debugger. Removing the ‘srst_only’ triggered the debugger to use the NRST line and everything started working.

I hope that helps,
Bryan

Link
Posted by adibacco on 2016-01-07 16:13
I had similar problem but then discovered that my NRST line from ST Link V2 was broken. I just replaced the wire and it started to work again.
Link
Posted by adibacco on 2016-01-14 13:46

Furthermore, I would suggest to select the right JTAG device, sometimes both an ST-LinkV2 and a ST-LinkV2-1 are present in the SystemWorkbench at the window whose screenshot is attached to this reply. If you select the wrong one, OpenOCD says “Error: open failed” and then eclipse says “Error message from debugger back end:
localhost:3333: The system tried to join a drive to a directory on a joined drive.
localhost:3333: The system tried to join a drive to a directory on a joined drive.”

Screen Shot 2016-01-14 at 13.46.03.png (208.70 Kb)
Link
Posted by brotfl on 2016-05-15 10:20

Hello Bryan!

Apparently your solution works for other people, so I woiuld like to try it.
What do you mean by “I modified the custom .cfg”. I mean, where is this .cfg file?
Do I have to find a file named “.cfg”, starting with a . like some config files, or
is it a file like “openocd.cfg” with possibly another name?
I have tried ps -ax | grep openocd, but there is no reference anywhere.
Is it a file in the workspace?

Thanks,

Pascal

Link
Posted by GuyWilliamson on 2016-09-03 08:23

I am using the STM32L051 with the ST-LINK-V2

I seem to have this problem with the reset line - reset_config srst_only srst_nogate

I change the .custom.cfg file to remove srst_only

When I launch the debugger, it modifies the .custom.cfg file and puts it back

Where is this modification coming from?

Thanks in advance

Link
Posted by garryp on 2018-04-11 04:48

Hello,
May I know where is this custom.cfg file is located?
I am having the same problem
Thanks

Link
Posted by SUPERMOSFET on 2018-08-07 02:33

This fix has worked for me as well.
Here is a portion of my cfg file:


reset_config srst_nogate connect_assert_srst
set CONNECT_UNDER_RESET 1

Link
Posted by uCHobby on 2018-02-12 19:03

Workaround: increase “set remotetimeout” in GDB

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

Link
Posted by uCHobby on 2018-02-13 02:44
I found the setting, just add the variable to the GDB tab on he project
Link
Posted by pocztamix on 2018-06-14 10:41

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?

Link

Posted by SyUm75 on 2015-05-05 10:07

Hi Bryan,

it works perfectly with your solution.
Thanks !!

Sylvain

Link

Posted by hbomber on 2015-07-29 15:39
Thank you for this post. I was having the same problem and this fixed it!
Link

Posted by Andrey_13 on 2015-09-18 19:58

Hi ST world.
Wy project on stm32f415 worked with openocd 1.3. In after updating to version 1.4 it stopped work. Error:

Error in final launch sequence
Failed to execute MI command:
load D:\Work\Projects\Makett_105\STM32F415_ili9341\Debug\F415_ILI9342.elf

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Error erasing flash with vFlashErase packet

I modified the custom .cfg file in the following way:
reset_config srst_nogate


But did not achieve the result.

Thank you in advance

Link

Posted by SyUm75 on 2015-09-21 10:16

Hi Andrey,

you shoudl try to dig in .cfg files that are in the AC6 gcc eclipse plugin. And notably in .\eclipse\plugins\fr.ac6.mcu.debug_1.3.0.201507241045\resources\openocd\scripts\target\stm32F4.cfg file.

Some reset / connection options are set in it (line 86)
You should check it’s still what you want.

Hope that help,
Regards,
Sylvain

Link
Posted by AnderHyIs on 2016-07-01 14:42

Your’re spot on there, Sylvain.
That reference in the plugins folder (stm32fxx.cfg) overrides the one in the custom.cfg in the workspace -> I had same problem on different device.
Fixed it

Link
Posted by rose on 2017-06-03 01:17

I found also that you could also use the GUI to modify the .cfg file that is generated. I am posting the steps below in case they help anyone else:

  1. Right Click on the Project, Click Properties
  2. Click on “Run/Debug Settings”
  3. Select the pesky Launch Configuration that keeps generating with the srst_only in it & click “Edit”
  4. Click the “Debugger” Tab
  5. Go into the Configuration Script section and click “Show generator options...”
  6. Change the Reset Mode to “Software system reset” (or whatever change you’d like to make- this change fixed my errors)
  7. Click Apply
GuiConfigSettings.png (51.54 Kb)
GuiConfigSettings.png (51.54 Kb)
Link
Posted by jkstm32 on 2017-11-05 04:29
Very useful post. Thanks!
Link
Posted by mahmudzero on 2017-11-06 01:22

Well that changed some stuff for me. Now I’m getting the following:

Open On-Chip Debugger 0.10.0-dev-00005-g4030e1c-dirty (2017-10-24-07:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
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 v29 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : vid/pid are not identical: 0x0483/0x374B 0x0483/0x3748
Info : using stlink api v2
Info : Target voltage: 3.261782
Info : Stlink adapter speed set to 950 kHz
Info : STM32F030R8Tx.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : Stlink adapter speed set to 950 kHz
adapter speed: 950 kHz
STM32F030R8Tx.cpu: target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
in procedure ‘program’
in procedure ‘reset’ called at file “embedded:startup.tcl”, line 478
in procedure ‘ocd_bouncer’
in procedure ‘ocd_process_reset’
in procedure ‘ocd_process_reset_inner’ called at file “embedded:startup.tcl”, line 248
in procedure ‘STM32F030R8Tx.cpu’ called at file “embedded:startup.tcl”, line 370
in procedure ‘ocd_bouncer’

    • Programming Started **

auto erase enabled
Error: Cannot identify target as a stm32x
Error: auto_probe failed

    • Programming Failed **

shutdown command invoked

Link
Posted by LaurentL on 2017-11-06 10:04

Hello,

Which device are you trying to connect to ?
Because the post is for STM32L053 and your log is about a STM32F030.

If you’re trying to connect to a STM32L053, you have to select the right board and mcu in your project.

If it is indeed an F030, you can try to add -d in openocd options in debug config tab.
You will see which device is recognized or if an error is around.

Rgds,
Laurent

Link

Posted by jedrek1993 on 2015-10-11 17:41

Hello,
I have the same problem with connecting to STMF405.
I’ve tried everything above, but nothing helped.
All the time I got error:

Error in final launch sequence
Failed to execute MI command:
load “C:\STM32\test1\SW4STM32\test1 Configuration\Debug\test1 Configuration.elf”

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Error erasing flash with vFlashErase packet


Do you have any more suggestions?
Regards
Jedrzej

Link
Posted by barrytough on 2015-12-22 09:55

Do you solve the problem?
Error in final launch sequence
Failed to execute MI command:
load F:\STM32-Workspace\PX4Flow-SWD\Debug\PX4Flow-SWD.elf

Error message from debugger back end:
Error erasing flash with vFlashErase packet
Error erasing flash with vFlashErase packet

Link

Page: 1/3  [Next]
1  2  3