Skip to main content
MHerz.1
Associate II
September 12, 2023
Question

STM32 MP157 SSH Debugging

  • September 12, 2023
  • 3 replies
  • 3581 views

Hello, I currently working with a STM32MP157D-DK1 Development Board. I populated the board with a prebuild openstlinux 6.1 build. A SSH connection via console is successful.

To get the M4 microcontroller running I was able to build a .elf file from the GPIO_EXTI example given by the STM32Cube_FW_MP1_V1.6.0. The .elf can be uploaded into the /boot/ directory via the scp command. By configuring Boot From an SD Card the M4 starts running an executes the just uploaded .elf file.

In order to debug the software I want to use the STM32CubeIDE Debug Configuration 'thru Linux core (Production mode)'. Unfortunatly I'm not able to connect my board with the given Target status widget, which is necessary for a successful connection build up. When i try to connect my board via the "Connections" Window -> right click SSH setup -> "Open Connection", I get the following generic error: 

"

Error opening connections
Session.connect: java.net.ConnectException: Connection timed out: connect

"

Creating a connection by clicking "Open Command Shell" works aswell. Trying to Debug and Flash via the ST-Link USB Connection works without any problems. Has anyone an idea where the problem is hidden?

Firmware: 

  • stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21

Programm Switch:

  • 1 = ON
  • 2 = ON

STM32CubeIDE 

  • Version: 1.13.1
  • Build: 17479_20230728_0839 (UTC)

Setup

  • Ethernet Cable connected (SSH via Console approved)
  • Power Supply enabled

SSH Config Propertys:

  • Host : 192.168.2.99
  • User: root
  • Public Key based authentication: enabled
This topic has been closed for replies.

3 replies

MHerz.1
MHerz.1Author
Associate II
September 15, 2023

Is any information missing? Can anyone help?

MHerz.1
MHerz.1Author
Associate II
September 26, 2023

Still unresolved.

debugging
Lead
October 5, 2023

https://www.st.com/resource/en/product_training/STM32MP1-Ecosystem-Trace_and_debug.pdf

Does not show a path to debug the M4 via network. Network debugging to the kernel requires GDB. Perhaps this pdf gives some hints.