From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dfutool problems
Date: Sat, 16 Jun 2007 09:52:06 +0200 [thread overview]
Message-ID: <1181980327.6846.80.camel@aeonflux.inter-touch.com> (raw)
In-Reply-To: <4665E3BA.1040309@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... :)
if it is Broadcom then it will fail. And it is possible to get this back
out of the mode, but no tool supports it. Or maybe the dfu-util from the
OpenMoko project.
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-06-16 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:29 [Bluez-users] dfutool problems Jarom Hatch
2007-06-16 7:52 ` 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=1181980327.6846.80.camel@aeonflux.inter-touch.com \
--to=marcel@holtmann.org \
--cc=bluez-users@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