Eclipse Community Forums: C / C++ IDE (CDT)

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » GDB / OpenOCD problem

Show: Today's Messages :: Show Polls :: Message Navigator

GDB / OpenOCD problem [message #1827574]

Mon, 18 May 2020 14:09

Diz P

Messages: 1
Registered: May 2020

Junior Member

HI,

Im having a problem with Eclipse and GDB/OpenOCD. Im trying to get GDB working with a MAX32660 Evaluation board on Ubuntu 18.04.

I am currently using xpacks
xpack-arm-none-eabi-gcc-9.2.1-1.1-linux-x64.tar.gz
xpack-openocd-0.10.0-13-linux-x64.tgz
20200127-1311-gnumcueclipse-4.7.2-2019-12-R-linux.gtk.x86_64.tar.gz

The debugger start but then fails with error quoted as

Error in final launch sequence
Failed to execute MI command:
load /home/jenkins/development/max32660/Hello_world_today/build/max32660.elf
Error message from debugger back end:
Error finishing flash operation
Failed to execute MI command:
load /home/jenkins/development/max32660/Hello_world_today/build/max32660.elf
Error message from debugger back end:
Error finishing flash operation
Error finishing flash operation

Ive since enabled the debug and capture the following from the console (see attachment).

Using the CLI ive started an openocd session and then telnet'd in which work up to that point.

I just cant figure out why this is not working with eclipse.

Any suggestions / help would be appreciated.

Stay safe..

Attachment: debug.txt
(Size: 203.28KB, Downloaded 171 times)

Report message to a moderator

Re: GDB / OpenOCD problem [message #1837629 is a reply to message #1827574]

Wed, 03 February 2021 13:06

poul flindt

Messages: 2
Registered: February 2021

Junior Member

The standard gdb that elicpse calls does not support all targets. You need to supply a gdb program from your toolchain in the debug setup.
Typically "arm-none-eabi-gdb".

Report message to a moderator

Re: GDB / OpenOCD problem [message #1837649 is a reply to message #1827574]

Wed, 03 February 2021 15:42

Tauno Voipio

Messages: 742
Registered: August 2014

Senior Member

There are several steps in Eclipse/GDB/OpenOCD connection:
- Eclipse to GDB using GDB/MI,
- GDB to OpenOCD using GDB remote,
- OpenOCD to target (probably) using JTAG

To debug the situation, you should take it step-by-step:
- Check OpenOCD and target using OpenOCD Telnet connection
from the console
- Check GDB to OpenOCD using GDB from console
- Last, Eclipse to GDB using MI

The error indications you have are telling that GDB
is not there or not understanding what you're attempting to do.

OpenOCD hints that you're doing cross-development for
an ARM target. The GDB has to be for an ARM target and
runnable on your host machine (PC?).

Please start by getting and reading the OpenOCD manual.

--

Tauno Voipio

Report message to a moderator

Previous Topic:	How to identify the specific include files Eclipse actually looked at trying to resolve the type?
Next Topic:	GDB hw debugging not uploading to target.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Oct 03 17:18:37 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter