public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] How to confirm if a device has DFU support	(dfutool)?
Date: Thu, 01 Nov 2007 06:04:10 +0100	[thread overview]
Message-ID: <1193893450.32459.114.camel@violet> (raw)
In-Reply-To: <c004c40d0710311812u50795ca4wa3a8f3a6b2848ec0@mail.gmail.com>

Hi Raul,

> 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?

that is plain wrong. Most CSR based devices are nowadays ROM chips and
don't support DFU anymore. However check /proc/bus/usb/devices, it will
tell you exactly if it is supported or not.

Regards

Marcel



-------------------------------------------------------------------------
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

  reply	other threads:[~2007-11-01  5:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  1:12 [Bluez-devel] How to confirm if a device has DFU support (dfutool)? Raul Siles
2007-11-01  5:04 ` Marcel Holtmann [this message]
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=1193893450.32459.114.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