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

Forum List Topic List

You are viewing a reply to problem with debugging the GPIO existing code on the stm32L4RG board  

problem with debugging the GPIO existing code on the stm32L4RG board

Posted by danilopucci on 2017-08-21 19:58

Hi Neham,

In your case, the STLink is embedded to your Nucleo board. On Nucleo board you can use the embedded STLink to program the MCU on Nucleo board or you can use your Nucleo board as a STLink.

Refer to this document (your Nucleo Board user manual)
http://www.st.com/content/ccc/resource/technical/document/user_manual/98/2e/fa/4b/e0/82/43/b7/DM00105823.pdf/files/DM00105823.pdf/jcr:content/translations/en.DM00105823.pdfQuestion

On section “6.2.3 Using the ST-LINK/V2-1 to program and debug the STM32 on board” and check if the jumpers is like described there. That jumpers make the connection between embedded STLink and the MCU (that is what I mean when said to you check the connection between STLink and MCU).

About your failed instalation of STLink Utillity on repo that you send (https://github.com/texane/stlink) on installation procedure is saying that this version is not compatible to Debian “For Debian Linux based distributions there is no package available in the standard repositories so you need to install from source yourself.”

But first try to check the jumpers, maybe it will solve your first issue.

For your second issue: everything looks OK on your screenshot... Reading the message from your first topic it looks like the GDB is not finding the debugger symbols

When looking at Project Explorer, do you have a “Debug” folder inside the workspace? It is created automatically and the debugger symbols is placed there after compile.

Reads: 1094
Link