2023-01-02 01:11 AM
When i run my code, something wrong with the gdb (like in the picture). Someone can help me pls?
Solved! Go to Solution.
2023-01-05 02:18 AM
It is a normal behaviour when making run. If download is verified successfully, GDB session will be terminated that's why you see "terminated arm-none-eabi-gdb" in the debug window.
2023-01-02 01:44 AM
What's in the console?
2023-01-02 01:47 AM
It says download successfully, is it run properly or not (with terminated arm-none-eabi-gdb)??
2023-01-02 05:55 AM
Hello BAl K.1 ,
At first , let me thank you for reporting your issue.
Could you please supply the gdb server log-file? It will be created if option “Log to file�? is enabled in the debug settings.
Regards,
Rim
2023-01-02 07:31 PM
STMicroelectronics ST-LINK GDB server. Version 7.1.0
Copyright (c) 2022, STMicroelectronics. All rights reserved.
Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 31
Listen Port Number : 6123
Status Refresh Delay : 15s
Verbose Mode : Enabled
SWD Debug : Enabled
InitWhile : Enabled
COM frequency = 4000 kHz
Target connection mode: Under reset
Reading ROM table for AP 0 @0xe00fffd0
Hardware watchpoint supported by the target
ST-LINK Firmware version : V2J40M27
Device ID: 0x434
PC: 0x801d0dc
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.22 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Stm32Device, pollAndNotify running...
SwvSrv state change: 0 -> 1
Waiting for connection on port 6124...
Waiting for debugger connection...
Waiting for connection on port 6123...
Accepted connection on port 6123...
Debugger connected
Waiting for debugger connection...
Waiting for connection on port 6123...
GDB session thread running
GdbSessionManager, session started: 1
Accepted connection on port 6123...
Debugger connected
Waiting for debugger connection...
Waiting for connection on port 6123...
GDB session thread running
GdbSessionManager, session started: 2
Stm32Device, closeDevice() entry
GDB session, device event: 5
GDB session, device event: 5
Stm32Device, pollAndNotify stopped
Stm32Device, closeDevice() exit
------ Switching to STM32CubeProgrammer -----
-------------------------------------------------------------------
STM32CubeProgrammer v2.12.0
-------------------------------------------------------------------
Log output file: C:\Users\brama\AppData\Local\Temp\STM32CubeProgrammer_a12800.log
ST-LINK SN : 066AFF363355373043093915
ST-LINK FW : V2J40M27
Board : 32F469IDISCOVERY
Voltage : 3.22V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x434
Revision ID : Rev A
Device name : STM32F469xx/F467xx
Flash size : 2 MBytes
Device type : MCU
Device CPU : Cortex-M4
BL Version : 0x90
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a12800.srec
File : ST-LINK_GDB_server_a12800.srec
Size : 350.25 KB
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 6]
Download in Progress:
�������������������������������������������������� 0%
�������������������������������������������� 89%������ 100%
File download complete
Time elapsed during download operation: 00:00:06.721
Verifying ...
Read progress:
�������������������������������������������������� 50%
�������������������������������������������������� 100%
Download verified successfully
------ Switching context -----
COM frequency = 4000 kHz
Target connection mode: Under reset
Reading ROM table for AP 0 @0xe00fffd0
Hardware watchpoint supported by the target
ST-LINK Firmware version : V2J40M27
Device ID: 0x434
PC: 0x801d0dc
ST-LINK detects target voltage = 3.22 V
ST-LINK device status: HALT_MODE
GDB session, device event: 6
GDB session, device event: 6
Stm32Device, pollAndNotify running...
GDB session, device event: 3
GDB session, device event: 3
GDB session, device event: 1
GDB session, device event: 1
GDB session terminated: Client connection lost
GdbSessionManager, session terminated: 2
Received Ctrl-C from the client
ST-LINK device status: RUN_MODE
Device not halted(0), performing Ctrl-C
GDB session, device event: 4
Device halted
ST-LINK device status: HALT_MODE
GDB session, device event: 0
GDB session terminated: Client connection lost
GdbSessionManager, session terminated: 1
GdbSrv, last session terminated, signal dispose
Stopping port 6123
Received stop for port 6123, not accepting new connections.
GdbSrv, deInit entry.
Shutting down...
GdbSessionManager, deInit entry.
GDB session disposed: 2
GDB session disposed: 1
GdbSessionManager, deInit exit
SwvSrv deInit entry
Stopping port 6124
Received stop for port 6124, not accepting new connections.
SwvSrv deInit exit
Stm32Device, closeDevice() entry
Stm32Device, pollAndNotify stopped
Stm32Device, closeDevice() exit
Stm32Device, deInit success
GdbSrv, deInit exit.
Exit.
2023-01-02 07:32 PM
is that the gdb server log-file??
2023-01-03 06:42 AM
Hello BAl K.1,
Are you sure you are using the right debug button looks like you are using the run button?
2023-01-03 09:39 AM
Yes, i use run button, i want to run the code and that error appearing. is there any solution for that??
2023-01-05 02:18 AM
It is a normal behaviour when making run. If download is verified successfully, GDB session will be terminated that's why you see "terminated arm-none-eabi-gdb" in the debug window.