Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Embedded Debugging for Motorola 68332 with gdb-5.3 + bdm

I did not get much (any) response on the newsgroup yet, though I'll try on
this ML in the hope, someone might give me any hint I'm doing wrong.


I'm trying to get the gdb-5.3 running from Eclipse
3.0/CDT2.0.0_200404160300. My gcc-compiler generates coff-files for the
Motorola 68332/376.

I have the gdb running on the console, where I need to call a defined
init-routine 'initminpac' to initialize the uP.

I call it like:
C:\cygwin\m68k-gdb5\m68k-bdm-elf-gdb --command=gdb.ini main.coff
(gdb) initminipac
(gdb)
Then I can do an
(gdb) b main.c
(gdb) run main.coff

which will download the file and run it up to main entry.

How would I start the process in CDT Debug Session?

I tried the 'Cygwin GDB Debugger' with the gdb path set as above and the
command file set to gdb.ini. It will take a while until an error message
comes up saying that the target does not respond. Btw., 'GDB Server' would
just return an broken pipe error in the .log and afterwards the same about
no response. 

!ENTRY org.eclipse.cdt.debug.core 4 1000 Apr 30, 2004 17:26:56.592
!MESSAGE Internal error logged from CDI Debug:
!STACK 0
org.eclipse.cdt.debug.mi.core.cdi.MI2CDIException:
!src.MISession.Target_not_responding! 

I read about other developers setting up for other architectures. All had to
add to Elf.java something about E_MACHINE or such. I wonder if this is also
true for COFF files? Any help is appreciated, since I want to get away from
the rather instable Insight.


-- 
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl



Back to the top