Skip to contentSkip to conversation

testing if connection with baycom modem works

DISCUSSION Folkert van Heusden 1 participant 3 messages Mar 4, 2007

lore
Share & tools
lore
#0 lore raw

Hi,

I have a baycom-modem connected to a serial-port and a 27mc radio. Now after some patching of the baycom_ser_hdx driver (it did now allow port addresses above > 0x1000) this runs without errors:

/bin/setserial /dev/ttyS3 uart none
/sbin/modprobe baycom_ser_hdx mode="ser12*" iobase=0xb808 irq=15 /usr/bin/sethdlc -i bcsh0 -p mode "ser12*" io 0xb808 irq 15

dmesg then says:

[5390108.456669] baycom_ser_hdx: (C) 1996-2000 Thomas Sailer, HB9JNX/AE4WA
[5390108.456675] baycom_ser_hdx: version 0.10 compiled 20:14:52 Mar  4 2007

and sethdlc output is:
/usr/bin/sethdlc: Version 0.5; (C) 1996-1997 by Thomas Sailer HB9JNX/AE4WA driver name: baycom_ser_hdx
current parameters: mode ser12* io 0xb808 irq 15
new parameters: mode ser12* io 0xb808 irq 15

I then do:
ifconfig bcsh0 10.0.0.1 netmask 255.0.0.0 hw ax25 fvh123-1 up multicast ifconfig bcsh0 broadcast 10.255.255.255 netmask 255.0.0.0

and after that I do ping 10.0.0.8 as a test.
Now the radio doesn't switch between receive and transmit every time it is supposed to send data. Also I added to the 'ser12_tx' function a prinkt-statement which is supposed to show a message when the pc is sending via that device: no output there.

So it seems something down the line is incorrect.

How can I debug these problems?

I verified that the rs232 cable is correct (all 9 pins are connected).

Folkert van Heusden

Signature · 9 lines
MultiTail er et flexible tool for å kontrolere Logfiles og commandoer.
Med filtrer, farger, sammenføringer, forskeliger ansikter etc.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw

