Re: [Bluez-users] Something strange with minicom

Re: [Bluez-users] Something strange with minicom

[Attila Zsigmond]

> are you sure that you wanna be in security mode 3. Using auth and
>  encrypt is not advisable.

I turned off but it makes no difference...

> Make sure that you grep the initial HCI and L2CAP connection setup,
>  because otherwise hcidump is not able to decode RFCOMM. Or specific
> the --psm=3 option on the command line.

Here is a new dump with --psm=3:

HCI sniffer - Bluetooth packet analyzer ver 1.20
device: hci0 snap_len: 1028 filter: 0xffffffff
< ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      61
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 2A 00 01 00
> ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      74
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 2A 00 01 00
> ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      7A
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 2A 00 01 00
> ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0D
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 2A 00 01 00
> ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 42 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 9 fcs 0x40
      0D 0A 45 52 52 4F 52 0D 0A

I don't see any echoed characters at the end, only the "ERROR" message. 
But ATZ is a very common modem command and as I wrote earlier, it works 
with windows hyperterminal. I noticed that I enter only "AT", I got an 
OK. But any other AT commands don't work.

I'm sorry but I'm a newbe and don't know how to "grep the initial HCI 
and L2CAP connection setup". Here is my hcid.conf file:

options {
        autoinit yes;
        security auto;
        pairing multi;
        pin_helper /bin/bluepin;
}
device {
        name "Cornflower";
        class 0x3e0100;
        iscan enable; pscan enable;
        lm master;
        lp rswitch,hold,sniff,park;
}

My mobile is a sharp gx15. Here is its "hcitool info" output, maybe it 
can help:

Requesting information ...
        BD Address:  08:00:1F:51:D1:E9
        Device Name: Wildrose
        LMP Version: 1.1 (0x1) LMP Subversion: 0x460
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xef 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
        <3-slot packets> <5-slot packets> <encryption> <slot offset>
        <role switch> <hold mode> <sniff mode> <park state> <RSSI>
        <channel quality> <SCO link> <HV2 packets> <HV3 packets>
        <u-law log> <A-law log> <CVSD> <paging scheme>
        <transparent SCO>

Please tell me if you need any other info...

Attila


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Marcel Holtmann]

Hi Attila,

> > Make sure that you grep the initial HCI and L2CAP connection setup,
> >  because otherwise hcidump is not able to decode RFCOMM. Or specific
> > the --psm=3 option on the command line.
> 
> Here is a new dump with --psm=3:

use "hcidump -X -V --psm=3" so I don't have to decode everything by
myself.

> I don't see any echoed characters at the end, only the "ERROR" message. 
> But ATZ is a very common modem command and as I wrote earlier, it works 
> with windows hyperterminal. I noticed that I enter only "AT", I got an 
> OK. But any other AT commands don't work.

The echoing must not be on by default. Enter "ATE1" and see happens.

> I'm sorry but I'm a newbe and don't know how to "grep the initial HCI 
> and L2CAP connection setup".

Start hcidump earlier so it can decode the whole connection setup.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Attila Zsigmond]

On Saturday 30 April 2005 01:56, Marcel Holtmann wrote:
> Hi Attila,
> use "hcidump -X -V --psm=3" so I don't have to decode everything by
> myself.
>
> Start hcidump earlier so it can decode the whole connection setup.
>
> Regards
>
> Marcel

Here is a dump with the parameters suggested. It seems normal for me. I 
begin to think that this problem is in relation to my sharp gx15 phone 
configuration and not to bluez. But I'm not sure. What do you think?

HCI sniffer - Bluetooth packet analyzer ver 1.20
device: hci0 snap_len: 1028 filter: 0xffffffff
< ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0041 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 12
    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 0d                                                .
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 41                                                A
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 54                                                T
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 5a                                                Z
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 0d                                                .
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 41 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 9 fcs 0x40
      0000: 0d 0a 45 52 52 4f 52 0d  0a                       ..ERROR..
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 61                                                a
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 74                                                t
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 0d                                                .
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 41 flags 0x02 dlen 14
    L2CAP(d): cid 0x0040 len 10 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 6 fcs 0x40
      0000: 0d 0a 4f 4b 0d 0a                                 ..OK..
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 61                                                a
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 74                                                t
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 1 fcs 0x9a
      0000: 0d                                                .
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 41
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 1
> ACL data: handle 41 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 9 fcs 0x40
      0000: 0d 0a 45 52 52 4f 52 0d  0a                       ..ERROR..

Attila 



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Marcel Holtmann]

Hi Attila,

> Here is a dump with the parameters suggested. It seems normal for me. I 
> begin to think that this problem is in relation to my sharp gx15 phone 
> configuration and not to bluez. But I'm not sure. What do you think?

it looks fine to me, too. Maybe you should try the attest program from
the bluez-utils source package.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Attila Zsigmond]

On Saturday 30 April 2005 21:38, Marcel Holtmann wrote:
> Hi Attila,
>
> > Here is a dump with the parameters suggested. It seems normal for
> > me. I begin to think that this problem is in relation to my sharp
> > gx15 phone configuration and not to bluez. But I'm not sure. What
> > do you think?
>
> it looks fine to me, too. Maybe you should try the attest program
> from the bluez-utils source package.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great
> events, 4 opportunities to win big! Highest score wins.NEC IT Guy
> Games. Play to win an NEC 61 plasma display. Visit
> http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


Marcel,

Is it possible that this error is caused by a kernel error? You knows it 
better... I have an old 2.4.24 kernel version. (Old kernel on an old 
PC: 700 MHz duron. :-( ) I know I should upgrade both.

Attila


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Marcel Holtmann]

Hi Attila,

> Is it possible that this error is caused by a kernel error? You knows it 
> better... I have an old 2.4.24 kernel version. (Old kernel on an old 
> PC: 700 MHz duron. :-( ) I know I should upgrade both.

I never tried a Samsung phone and maybe they are a little bit buggy, but
it can also be a problem of the kernel. The 2.4 series is no longer
actively maintained and you should really update to a 2.6 kernel.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Attila Zsigmond]

On Monday 02 May 2005 12:37, Marcel Holtmann wrote:
> Hi Attila,
>
> > Is it possible that this error is caused by a kernel error? You
> > knows it better... I have an old 2.4.24 kernel version. (Old kernel
> > on an old PC: 700 MHz duron. :-( ) I know I should upgrade both.
>
> I never tried a Samsung phone and maybe they are a little bit buggy,
> but it can also be a problem of the kernel. The 2.4 series is no
> longer actively maintained and you should really update to a 2.6
> kernel.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great
> events, 4 opportunities to win big! Highest score wins.NEC IT Guy
> Games. Play to win an NEC 61 plasma display. Visit
> http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users

It isn't a Samsung, it's a Sharp. But that makes no diference, I think. 
I will get and try a new kernel.

Attila


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Attila Zsigmond]

It cleared finally. I write this only to help to others. There was no 
hardware error, no kernel error, no bluez error, no error in the phone. 
I didn't know about rfcomm channels and I used the default 1 instead of 
5, which is for serial port service on sharp GX15 phone.

Attila

Marcel Holtmann wrote:
> Hi Attila,
> 
> 
>>Is it possible that this error is caused by a kernel error? You knows it 
>>better... I have an old 2.4.24 kernel version. (Old kernel on an old 
>>PC: 700 MHz duron. :-( ) I know I should upgrade both.
> 
> 
> I never tried a Samsung phone and maybe they are a little bit buggy, but
> it can also be a problem of the kernel. The 2.4 series is no longer
> actively maintained and you should really update to a 2.6 kernel.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] Something strange with minicom

[Attila Zsigmond]

Hello

I'm trying to connect to my new mobile phone via a usb bluetooth 
dongle. I solved many problems (and learned a lot) but I'm 
stuck. I downloaded and installed the latest bluez stuff. 
(Version 2.16 at this time) It seems to work but I still can not 
comminicate with my phone. I can start everything and could pair 
my phone with my PC. When I start minicom to test the 
connection, I can type anything but phone answers with "error". 
I tried it with hyperterminal under windows and it works. So we 
shouldn't talk about hardware problems.

Here is my hciconfig -a output:
hci0:   Type: USB
        BD Address: 00:09:DD:10:6D:32 ACL MTU: 192:8 SCO MTU: 
64:8
        UP RUNNING PSCAN ISCAN AUTH ENCRYPT
        RX bytes:1990 acl:51 sco:0 events:91 errors:0
        TX bytes:1174 acl:49 sco:0 commands:28 errors:0
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'Cornflower'
        Class: 0x3e0100
        Service Classes: Networking, Rendering, Capturing
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x460 LMP Ver: 1.1 (0x1) LMP 
Subver: 0x460
        Manufacturer: Cambridge Silicon Radio (10)

And here is the "hcidump -x" result when I enter an "atz" modem 
command in minicom:
HCI sniffer - Bluetooth packet analyzer ver 1.20
device: hci0 snap_len: 1028 filter: 0xffffffff
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 0]
      0B EF 03 61 9A
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 0]
      09 FF 01 01 5C
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 0]
      0B EF 03 74 9A
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 0]
      09 FF 01 01 5C
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 0]
      0B EF 03 7A 9A
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 0]
      09 FF 01 01 5C
< ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0041 len 5 [psm 0]
      0B EF 03 0D 9A
> HCI Event: Number of Completed Packets (0x13) plen 5
  01 29 00 01 00
> ACL data: handle 41 flags 0x02 dlen 9
    L2CAP(d): cid 0x0040 len 5 [psm 0]
      09 FF 01 01 5C
> ACL data: handle 41 flags 0x02 dlen 17
    L2CAP(d): cid 0x0040 len 13 [psm 0]
      09 EF 13 0D 0A 45 52 52 4F 52 0D 0A 40

I noticed in the last line that there was "09 ef 13" echoed back 
instead of "atz". So I can understand why the modem says error 
but I can't understand how can it receive these characters.

What I missed? Can anybody help?

Attila 



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Something strange with minicom

[Marcel Holtmann]

Hi Attila,

> I'm trying to connect to my new mobile phone via a usb bluetooth 
> dongle. I solved many problems (and learned a lot) but I'm 
> stuck. I downloaded and installed the latest bluez stuff. 
> (Version 2.16 at this time) It seems to work but I still can not 
> comminicate with my phone. I can start everything and could pair 
> my phone with my PC. When I start minicom to test the 
> connection, I can type anything but phone answers with "error". 
> I tried it with hyperterminal under windows and it works. So we 
> shouldn't talk about hardware problems.
> 
> Here is my hciconfig -a output:
> hci0:   Type: USB
>         BD Address: 00:09:DD:10:6D:32 ACL MTU: 192:8 SCO MTU: 
> 64:8
>         UP RUNNING PSCAN ISCAN AUTH ENCRYPT
>         RX bytes:1990 acl:51 sco:0 events:91 errors:0
>         TX bytes:1174 acl:49 sco:0 commands:28 errors:0
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'Cornflower'
>         Class: 0x3e0100
>         Service Classes: Networking, Rendering, Capturing
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x460 LMP Ver: 1.1 (0x1) LMP 
> Subver: 0x460
>         Manufacturer: Cambridge Silicon Radio (10)

are you sure that you wanna be in security mode 3. Using auth and
encrypt is not advisable.

> And here is the "hcidump -x" result when I enter an "atz" modem 
> command in minicom:
> HCI sniffer - Bluetooth packet analyzer ver 1.20
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < ACL data: handle 41 flags 0x02 dlen 9
>     L2CAP(d): cid 0x0041 len 5 [psm 0]
>       0B EF 03 61 9A

Make sure that you grep the initial HCI and L2CAP connection setup,
because otherwise hcidump is not able to decode RFCOMM. Or specific the
--psm=3 option on the command line.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users