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


Run/Debug problem in SW4STM32 using ST-Link/V2 SWD

I’ve just started using SW4STM32 and wrote a sample project to check it out but after setting up my board and its connection and a Run/Debug configuration I got this error when I want to deploy my program using ST-Link/V2 SWD:

Open On-Chip Debugger 0.9.0-dev-00415-g2d4ae3f-dirty (2015-06-12-17:54)
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
none separate
srst_only separate srst_nogate srst_open_drain connect_deassert_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 v23 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.261335
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

I can program the chip using every other tools I have on my computer like Keil and STM32 ST-LINK Utility pretty easy and I wasn’t expecting any problems at this stage!
ST-LINK has the latest firmware and I have installed the latest ST-LINK USB driver so I sort of blame SW4STM32.
Any thoughts?

Exactly, I have the same problem.
And i can not load and debug usig SW4STM32....
sad


Just make a copy of your project *.cfg file in the same directory and remove this phrase in your new file
srst_only
select the new file in the second tab of your project debug configuration instead of default *.cfg file and you’re good to go.

Thanks, this actually worked for me. I can now debug my custom board in sw4stm32 eclipse IDE

this is not working!!! me,too

I am developing a very important application using System workbench.

I can not tell you the number of times the debugger fails to load, it is constant. Why? Who knows. Why does it start working? Who knows. It just does.

This is a HUGE problem and from what I can tell no one seems to care in the least.

When I switched to Linux I thought perhaps it would work better, nope. Still just as bad.

My release was yesterday, and I can’t fix the problem because the debugger just says “Error erasing flash with vFlashErase packet”.

What does this mean? No one knows. How do I fix it? No one knows.

I have found that to get more information click the down-arrow next to the console icon, then select the gdb traces console, or the openocd console.

The openocd console says “Error: timed out while waiting for target halted”.

What does that mean? Dunno.

This is why it is free.

-Matt