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


Target connection fails with "Cannot identify target as a stm32x" (although STM32L053 works)

Hello,

You should use the Debug button but prior that you have to use menu “Debug as” => “AC6 C/C++ Application”.
After a correct debugging session, whenever you hit the debug button, it will debug the last debugged appli so it can be the wrong one.
You can select the appli to debug with the little arrow next to the debug button or wait over the button and see which appli will be debugged with the tooltip name.
ame.
Then, when you say the gdb console window is cleared and you see only the text of gdb, you have to switch to the openocd console to see the log.
There is a button on the rigth side of console window to switch window and choose the openocd one.


For the verbose mode of openocd, yes there is one, use the -d arg in openocd options text input in Debugger options tab in debug config window.
You’ll see a lot more text in openocd window and you might see which id it reads.
But there might be a lot of lines so you might have to remove the console buffer limit:
Go to menu Window => Preferences and Run/debug => Console and untick “Limit console output” and tick the 2 “show when program writes to standard out (and error)”.

For the connections, it seems they’re correct. Except VDDA, connect it to VDD or it is a typo ?
When you says “The Nucleo ST-Link Debugger is completely disconnected”, do you have broken the board ?
If yes, when you debug the nucleo L0, where do you connect the power ?
You take the 5V usb from dongle (where) and connect it to Vin (CN7-24) ?
So, no jumper at all on STlink side.

Another check is the script config file for openocd (cfg file), you should have created one with your custom board.
You should have a cfg file named with the project name on the bottom files of project in project explorer view.
Can you tell us which info are inside ?
You should have a swd transport selected to work (not JTAG that requires more pin and is not available on CortexM0 (STM32F0 or L0)).
And can you check in your “debug config” window in Debugger tab that this cfg filename is selected and “use local script” button is selected.

The cfg you made should contain these lines:
source find interface/stlink-v2-1.cfg
set WORKAREASIZE 0x2000
source find target/stm32f0x_stlink.cfg

Rgds,
Laurent