Something strange with minicom

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

01 29 00 01 00

    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

01 29 00 01 00

    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

01 29 00 01 00

    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

01 29 00 01 00

    L2CAP(d): cid 0x0040 len 5 [psm 0]
      09 FF 01 01 5C

    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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Attila,

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

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users