On 4/10/07, Iain Hibbert <[EMAIL PROTECTED]> wrote:
On Tue, 10 Apr 2007, Eric Anderson wrote:> On 04/10/07 15:04, Vittorio De Martino wrote: > > How can I make it? > > I don't see RFCOMM in the list above. yeah, Vittorio should try sdpcontrol -a tomtom search sp to see if the 'Serial Port' service is available.. > Record Handle: 0x00090001 > Service Class ID List: > Serial Port (0x1101) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 1 in the above example, you can connect to channel 1 directly since you know that the Serial Port service is there.. rfcomm_sppd -a xxx -t /dev/ttyp6 -c 1 perhaps if Vittorio can't find any serial port, try connecting to all the channels between 1 and 30 to see if he can find the one that the tomtom is listening on.
well, it might or might not work. was tomtom gps previously paired with another bluetooth device? some devices are quite paranoid and will not accept any incoming connection unless it comes from "known/trusted" device. if fact, some devices wont even advertise service once they were paired. the assumption here is that "known/trusted" device saved all required information (such as rfcomm channel number, link key or pin code) locally and will use it next time to connect. so, if your tomtom gps supports "pairing" mode you need to put it into this mode first time you try to connect "new" device to tomtom gps. also, as others already pointed out, it is better to use % sdpcontrol -a xxxx search sp instead of 'browse'. many devices do not bother to put advertised services into public browse group, so 'browse' will not find them. thanks, max _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "[EMAIL PROTECTED]"
