From: "Raul Siles" <raul.siles@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] How to confirm if a device has DFU support (dfutool)?
Date: Thu, 1 Nov 2007 02:12:44 +0100 [thread overview]
Message-ID: <c004c40d0710311812u50795ca4wa3a8f3a6b2848ec0@mail.gmail.com> (raw)
Hi everyone,
I'm trying to backup the firmware from a Conceptronic CBT100U USB
Bluetooth dongle using dfutool, and the message I get after selecting
the device is:
# dfutool -dhci0 archive file.dfu
...
"Can't identify device with DFU mode"
#
I understand this could mean this chip manufacturer does NOT support DFU,
although it is a CSR-based device, and mostly all CSR based modules and dongles
support DFU. How can I confirm if DFU is supported?
Sorry but I couldn't find any info on the net (apart from the dfutool
source code). From a quick code overview, it seems usb_find_devices()
fails to find the device.
The device revision details do not confirm it is a ROM-only device
(Thanks Marcel for the suggestion):
# hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:10:60:A6:0C:BC ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
Thanks!
--
RS
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-11-01 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 1:12 Raul Siles [this message]
2007-11-01 5:04 ` [Bluez-devel] How to confirm if a device has DFU support (dfutool)? Marcel Holtmann
2007-11-02 16:18 ` Raul Siles
2007-12-05 9:46 ` Raul Siles
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=c004c40d0710311812u50795ca4wa3a8f3a6b2848ec0@mail.gmail.com \
--to=raul.siles@gmail.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