Re: irda on the ipaq shell

Gday,

I suspect my ignorance of minicom (et al) is coming to the fore here,
as I had no results at all using the method below (I'll investigate later).
However, the main problem I have with this method is there is no way
of finding out where the error is:
ie. I can't tell if the ipaq is sending data, or if the laptop is
receiving/interpreting properly.
I'd like to be able to have something similar to irdadump as a
sanity check. My old method of testing serial mice didn't work
(ie. cat /dev/ttyS1) with a "cat: /dev/ttyS1: Input/output error".
Any easy way of passively watching the comm in tandem with minicom?
Do I need to initiate anything in minicom?

Have got job callout, back later.

Marcus.

> On Sun, 01 Feb 2004 10:18:22 +0100
> Danny Norging <danny.norging_at_gmx.de> wrote:
>
> > <on the ipaq side>
> > / # cat /dev/ttyS2
> > <on the pc side>
> > barney ~ # lsmod |grep ir
> > sir_dev 18348 0
> > irda 201528 1 sir_dev
> > barney ~ # watch "echo hi tux > /dev/ttyS1"
> Ok, now you must do the following:
>
> /etc/init.d/irda stop
> rmmod sir_dev
> rmmod irda
>
> Yes, you must remove ALL the drivers that use the /dev/ttyS1 port on
> your PC, otherwise minicom will not get or will get incomplete data.
>
> Now start minicom and setup it so that it uses /dev/ttyS1, no flow
> control, 115200, 8N1. Finally, add to the kernel command line:
>
> console=ttyS2,115200n8
>
> This *must* work.
>
> --
> Greetings,
> Andrew
> _______________________________________________
> H2200-port mailing list
> H2200-port_at_handhelds.org
> https://handhelds.org/mailman/listinfo/h2200-port
Received on Tue Feb 03 2004 - 02:52:56 EST