2020-08-24 03:27 AM
hi,
i updated STM32CubeIDE
to
Version: 1.4.2
Build: 7643_20200813_1322 (UTC)
and now the debug session doesn't send the compiled firmware to the target and just starts the gdb connection :
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.198425
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
Info : The target is not running when halt was requested, stopping GDB.
Warn : target STM32MP157CAAx.cm4 is not halted (gdb fileio)
Warn : target not halted
shutdown command invoked
Info : dropped 'gdb' connection
How can i fix that?
Solved! Go to Solution.
2020-08-24 03:54 AM
Hi @SMich.1
Sorry for inconvenience. This is a identified issue in our latest delivery.
As per already reported in previous post https://community.st.com/s/question/0D53W00000DGXEXSA5/stm32cubeide-debugger-wont-work-with-stm32mp1-dk2-with-the-20-dunfell-release
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:
Olivier
2020-08-24 03:54 AM
Hi @SMich.1
Sorry for inconvenience. This is a identified issue in our latest delivery.
As per already reported in previous post https://community.st.com/s/question/0D53W00000DGXEXSA5/stm32cubeide-debugger-wont-work-with-stm32mp1-dk2-with-the-20-dunfell-release
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:
Olivier
2020-08-24 04:00 AM
so the problem are in dunfell release ? not in the ide ?
I building dunfell for custom machine so if i understand right i should add to the dropbear : PACKAGECONFIG_remove = "disable-weak-ciphers"PR = "r1" ?
2020-08-24 04:23 AM
It's an unforeseen compability break between STM32CubeIDE and dunfell.
Waiting for proper fix in STM32CubeIDE we have temporary decided to workaround this on dunfell side. ( faster)
Seems you understand correctly patch to apply to your distribution.
Olivier
2020-08-24 04:45 AM
tnx, worked
2020-08-31 02:10 AM
Hi,
I have a similar problem.
I try run example from wiki for STM32MP157C-DK2: OpenAMP_TTY_echo.
This is my log from CubeIDE (ver. 1.4.0)
----------------------------------------------------------------------------------------------------
Open On-Chip Debugger 0.10.0+dev-g30d1303 (2020-06-18-09:11)
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.217357
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
Warn : target not halted
shutdown command invoked
Info : dropped 'gdb' connection
----------------------------------------------------------------------------------------------------
1. I use the latest STM32MP1_Starter_Package_-_images: en.FLASH-stm32mp1-openstlinux-5-4-dunfell-mp1-20-06-24.tar.xz (FlashLayout_sdcard_stm32mp157c-dk2-trusted.tsv).
2. I update the drobpear package on the STM32MP1 board:
----------------------------------------------------------------------------------------------
root@stm32mp1:~# apt-cache policy dropbear
dropbear:
Installed: 2019.78-r2
Candidate: 2019.78-r2
Version table:
*** 2019.78-r2 500
500 http://packages.openstlinux.st.com/2.0 dunfell/updates armhf Packages
100 /var/lib/dpkg/status
----------------------------------------------------------------------------------------------
But I can not sending Firmware to MPU.
How do I run this example from the wiki
2020-08-31 02:58 AM
You sure 2019.78-r2 that this is the version with update?
2020-08-31 03:14 AM
Yes. I use commands from release note: https://wiki.st.com/stm32mpu/wiki/STM32MP15_ecosystem_release_note_-_v2.0.0#Main_restrictions (5.1.1 OpenSTLinux (Cortex®-A7)).
Before update was:
Installed: 2019.78-r1
Candidate: 2019.78-r2
2020-08-31 04:15 AM
Hi @AZele.2
It should work properly with the 2019.78-r1 integrated by default.
Did you/could you test it ?
I will have a further look for the issue with r2.
Thx
Olivier
2020-08-31 08:26 PM
I solved part of the problem after installing CubeIde 1.4.0 on Windows 7 operating system (all work).
Before that I used Ubuntu 18.04 (Virtual Box)
It looks like a problem in using Virtual Box.