Linux bluetooth development
 help / color / mirror / Atom feed
From: mike <mikelee@avantwave.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Hardware error
Date: Tue, 01 Feb 2005 19:55:24 +0800	[thread overview]
Message-ID: <41FF6E2C.7040908@avantwave.com> (raw)

Dear All
    When i try to send file though bluetooth, there is a hardware error 
in hcidump. I am using serial dongle with CSR BC02 external chip set, 
hci firmware ver 18.1.  And then both side will halt at the bluetooth 
read/write system call. I want to find out is it the problem from my 
hardware or anything else. Do anyone have ideas?

 > HCI Event: Number of Completed Packets(0x13) plen 5
 > HCI Event: Number of Completed Packets(0x13) plen 5
< ACL data: handle 0x002a flags 0x02 dlen 20
    L2CAP(d): cid 0x62 len 16 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 12 fcs 0x40
< ACL data: handle 0x002a flags 0x02 dlen 192
 > HCI Event: Number of Completed Packets(0x13) plen 5
 > HCI Event: Number of Completed Packets(0x13) plen 5
< ACL data: handle 0x002a flags 0x01 dlen 139
    L2CAP(d): cid 0x62 len 327 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 322 fcs 0x40
 > HCI Event: Hardware Error(0x10) plen 1
 > ACL data: handle 0x002a flags 0x02 dlen 9
    L2CAP(d): cid 0x40 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 3
< ACL data: handle 0x002a flags 0x02 dlen 20
    L2CAP(d): cid 0x62 len 16 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 12 fcs 0x40
< ACL data: handle 0x002a flags 0x02 dlen 192


hci0:   Type: UART
        BD Address: 00:08:E0:01:49:6A ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:149871 acl:2811 sco:0 events:12828 errors:0
        TX bytes:1847648 acl:15873 sco:0 commands:307 errors:0
        Features: 0xff 0xff 0x8b 0x78 0x18 0x18 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'mike (0)'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.2 (0x2) HCI Rev: 0x490 LMP Ver: 1.2 (0x2) LMP Subver: 
0x490
        Manufacturer: Cambridge Silicon Radio (10)

best regard
Mike,Lee




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-02-01 11:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01 11:55 mike [this message]
2005-02-01 11:46 ` [Bluez-devel] Hardware error Marcel Holtmann
2005-02-01 12:31 ` Peter Wippich
2005-02-01 14:52 ` Steven Singer
2005-02-03 13:43   ` mike

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=41FF6E2C.7040908@avantwave.com \
    --to=mikelee@avantwave.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox