[cdt-debug-dev] Cross debugging for embedded target via BDM

[Leon Pollak <leonp@xxxxxxxxx>]

Hello, great people of CDT.
	Today I finally managed to compile and link my cross project: Eclipse in 
Linux RH9 for PowerPC embedded target. And I started attempts to run 
debugger.
	I changed file plugins/org.eclipse.cdt.debug.mi.core_1.0.0/plugin.xml as 
found in newsgroup:
> > change the lines
> >     cpu="native"
> > into
> >     cpu="native,ppc"
	and created local configuration with ppc-gdb and my .gdbinit. First I tested 
that everything works in plane ppc-gdb (text mode). Then I run 'Debug' in 
Eclipse. The result is the only message I received:

Failed Launching CDI debugger: Error Initializing: Target is not responding 
(timed out).

and the Eclipse stays in 'waiting' mode - the red ball in the left-low corner 
continues to roll.
	
	I checked (using commands like 'shell echo PointN >log') that my start script 
executes up to its end successfully.

The possible problem may be that I work via BDM (background debug mode - a 
specific HW for debugging in my MPC860) and it takes some time to load the 
executable (about 5-7sec). But when I work in place gdb, I receive the 
download protocol, which I do not receive in Eclipse at all. 
	So, my questions are:

1. Where the gdb output goes to? (Why I do not see it in console window?)
2. How can I increase the Eclipse's time out variable
3. CDT user FAQ suggests fro embedded debugging to use 'remote' target. I 
think that this is not applicable in the case of BDM, but may be I am wrong?

Many thanks ahead for any help.

-- 
Dr.Leon M.Pollak
leonp at plris dot com