From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dfutool problems
Date: Wed, 06 Jun 2007 00:30:43 +0200 [thread overview]
Message-ID: <1181082643.13429.143.camel@violet> (raw)
In-Reply-To: <4665E314.8050609@gmail.com>
Hi Jarom,
> I recently ran "dfutool archive foo" on my IBM bluetooth adapter
> (Broadcom) thinking it would save my firmware to the file "foo". It
> created a zero-length file, said that the operation timed out, and
> exited. Ever since, by bluetooth adapter has been stuck in DFU mode:
>
> # dfutool archive foo
> Available devices with DFU support:
>
> 1) Bus 003 Device 034: ID 0a5c:2000 Interface 0 (DFU mode)
>
> Select device (abort with 0): 1
>
> Firmware upload ...
> Can't upload next block: Connection timed out (110)
>
> from dmesg:
> usb 3-1: Product: Broadcom Bluetooth Download Device
>
> Does anyone know why it did that and how to get the adapter out of DFU
> mode? I don't want to have to buy a new adapter... :)
the Broadcom ones fail for no reason. Seems that their implementation of
DFU is buggy. I have seen that before.
However there is no tool to get it back into normal. It is not that
complicated, but you have to poke around the source code of dfutool for
that.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-06-05 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:26 [Bluez-devel] dfutool problems Jarom Hatch
2007-06-05 22:30 ` Marcel Holtmann [this message]
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=1181082643.13429.143.camel@violet \
--to=marcel@holtmann.org \
--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