Sign in

Search rabbit-semi

Subscribe to rabbit-semi

Discussion Groups

Discussion Groups | Rabbit-Semi | PPP fails to connect second time around

This is a group for folks designing and programming embedded systems using the Rabbit Semiconductor C-programmable microcontroller. Rabbit Semi is a spin-off from Z-World who makes a variety of embedded modules and tools. This group is not affiliated with either Rabbit or Z-World, but is a user forum for sharing ideas, asking questions, flaunting knowledge, and other typical user group stuff. The Rabbit is a powerful uC, supported by a full-featured C-compiler.

PPP fails to connect second time around - Dave McLaughlin - Aug 31 6:23:02 2009

I have got my PPP problem resolved with regards to connecting but now I
can't get it to do it more than once.

Running under DynC 10.56 and using an RCM5450W I get connected and can send
data etc. If I disconnect and then try to connect again, the library gives a
no buffer space available error. Here is the debug output and you can see
the disconnect from the first connection, then it tries again and fails.

SERLINK: sendpacket using 000090B0
--- pkt flags=x40 i/f=0 tstamp=55555 len=5 ---
sect 1, len=5 addr=x001090D7 rlen=1568
41 54 48 0D 0A ATH
SERLINK: transmitter was idle
SERLINK: receive processed 1 chars
SERLINK: got raw packet len=1, chatting=hangup
SERLINK: receive processed 9 chars
SERLINK: got raw packet len=3, chatting=hangup
SERLINK: got raw packet len=2, chatting=hangup
SERLINK: got raw packet len=4, chatting=hangup
CHAT: found it!
CHAT: end of script
SERLINK: Closed PPP serial on iface 0
SERLINK: baud rate 57600: setting divisor to 39
SERLINK: bringing up serial PPP interface 0
SERLINK: baud rate 57600: setting divisor to 39
SERLINK: Opened PPP serial on iface 0 at 57600 baud
CHAT: sending 'ATZ'
SERLINK: starting modem escape sequence
SERLINK: sendpacket totlen=1 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=000000 rxxpkt=000000
SERLINK: sendpacket totlen=1 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=000000 rxxpkt=000000
SERLINK: sendpacket totlen=1 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=000000 rxxpkt=000000
If you don't enable debug the programme just appears to hang inside this
looping around.

I also noticed today that during the first connect that it attempts to
connect to the server to send data, it also gives this error after sending a
few packets.

Opening socket
TCP/IP Failed Open
SERLINK: sendpacket totlen=44 i/f 0
SERLINK: sendpacket using 0000B054
--- pkt flags=x40 i/f=0 tstamp=56414 len=44 ---
sect 1, len=44 addr=x0010B07B rlen=1529
FF 03 00 21 45 00 00 28 00 09 00 00 40 06 C1 10 !E ( @
72 7B D1 AB 76 89 FF 06 20 E7 13 8A 00 00 00 00 r{ v
00 00 00 00 50 04 04 00 BD B8 00 00 P
SERLINK: transmitter was idle
SERLINK: sendpacket totlen=48 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=100000 rxxpkt=10B6A8
p=108408 p->ll_flags=80 p->len=48
p=107DB4 p->ll_flags=80 p->len=48
p=108A5C p->ll_flags=80 p->len=48
p=1090B0 p->ll_flags=80 p->len=48
p=109704 p->ll_flags=80 p->len=48
p=109D58 p->ll_flags=80 p->len=48
p=10A3AC p->ll_flags=80 p->len=48
p=10AA00 p->ll_flags=80 p->len=56
p=10B054 p->ll_flags=80 p->len=48
p=10B6A8 p->ll_flags=00 p->len=10092
Opening socket
TCP/IP Failed Open
SERLINK: sendpacket totlen=44 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=100000 rxxpkt=10B6A8
p=108408 p->ll_flags=80 p->len=48
p=107DB4 p->ll_flags=80 p->len=48
p=108A5C p->ll_flags=80 p->len=48
p=1090B0 p->ll_flags=80 p->len=48
p=109704 p->ll_flags=80 p->len=48
p=109D58 p->ll_flags=80 p->len=48
p=10A3AC p->ll_flags=80 p->len=48
p=10AA00 p->ll_flags=80 p->len=56
p=10B054 p->ll_flags=80 p->len=48

Ignore the fact that it failed to connect, this is because my server was
down during the test. You can see the first part is OK, then it fails
similar to the redial. This indicates the fault lies in the PPP or SERLINK
driver.

Running under DynC 9.62 with an RCM3000 the same dialing and connecting code
works fine. Subsequent redials are also ok. This is using a different
library so I suspect the issue is with the new 4000/5000 series libraries
and the changes for PPP.

Regards
Dave..

(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: PPP fails to connect second time around - vivek gangwar - Aug 31 16:41:00 2009

Just Reinitialize to the socket driver then try to connect

////////////////////////////////////////////////////
try

sock_init_or_exit()
for Initialize the socket

then TCP_OPEN()

////////////////////////////////////////////
--- On Mon, 31/8/09, Dave McLaughlin wrote:
From: Dave McLaughlin
Subject: [rabbit-semi] PPP fails to connect second time around
To: r...@yahoogroups.com
Date: Monday, 31 August, 2009, 3:48 PM

I have got my PPP problem resolved with regards to connecting but now I can’t get it to do it more than once.

Running under DynC 10.56 and using an RCM5450W I get connected and can send data etc. If I disconnect and then try to connect again, the library gives a no buffer space available error. Here is the debug output and you can see the disconnect from the first connection, then it tries again and fails.

SERLINK: sendpacket using 000090B0
--- pkt flags=x40 i/f=0 tstamp=55555 len=5 ---
sect 1, len=5 addr=x001090D7 rlen=1568
41 54 48 0D 0A                                    ATH
SERLINK: transmitter was idle
SERLINK: receive processed 1 chars
SERLINK: got raw packet len=1, chatting=hangup
SERLINK: receive processed 9 chars
SERLINK: got raw packet len=3, chatting=hangup
SERLINK: got raw packet len=2, chatting=hangup
SERLINK: got raw packet len=4, chatting=hangup
CHAT: found it!
CHAT: end of script
SERLINK: Closed PPP serial on iface 0
SERLINK: baud rate 57600: setting divisor to 39
SERLINK: bringing up serial PPP interface 0
SERLINK: baud rate 57600: setting divisor to 39
SERLINK: Opened PPP serial on iface 0 at 57600 baud
CHAT: sending 'ATZ'
SERLINK: starting modem escape sequence
SERLINK: sendpacket totlen=1 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=000000 rxxpkt=000000
SERLINK: sendpacket totlen=1 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=000000 rxxpkt=000000
SERLINK: sendpacket totlen=1 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=000000 rxxpkt=000000

If you don’t enable debug the programme just appears to hang inside this looping around.

I also noticed today that during the first connect that it attempts to connect to the server to send data, it also gives this error after sending a few packets.

Opening socket
TCP/IP Failed Open
SERLINK: sendpacket totlen=44 i/f 0
SERLINK: sendpacket using 0000B054
--- pkt flags=x40 i/f=0 tstamp=56414 len=44 ---
sect 1, len=44 addr=x0010B07B rlen=1529
FF 03 00 21 45 00 00 28 00 09 00 00 40 06 C1 10      !E (    @
72 7B D1 AB 76 89 FF 06 20 E7 13 8A 00 00 00 00   r{ v
00 00 00 00 50 04 04 00 BD B8 00 00                   P
SERLINK: transmitter was idle
SERLINK: sendpacket totlen=48 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=100000 rxxpkt=10B6A8
p=108408 p->ll_flags=80 p->len=48
p=107DB4 p->ll_flags=80 p->len=48
p=108A5C p->ll_flags=80 p->len=48
p=1090B0 p->ll_flags=80 p->len=48
p=109704 p->ll_flags=80 p->len=48
p=109D58 p->ll_flags=80 p->len=48
p=10A3AC p->ll_flags=80 p->len=48
p=10AA00 p->ll_flags=80 p->len=56
p=10B054 p->ll_flags=80 p->len=48
p=10B6A8 p->ll_flags=00 p->len=10092
Opening socket
TCP/IP Failed Open
SERLINK: sendpacket totlen=44 i/f 0
SERLINK: sendpacket no buffer avail
txpkt=000000 txxpkt=100000 rxxpkt=10B6A8
p=108408 p->ll_flags=80 p->len=48
p=107DB4 p->ll_flags=80 p->len=48
p=108A5C p->ll_flags=80 p->len=48
p=1090B0 p->ll_flags=80 p->len=48
p=109704 p->ll_flags=80 p->len=48
p=109D58 p->ll_flags=80 p->len=48
p=10A3AC p->ll_flags=80 p->len=48
p=10AA00 p->ll_flags=80 p->len=56
p=10B054 p->ll_flags=80 p->len=48

Ignore the fact that it failed to connect, this is because my server was down during the test. You can see the first part is OK, then it fails similar to the redial. This indicates the fault lies in the PPP or SERLINK driver.

Running under DynC 9.62 with an RCM3000 the same dialing and connecting code works fine. Subsequent redials are also ok. This is using a different library so I suspect the issue is with the new 4000/5000 series libraries and the changes for PPP.

Regards
Dave….
Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!

(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )

Re: PPP fails to connect second time around - Dave McLaughlin - Sep 1 3:44:29 2009

Tried that and still get the buffer failure.

Is so darn frustrating as it is holding up my design now. Is all in the hands for Rabbit now to find the fault in their code.

Does anyone else here have a Rabbit 5000 based design and a modem they could run the MODEM_TEST.C programme in the PPP samples directory and see if it works for you?

Dave...

---
Very funny Scotty, now beam down my clothes!!!
---
http://www.embeddedcomputer.co.uk
---

From: r...@yahoogroups.com [mailto:r...@yahoogroups.com] On Behalf Of vivek gangwar
Sent: 31 August 2009 20:16
To: r...@yahoogroups.com
Subject: {Disarmed} Re: [rabbit-semi] PPP fails to connect second time around

Just Reinitialize to the socket driver then try to connect

////////////////////////////////////////////////////

try

sock_init_or_exit()

for Initialize the socket

then TCP_OPEN()

////////////////////////////////////////////

(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )