public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daryl Van Vorst" <daryl@wideray.com>
To: "'Marcel Holtmann'" <marcel@holtmann.org>
Cc: "'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Missing data in ACL packets from CSR chip
Date: Fri, 13 Feb 2004 09:35:25 -0800	[thread overview]
Message-ID: <000501c3f257$c4649af0$1a01010a@baked> (raw)
In-Reply-To: <1076688033.2671.113.camel@pegasus>

Marcel,

It looks like a UART problem to me too, but it's probably not on my side
because both the sniffer and the host saw the same error.

I would like to try BCSP. Are there tools available to put the module in
BCSP mode?

I'm trying to get a firmware upgrade... But no luck yet.

-Daryl.

> -----Original Message-----
> From: Marcel Holtmann [mailto:marcel@holtmann.org] 
> Sent: February 13, 2004 8:01 AM
> To: Daryl Van Vorst
> Cc: BlueZ Mailing List
> Subject: Re: [Bluez-devel] Missing data in ACL packets from CSR chip
> 
> 
> Hi Daryl,
> 
> > Here's my decode:
> > 
> > Starting at index 536645:
> > 
> > 0536645: 04 13 05 01 2d 00 03 00
> > HCI event: Number of completed packets
> > 
> > 0536655: 02 2d 20 09 00 05 00 40 00 21 ff 01 03 9c
> > Valid ACL data packet.
> > 
> > 0536673 - 0537012
> > More Number of completed packets events
> > 
> > 0537013: 02 2d 20 09 00 05 00 40 00 21 ff 01 01 9c
> > Valid ACL data packet
> > 
> > 0537031: 02 2d 20 09 00 05 00 40 00 21 ff 01 9c 02
> > Corrupt packet.
> 
> this looks like an UART problem to me, but I don't know if it 
> is on the chip, on the module or one your side.
> 
> Is it possible for you to use BCSP? Do you have a firmware 
> update to the latest HCI 16.x or HCI 17.x?
> 
> Regards
> 
> Marcel
> 
> 
> 

  reply	other threads:[~2004-02-13 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 17:53 [Bluez-devel] Missing data in ACL packets from CSR chip Daryl Van Vorst
2004-02-13 16:00 ` Marcel Holtmann
2004-02-13 17:35   ` Daryl Van Vorst [this message]
2004-02-13 17:44     ` Marcel Holtmann
2004-02-13 18:53       ` Daryl Van Vorst
2004-02-13 19:22         ` Marcel Holtmann
2004-02-13 19:42           ` Daryl Van Vorst
2004-02-13 20:04             ` Marcel Holtmann
2004-02-13 19:11   ` Daryl Van Vorst
2004-02-13 19:40     ` Marcel Holtmann

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='000501c3f257$c4649af0$1a01010a@baked' \
    --to=daryl@wideray.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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