To the function ser12_interrupt I added the following printk-statement:

        baycom_int_freq(bc);
        do {
printk(KERN_INFO "interrupt %d: %d\n", irq, iir & 6); /* THIS ONE */
                switch (iir & 6) {
                case 6:

Now all I see in dmesg is:

[5391104.760314] baycom_ser_hdx: (C) 1996-2000 Thomas Sailer, HB9JNX/AE4WA
[5391104.760322] baycom_ser_hdx: version 0.10 compiled 20:45:04 Mar  4 2007
[5391105.157757] baycom_ser_hdx: found 4 net devices
[5391110.879166] interrupt 15: 2
[5391110.879198] receive data blabla 1  <-- *1
[5391110.879235] baycom_ser_hdx: ser12 at iobase 0xb808 irq 15 uart 16550A
[5391110.889758] ADDRCONF(NETDEV_CHANGE): bcsh0: link becomes ready

*1: I added also a prinkt-statement to ser12_rx to see if anything comes in and ditto to ser12_tx.
And even when I ping no more extra debugging comes into dmesg. Also with or without audio from the radio going trough the baycom-modem: no receive, interrupt or transmit message passes by in dmesg.

Anyone got an idea what is going wrong here?

Quoted 30 lines · Folkert van Heusden

Hi,

I have a baycom-modem connected to a serial-port and a 27mc radio. Now after some patching of the baycom_ser_hdx driver (it did now allow port addresses above > 0x1000) this runs without errors:

/bin/setserial /dev/ttyS3 uart none
/sbin/modprobe baycom_ser_hdx mode="ser12*" iobase=0xb808 irq=15 /usr/bin/sethdlc -i bcsh0 -p mode "ser12*" io 0xb808 irq 15

dmesg then says:

[5390108.456669] baycom_ser_hdx: (C) 1996-2000 Thomas Sailer, HB9JNX/AE4WA
[5390108.456675] baycom_ser_hdx: version 0.10 compiled 20:14:52 Mar  4 2007

and sethdlc output is:
/usr/bin/sethdlc: Version 0.5; (C) 1996-1997 by Thomas Sailer HB9JNX/AE4WA driver name: baycom_ser_hdx
current parameters: mode ser12* io 0xb808 irq 15
new parameters: mode ser12* io 0xb808 irq 15

I then do:
ifconfig bcsh0 10.0.0.1 netmask 255.0.0.0 hw ax25 fvh123-1 up multicast ifconfig bcsh0 broadcast 10.255.255.255 netmask 255.0.0.0

and after that I do ping 10.0.0.8 as a test.
Now the radio doesn't switch between receive and transmit every time it is supposed to send data. Also I added to the 'ser12_tx' function a prinkt-statement which is supposed to show a message when the pc is sending via that device: no output there.

Quoted 15 lines

So it seems something down the line is incorrect.

How can I debug these problems?

I verified that the rs232 cable is correct (all 9 pins are connected).

Folkert van Heusden

Signature · 5 lines
MultiTail er et flexible tool for å kontrolere Logfiles og commandoer.
Med filtrer, farger, sammenføringer, forskeliger ansikter etc.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Folkert van Heusden

Signature · 8 lines
www.vanheusden.com/multitail - multitail is tail on steroids. multiple
               windows, filtering, coloring, anything you can think of
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw

Ok, I tried baycom_ser_fdx and this one seems to work!!
That is: when I ping, I see the radio going to 'tx'-status. Now only I have to find someone living near me (Gouda/The Netherlands) who can verify that my radio indeed is transmitting (need to find the squelch level and the volume of the radio) :-)
Oh and I need to find a traffic dumper capable of dumping data link type 3.

Quoted 75 lines · Folkert van Heusden

To the function ser12_interrupt I added the following printk-statement:

        baycom_int_freq(bc);
        do {
printk(KERN_INFO "interrupt %d: %d\n", irq, iir & 6); /* THIS ONE */
                switch (iir & 6) {
                case 6:

Now all I see in dmesg is:

[5391104.760314] baycom_ser_hdx: (C) 1996-2000 Thomas Sailer, HB9JNX/AE4WA
[5391104.760322] baycom_ser_hdx: version 0.10 compiled 20:45:04 Mar  4 2007
[5391105.157757] baycom_ser_hdx: found 4 net devices
[5391110.879166] interrupt 15: 2
[5391110.879198] receive data blabla 1  <-- *1
[5391110.879235] baycom_ser_hdx: ser12 at iobase 0xb808 irq 15 uart 16550A
[5391110.889758] ADDRCONF(NETDEV_CHANGE): bcsh0: link becomes ready

*1: I added also a prinkt-statement to ser12_rx to see if anything comes in and ditto to ser12_tx.
And even when I ping no more extra debugging comes into dmesg. Also with or without audio from the radio going trough the baycom-modem: no receive, interrupt or transmit message passes by in dmesg.

Anyone got an idea what is going wrong here?

Quoted 30 lines · Folkert van Heusden

Hi,

I have a baycom-modem connected to a serial-port and a 27mc radio. Now after some patching of the baycom_ser_hdx driver (it did now allow port addresses above > 0x1000) this runs without errors:

/bin/setserial /dev/ttyS3 uart none
/sbin/modprobe baycom_ser_hdx mode="ser12*" iobase=0xb808 irq=15 /usr/bin/sethdlc -i bcsh0 -p mode "ser12*" io 0xb808 irq 15

dmesg then says:

[5390108.456669] baycom_ser_hdx: (C) 1996-2000 Thomas Sailer, HB9JNX/AE4WA
[5390108.456675] baycom_ser_hdx: version 0.10 compiled 20:14:52 Mar  4 2007

and sethdlc output is:
/usr/bin/sethdlc: Version 0.5; (C) 1996-1997 by Thomas Sailer HB9JNX/AE4WA driver name: baycom_ser_hdx
current parameters: mode ser12* io 0xb808 irq 15
new parameters: mode ser12* io 0xb808 irq 15

I then do:
ifconfig bcsh0 10.0.0.1 netmask 255.0.0.0 hw ax25 fvh123-1 up multicast ifconfig bcsh0 broadcast 10.255.255.255 netmask 255.0.0.0

and after that I do ping 10.0.0.8 as a test.
Now the radio doesn't switch between receive and transmit every time it is supposed to send data. Also I added to the 'ser12_tx' function a prinkt-statement which is supposed to show a message when the pc is sending via that device: no output there.

Quoted 15 lines

So it seems something down the line is incorrect.

How can I debug these problems?

I verified that the rs232 cable is correct (all 9 pins are connected).

Folkert van Heusden

Signature · 5 lines
MultiTail er et flexible tool for å kontrolere Logfiles og commandoer.
Med filtrer, farger, sammenføringer, forskeliger ansikter etc.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
Quoted 7 lines

Folkert van Heusden

Signature · 4 lines
www.vanheusden.com/multitail - multitail is tail on steroids. multiple
               windows, filtering, coloring, anything you can think of
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Folkert van Heusden

Signature · 9 lines
To MultiTail einai ena polymorfiko ergaleio gia ta logfiles kai tin
eksodo twn entolwn. Prosferei: filtrarisma, xrwmatismo, sygxwneysi,
diaforetikes provoles. http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html