[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

additional serial ports & Pilot cradle connection



I've added a serial port card to my PC and configured it with the
jumpers to use interrupts 5 and 2 for COM3 and COM4 respectively.
I've created the following /etc/rc.serial and made it executable:

    #!/bin/sh
    /bin/setserial /dev/ttyS2 irq 9
    /bin/setserial /dev/ttyS3 irq 5

During booting, I see the following:

    Linux version 2.0.30 (root pentagon gbhap com) (gcc version 2.7.2.1) #1 Fri Aug 8 17:29:03 BST 1997
    Serial driver version 4.13 with no serial options enabled
    tty00 at 0x03f8 (irq = 4) is a 16550A
    tty01 at 0x02f8 (irq = 3) is a 16550A
    tty02 at 0x03e8 (irq = 4) is a 16550A
    tty03 at 0x02e8 (irq = 3) is a 16550A
				[...]

Here are the results of a couple of diagnostics programs:

    [root pentagon robin]# setserial -bg /dev/cua[0-3]
    /dev/cua0 at 0x03f8 (irq = 4) is a 16550A
    /dev/cua1 at 0x02f8 (irq = 3) is a 16550A
    /dev/cua2 at 0x03e8 (irq = 2) is a 16550A
    /dev/cua3 at 0x02e8 (irq = 5) is a 16550A

    [root pentagon robin]# cat /proc/interrupts 
     0:     225724   timer
     1:       4125   keyboard
     2:          0   cascade
     4:      62365 + serial
    10:       8055   NE2000
    11:      35482 + aic7xxx
    13:          1   math error
    15:          0 + ide1

    [root pentagon robin]# cat /proc/ioports 
    0000-001f : dma1
    0020-003f : pic1
    0040-005f : timer
    0060-006f : keyboard
    0080-009f : dma page reg
    00a0-00bf : pic2
    00c0-00df : dma2
    00f0-00ff : npu
    0170-0177 : ide1
    02e8-02ef : serial(set)
    02f8-02ff : serial(auto)
    0320-033f : NE2000
    0376-0376 : ide1
    03c0-03df : vga+
    03e8-03ef : serial(set)
    03f0-03f5 : floppy
    03f7-03f7 : floppy DIR
    03f8-03ff : serial(auto)
    6100-61be : aic7xxx

    [root pentagon robin]# ls -l /dev/cua[0-3] /dev/ttyS[0-3]
    crw-rw----   1 root     uucp       5,  64 Nov 25 16:37 /dev/cua0
    crw-------   1 root     uucp       5,  65 Nov 25 16:04 /dev/cua1
    crw-------   1 uucp     uucp       5,  66 Nov 25 16:24 /dev/cua2
    crw-rw----   1 uucp     uucp       5,  67 Jan  1  1980 /dev/cua3
    crw-r--r--   1 root     root       4,  64 Jan  1  1980 /dev/ttyS0
    crw-------   1 root     root       4,  65 Nov 25 17:23 /dev/ttyS1
    crw-------   1 uucp     uucp       4,  66 Nov 25 17:21 /dev/ttyS2
    crw-r--r--   1 root     root       4,  67 Nov 25 17:22 /dev/ttyS3

Right, now that's over, time for the problem.  With the cradle plugged
into /dev/ttyS1 everything works fine:

    [root pentagon robin]# pilot-xfer /dev/ttyS1 -l
    Waiting for connection on /dev/ttyS1 (press the HotSync button now)...
    Connected
    Reading list of databases...
    'Unsaved Preferences'
    'Saved Preferences'
    'Graffiti ShortCuts'
    'Net Prefs'
				[...]
    List done.

With the cradle plugged into /dev/ttyS[23] I get the following:

    [root pentagon robin]# pilot-xfer /dev/ttyS2 -l
    Waiting for connection on /dev/ttyS2 (press the HotSync button now)...
		[...nothing, then Pilot times out...]

Incidentally, it doesn't seem to make any difference whether I use
ttyS[0-3] or cua[0-3].  What's going wrong here, and how can I fix
it?
  I'd like to get a PPP connection to the Pilot up and running as
well -- perhaps this would provide better diagnostics than the
HotSync?

-- 
 Robin Stephenson
 For Comfortable And Safe Use, Please Read The Safety & Comfort Guide



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]