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


Debugging hangs with F3 discovery board [solved]

29 March 2015:
I fixed the below problem - the initially chosen port number (3333) was blocked internally in my computer (probably some setting pushed by our IT dept.). In the debug configuration, I changed the port used to 444, and now all debugging works perfectly!

_
I’m trying to start debugging of a simple project created by the New->Project wizard, which was told to build it for the STM32 Discovery board. When I try to Debug As->Ac6 STM32 C/C++ Application, GDB and OpenOCD start normally, but then hang. OpenOCD reports:

Open On-Chip Debugger 0.9.0-dev-00101-g3a546c5-dirty (2014-09-23-14:54)
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 v23 API v2 SWIM v0 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 2.904739
Info : stm32f3x.cpu: hardware has 6 breakpoints, 4 watchpoints

So it’s recognizing the target just fine. But after about a half minute, I start seeing this in the gdb traces console:

526,462 ~”Ignoring packet error, continuing...\n”
526,462 &”warning: unrecognized item "timeout" in "qSupported" response\n”
540,462 ~”Ignoring packet error, continuing...\n”
554,462 ~”Ignoring packet error, continuing...\n”
568,462 ~”Ignoring packet error, continuing...\n”
582,462 ~”Ignoring packet error, continuing...\n”
596,462 ~”Ignoring packet error, continuing...\n”
596,462 =thread-group-started,id=”i1”,pid=”42000”
596,462 =thread-created,id=”1”,group-id=”i1”
596,462 14-list-thread-groups --available
596,472 15-list-thread-groups
610,462 ~”Ignoring packet error, continuing...\n”
610,462 =thread-group-exited,id=”i1”
610,462 13error,msg=”Malformed response to offset query, timeout”
610,462 (gdb)
610,462 &”\n”
610,462 done

The flash never gets written, and the debugging operation never starts. After about 5 minutes, OpenOCD quits with a 1 result code. I used the ST-LINK utility to flash the on-board JTAG interface with the latest firmware, restarted Eclipse, and tried the same thing with identical results.

Any helpful suggestions would be welcome, thanks.