Eclipse Community Forums: C / C++ IDE (CDT) » GDB Hardware Debugging problem

Home » Language IDEs » C / C++ IDE (CDT) » GDB Hardware Debugging problem(not connected to remote target)

GDB Hardware Debugging problem [message #1744116]

Thu, 22 September 2016 09:10

Eclipse User

Hi!
I need to debug C/C ++ code embedded devices based on STM32F4 on Eclipse NEON.
To do this, I select "GDB Hardware Debugging" with "Generic Serial" connection. But there is a problem when you connect to the target debug probe (BlackMagik).
session setup screenshot
www.klen.org/tmp/dbg.png

error widget screenshoot
www.klen.org/tmp/err.png

How to say CDT what need use a "extended-remote" target instead "remote"?
On Eclipse Mars i'm use GDB Hardware Debugging with Legacy mode and say any in GDB scripts and this work properly.

thanks!

Re: GDB Hardware Debugging problem [message #1786822 is a reply to message #1744116]

Sun, 13 May 2018 08:22

Eclipse User

I agree with Klen.
I was using Eclipse Mars and this would work, but now using Eclipse Oxygen I find that when selecting "GDB Hardware Debugging" and "Use remote target" with "generic serial" selected the command "-target-select remote" is automatically sent, where we need "target extended-remote " (i.e. -target-select extended-remote) to connect to a BlackMagic probe ("-target-select remote" will cause GDB to return "The target is not running (try extended-remote?)".
There doesn't seem to be any way to bypass or remove that wrong command.

Re: GDB Hardware Debugging problem [message #1786906 is a reply to message #1786822]

Tue, 15 May 2018 06:56

Eclipse User

Would it be possible for a developer to add a radio button to the Debugger tab of the GDB Hardware Debugging page to select between "target remote" and "target extended-remote"?

Previous Topic:	Set C++ Standart to C++17
Next Topic:	graph data on Eclipse console window to our computer

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 14:36:59 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter