Re: Problem with remote debugging on 68K remote.

[jtc@redback.com (J.T. Conklin)]

>>>>> "Steven" == Steven W Orr <steveo@world.std.com> writes:
Steven> The jump command is correctly interpreted and the 68K target
Steven> successfully begins execution of its code.  Once the 68K
Steven> target has initialized, it prints out a login banner to the
Steven> console port and displays a prompt, where a user can then
Steven> issue commands to the target.  When connecting to the target's
Steven> console port via GDB, however, this login banner isn't
Steven> displayed by the GDB session on the Sun host.  We have
Steven> verified that the target is indeed displaying the login banner
Steven> by using a Y-cable setup on the console port, so that any
Steven> console port output is simultaneously sent to a dumb terminal
Steven> and the Annex 3 connection.

It sounds like you are using a single serial connection for both debug
protocol transport and console output.  For this to work, you need to
ensure that all console output is encapsulated in an 'O' response for
GDB to display it.  Otherwise, GDB will attempt your console output as
debug packets.

Steven> Years ago, a previous employee developed a similar capability
Steven> with a similar product of ours, this one based on the AMD 29K
Steven> processor.  The Annex connection method is the same.  The only
Steven> differences are that the AMD29K uses a different GDB stub in
Steven> the platform, and the host GDB program used at the time was
Steven> version 4.11 built for AMD Ebmon 29K.

You might want examine the stub and/or console I/O code on your 29k
product to see if it's encapsulating console output.

	--jtc

-- 
J.T. Conklin
RedBack Networks