Firewire blues

[Gerald Heinig]

Gerald Heinig wrote:
>>
>>
>> I recall some issues with gdb and firewire as a module that may or may
>> not be fixed.
>> I recommend to put the dcons into the kernel to avoid any problems.
> 
> 
> I tried that too. There are a few additional flags that can be set. Of 
> particular interest are DCONS_FORCE_CONSOLE and DCONS_FORCE_GDB. I 
> presume I should set FORCE_CONSOLE to 1 if I want a console over 
> firewire, am I right?
> I'll take a look and see if there are any bugfixes for firewire.

It turns out that you need to set DCONS_FORCE_CONSOLE to 1 if you want 
to have a remote console over firewire.
I've got my link working with firewire now, but unfortunately I still 
can't get kgdb to connect.

If I do the following on the debugging machine:

kgdb -r /dev/fwmem0.0 kernel.debug

I get:

[general gdb stuff]
Switching to remote protocol
get_tty_state failed: Invalid argument
set_tty_state failed: Invalid argument
get_tty_state failed: Invalid argument
set_tty_state failed: Invalid argument
Couldn't establish connection to remote target
Reply contains invalid hex digit 12

When doing this, the remote machine's kernel wqas compiled with devices 
dcons and dcons_crom and options DCONS_FORCE_GDB=1

Any ideas?

Cheers,
Gerald