From: Marcel Holtmann <marcel@holtmann.org>
To: Carlos AM <Carlos@naxus.biz>
Cc: lista bluez <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM communication gets stalled
Date: Thu, 15 Jul 2004 19:48:42 +0200 [thread overview]
Message-ID: <1089913722.4517.37.camel@pegasus> (raw)
In-Reply-To: <002c01c46a77$034a25e0$5000005a@naxus>
Hi Carlos,
> I'm using bluez-libs-2.7 and bluez-utils-2.7 to develop a GPS system
> that communicates via bluetooth. I use the RFCOMM and the connection
> and disconnection works fine but the transmission gets stalled in
> about ten minutes. Both sides indicate that they are still connected,
> but in the GPS side, the process that writes in the rfcomm device
> (/dev/bluetooth/rfcomm/0) stops on a blocking write call:
>
> write(fdbluetooth,s,strlen(s));
>
> I open the rfcomm device this way:
>
> fdbluetooth= open("/dev/bluetooth/rfcomm/0",O_RDWR | O_NOCTTY);
>
>
> That write call works fine for a while until the communication gets
> stalled.
don't use the RFCOMM TTY terminal emulation. Go directly throught the
RFCOMM socket interface. If you still got problems check with hcidump
what is going on.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-15 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 14:21 [Bluez-devel] RFCOMM communication gets stalled Carlos AM
2004-07-15 17:48 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-15 18:11 Williams, Richard
2004-07-15 18:23 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089913722.4517.37.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Carlos@naxus.biz \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.