cancel
Showing results for 
Search instead for 
Did you mean: 

Cube IDE debug doesn't work on stm32mp157a-DK1

MBassi
Associate III

Hi,

I'm having an issue while trying to debug the OpenAMP_TTY_ECHO_CM4 example described in gettin' started guide for stm32mp157a-DK1 (here link) using Cude IDE 1.4.2 on windows 10 machine. I configure the debug session as describe in the guide section 7, but when I started it, I got the following messages:

Open On-Chip Debugger 0.10.0+dev-g30d1303 (2020-06-18-09:13)

Licensed under GNU GPL v2

For bug reports, read

   http://openocd.org/doc/doxygen/bugs.html

srst_only srst_pulls_trst srst_gates_jtag srst_open_drain connect_deassert_srst

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : STLINK V2J37M26 (API v2) VID:PID 0483:3752

Info : Target voltage: 3.220093

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : clock speed 4000 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x6ba02477

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x6ba02477

Info : STM32MP157CAAx.cm4: hardware has 6 breakpoints, 4 watchpoints

Info : STM32MP157CAAx.cpu0: hardware has 6 breakpoints, 4 watchpoints

Info : STM32MP157CAAx.cpu1: hardware has 6 breakpoints, 4 watchpoints

Info : STM32MP157CAAx.cm4: external reset detected

Info : starting gdb server for STM32MP157CAAx.cpu0 on 3334

Info : Listening on port 3334 for gdb connections

Info : starting gdb server for STM32MP157CAAx.cm4 on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : Halt timed out, wake up GDB.

Error: timed out while waiting for target halted

Error executing event gdb-attach on target STM32MP157CAAx.cm4:

Info : New GDB Connection: 1, Target STM32MP157CAAx.cm4, state: reset

Warn : negative reply, retrying

Warn : negative reply, retrying

Warn : target not halted

Info : target STM32MP157CAAx.cm4 was not halted when resume was requested

When I reopen a serial console on cube IDE to run the test (according to guide section 8), I can't find any /dev/ttyRPMSG0 or /dev/ttyRPMSG1 device.

Please someone could help?

Marco.

11 REPLIES 11

Hi @MBassi​ ,

Straight forward solution is to download again the starter package from st.com and reflash it on board.

Second solution is to update dropbear version on target using apt-get service as per advice here :

https://wiki.st.com/stm32mpu/wiki/STM32MP15_OpenSTLinux_release_note#Main_restrictions_list

Third solution is application of the patch and generation of a new image using Distribution package.

https://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_Package

Hope it help,

Olivier

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
MBassi
Associate III

Thanks @Community member​ the second solution suits my case: now I can use Cube IDE debugger (production mode) on my dunfell customized.

Marco