STM32CubeIDE Debugger wont work with STM32MP1 DK2 with the 2.0 dunfell release.

[ADeck]

I cant seem to get the STM32CubeIDE to work with the STM32MP157C-DK2 board. It builds the examples and then when I go to load and debug i get the following:

Open On-Chip Debugger 0.10.0+dev-01193-g5ce997d (2020-02-20-10:57)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
cortex_a interrupt mask on
cortex_a interrupt mask on
cortex_a domain access control fixup on
cortex_a domain access control fixup on
none separate
adapter speed: 8000 kHz
adapter_nsrst_assert_width: 200
adapter_nsrst_delay: 200
none srst_pulls_trst
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 V2J36S26 (API v2) VID:PID 0483:3752
Info : using stlink api v2
Info : Target voltage: 3.231496
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 : SRST line released
Info : stlink_connect(connect)
Info : SWD DPIDR 0x6ba02477
Info : STM32MP157CAAx.cpu0: hardware has 6 breakpoints, 4 watchpoints
Info : STM32MP157CAAx.cpu1: hardware has 6 breakpoints, 4 watchpoints
Error: Could not find MEM-AP to control the core
Info : Listening on port 3334 for gdb connections
Info : Listening on port 3333 for gdb connections
ap 0 selected, csw 0x10006000
Info : accepting 'gdb' connection on tcp/3333
Error: Target not examined yet
 
 
Info : New GDB Connection: 1, Target STM32MP157CAAx.cpu2, state: unknown
undefined debug reason 7 - target needs reset
Error: Target not examined yet
Error: Target not examined yet
Error: Target not examined yet
Error: Target not examined yet
Error: Target not examined yet
Error: Target not examined yet
Error: Target not examined yet
Info : The target is not running when halt was requested, stopping GDB.
Warn : target STM32MP157CAAx.cpu2 is not halted (gdb fileio)
Error: Target not examined yet
Error: Target not examined yet
ap 0 selected, csw 0x10006000
shutdown command invoked
 
 
Info : dropped 'gdb' connection

if I set any type of break-point it complains about using too many break points (even if there is only one. If I go back to the 1.2 version release with the basic image it works fine. The basic image seems to have gone away in the 2.0 release so I have switched over to the trusted version. Is there something I need to do or enable? Is the trusted version preventing the debugger from working?

[Olivier GALLIEN · Accepted solution]

Hi @ADeck​ 

Sorry for inconvenience. This is a identified issue in our latest delivery.

​The fix is now published.

https://wiki.st.com/stm32mpu/wiki/STM32MP15_ecosystem_release_note_-_v2.0.0

https://wiki.st.com/stm32mpu/wiki/STM32MP15_OpenSTLinux_release_note_-_v2.0.0

some cipher methods have been disabled by the community for security reasons.

As a consequence some ssh requests from STM32CubeIDE may not be functional due to the dropbear package configuration.

In this case, you can either:

• refer to https://github.com/STMicroelectronics/meta-st-stm32mp/commit/36a9911705bd37df136e9ac51dbf418861d510c9
• or use the latest STM32MP1_Starter_Package_-_images : https://wiki.st.com/stm32mpu/wiki/STM32MP1_Starter_Package_-_images

Best Regards,

Olivier

[SAnto.3]

Hi @Community member​ 

I have the same issue.

However, I :

• Updated and flashed the starter package image to v2.0 (dunfell 20-06-24) with trusted tsv for STM32MP157C-DK2,
• Updated dropbear to version 2019.78-r2

... and still the same error log pops out on IDE when trying to debug OpenAMP_TTY_echo_CM4 project.

The last solution could be to modify recipes-core dropbear file ( https://github.com/STMicroelectronics/meta-st-stm32mp/commit/36a9911705bd37df136e9ac51dbf418861d510c9 ). Where and how this modification should be done ?

Thank you in advance,

Antoine

[Olivier GALLIEN]

Hi @SAnto.3​ ,

FYI the starter package you can get now on st.com contain the fix and should work out of the box.

If you still get the issue with it it's likely another issue.

In that case please create a new post and share some screenshots of your debug configuration and all error traces you get ?

Thanks

Olivier

[SAnto.3]

Hi @Community member​ 

It unfortunately didn't work... I created a new post with all the information here : https://community.st.com/s/question/0D53W00000LDFW2SAP/errors-in-openocd-when-debugging-starter-package-projects-in-stm32cubeide

Thanks for your reply.