Return-Path: Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm From: Marcel Holtmann To: Robert Wlaschin Cc: "'bluez-devel@lists.sourceforge.net'" In-Reply-To: References: Content-Type: text/plain Message-Id: <1128485442.26362.29.camel@blade> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 05 Oct 2005 06:10:42 +0200 Hi Robert, > That was a good suggestion. I've seen usage of those programs on > various help/websites. > > Due to a hardware limitations, I only have microcom available which > seems flaky at best. I seem to be getting the 'Exitcode 2 - cannot > open device /dev/rfcomm0' error message. But I have tried opening a > standard serial connection with microcom and it does function. > > The code in attest should work given the method I am using, is this > correct? If so I can just rewrite it to something ... a little more > towards my purpose. check if the /dev/rfcomm0 device node has been created and if yes, then run "hcidump -X -V" to see why the RFCOMM channel can't be opened. Regards Marcel ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel