MC 68040 debugging via JTAG with gdb?

Hello all,

is it possible to debug a Motorola MC 68040 via JTAG?
I'm looking for a cheap way to debug software in MC 68040 via PC.
gdb would be perfect.
Something like macraigor OCDRemote but for this processor.

greetings
Carsten
-- 
http://learn.to/quote - richtig zitieren
http://www.realname-diskussion.info - Realnames sind keine Pflicht
http://oe-faq.de/ - http://www.oe-tools.de.vu/ - OE im Usenet
http://www.spamgourmet.com/ - Emailadresse(n) gegen Spam

> is it possible to debug a Motorola MC 68040 via JTAG?

I don't believe the 68040 has a JTAG port. All the hardware debuggers
I'm aware of for this processor are full ICEs that totally replace the
CPU.

If you want to use gdb on this processor, you will need to port gdb
stubs (I find it hard to believe that nobody has done this before...)
and connect over serial, Ethernet or whatever other interface is
readily available in your target system.

larwe@larwe.com (Lewin A.R.W. Edwards) wrote:

>I don't believe the 68040 has a JTAG port.

It has, but I don't know which software is needed to use it.

>If you want to use gdb on this processor, you will need to port gdb
>stubs 

What is a stub?

greetings
Carsten
-- 
http://learn.to/quote - richtig zitieren
http://www.realname-diskussion.info - Realnames sind keine Pflicht
http://oe-faq.de/ - http://www.oe-tools.de.vu/ - OE im Usenet
http://www.spamgourmet.com/ - Emailadresse(n) gegen Spam

Carsten Krueger wrote:
> larwe@larwe.com (Lewin A.R.W. Edwards) wrote:
> 
> 
>>I don't believe the 68040 has a JTAG port.
> 
> 
> It has, but I don't know which software is needed to use it.
> 
> 
>>If you want to use gdb on this processor, you will need to port gdb
>>stubs 
> 
> 
> What is a stub?
> 

GDB stub is a piece of code in the target system. The stub
understands the GDB remote debugging protocol and functions
as the GDB's resident agent reading and setting register
contents, memory contents and breakpoints.

The stub functioning and structure is documented in the
GDB sources and documentation.

Googling 'gdb stub' gave about 43000 hits, at least the
first couple of pages fully relevant to the question.

-- 

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio <tauno.voipio@iki.fi.NOSPAM.invalid> wrote:

>GDB stub is a piece of code in the target system. The stub
>understands the GDB remote debugging protocol and functions
>as the GDB's resident agent reading and setting register
>contents, memory contents and breakpoints.

ok

>Googling 'gdb stub' gave about 43000 hits, at least the
>first couple of pages fully relevant to the question.

Thx, your abstract is much more clear than the hits (for me).

Interesting concept, but I don't know if I can use it. The problem is,
what do I do if my programm is crashed.
I think a stub is than "crashed", too.

greetings
Carsten
-- 
http://learn.to/quote - richtig zitieren
http://www.realname-diskussion.info - Realnames sind keine Pflicht
http://oe-faq.de/ - http://www.oe-tools.de.vu/ - OE im Usenet
http://www.spamgourmet.com/ - Emailadresse(n) gegen Spam

Carsten Krueger wrote:
> 
> Interesting concept, but I don't know if I can use it. The problem is,
> what do I do if my programm is crashed.
> I think a stub is than "crashed", too.

It depends.

If the stub is run interrupt-driven and the main code
crash did not succeed in destroying the interrupt
environment, you may still succeed in making a post-
mortem of the crash.

IMHO, the main use is in normal debugging, i.e. running
until a breakpoint, looking at variables, etc.

I have written a stub for ARM7TDMI and run it
successfully for a couple of years. As there are
graphic front-ends for GDB, it is actually a nice
debugging environment for an embedded system.

Regards from Helsinki, the home city of Linux.

-- 

Tauno Voipio
tauno voipio (at) iki fi

Tauno Voipio <tauno.voipio@iki.fi.NOSPAM.invalid> wrote:

>If the stub is run interrupt-driven and the main code
>crash did not succeed in destroying the interrupt
>environment, you may still succeed in making a post-
>mortem of the crash.

good idea

gdb has a stub for Motorola :-)
http://sources.redhat.com/gdb/current/onlinedocs/gdb_18.html#SEC156

These working remote stubs are distributed with GDB: 

i386-stub.c 
For Intel 386 and compatible architectures. 

m68k-stub.c 
For Motorola 680x0 architectures. 

sh-stub.c 
For Renesas SH architectures. 

sparc-stub.c 
For SPARC architectures. 

sparcl-stub.c 
For Fujitsu SPARCLITE architectures.

Thx for your hints.

greetings
Carsten
-- 
http://learn.to/quote - richtig zitieren
http://www.realname-diskussion.info - Realnames sind keine Pflicht
http://oe-faq.de/ - http://www.oe-tools.de.vu/ - OE im Usenet
http://www.spamgourmet.com/ - Emailadresse(n) gegen Spam

Carsten Krueger <cakruege@despammed.com> writes:
> is it possible to debug a Motorola MC 68040 via JTAG?

The MC68040 doesn't have any in-circuit-debug support.

Eric Smith <eric-no-spam-for-me@brouhaha.com> wrote:

>The MC68040 doesn't have any in-circuit-debug support.

Thx for this clear statement.

Gru&#4294967295; Carsten
-- 
http://learn.to/quote - richtig zitieren
http://www.realname-diskussion.info - Realnames sind keine Pflicht
http://oe-faq.de/ - http://www.oe-tools.de.vu/ - OE im Usenet
http://www.spamgourmet.com/ - Emailadresse(n) gegen Spam