Cube IDE debug doesn't work on stm32mp157a-DK1

MBassi · ‎2020-10-23

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 : 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 : 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.

Olivier GALLIEN · ‎2020-10-29

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.

View solution in original post

Raggio · ‎2020-10-23

Thank you for the question Marco, I have your same problem when trying to start the debug session with CubeIDE.

I've successfully tried manual start of the demo application via "remoteproc" and also the debug in Reserved (Engineering) mode. But the Production Mode debug on the M4 won't start.

I hope someone could help us!

Raggio · ‎2020-10-27

Hi all, i still have the same problem, even with a fresh install of both the environment and IDE.

Anyone else is experiencing this problem or would help?

MBassi · ‎2020-10-27

Hi,

I also tryed using the cube IDE 1.4.2 for Ubuntu OS but I got the same debugging issue.

Hope someone could help

OHaza.1 · ‎2020-10-27

I have this issue too, I think it might be because the example is for the dk2 devboard which has a slightly different cpu but it's not clear

OHaza.1 · ‎2020-10-27

In the debugger options, under configuration script you can show the options and change connection speed to 4mhz.. this gets rid of that error but still has a target halted issue

Olivier GALLIEN · ‎2020-10-28

Hi @MBassi , @Raggio ,

This issue really looks like the known "STM32CubeIDE vs OpenSTLinux misalignement on “ciphers�? as highlighted in the "pin" post :

https://community.st.com/s/question/0D53W00000JQ4z4SAD/stm32mp1-ecosystem-known-bugs-and-common-pitfalls

Symptom : Prevent to load M4 firmware in Production mode

Seen in post : https://community.st.com/s/question/0D53W00000G1PG8SAN/update-stm32cubeide-version-142-stopped-sending-firmware-to-mpu

Starter package : fixed

Developper Package : not visible

Distribution package : Patch delivered on github

https://github.com/STMicroelectronics/meta-st-stm32mp/commit/36a9911705bd37df136e9ac51dbf418861d510c9

Can you pleas check ?

Thx

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 · ‎2020-10-28

Hi @Community member

Thanks for answer me, I read the posts you linked in your reply. I use a customized version of dunfell release, so I have to use the github link to download (I used git command) a patch file, but the file I get doesn't seem I patch file. I'm new in kernel recompiling so maybe I miss something about patching procedure,

please could you help me

Marco.

OHaza.1 · ‎2020-10-29

I managed to connect /run the program with breakpoints using a much lower connection speed in the khz range, started at the lowest and looking to see how high it can get as it's a bit slow to use at the lowest settings

MBassi · ‎2020-10-29

Thanks @OHaza.1

I tryed to lower connection down to khz speed but my issue remains.

I thinks the solution posted by Olivier could suit better my case, but I have to understand how to apply the changes on my dunfell costumized release.

At the moment I don't known where/how to apply the changes present in the github link: I can't use the repository directly because it's part of bitbake layers system but I use a differt compile chain