public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] CSR firmware
Date: Sat, 29 May 2004 11:08:05 +0200	[thread overview]
Message-ID: <200405291108.06457.cijoml@volny.cz> (raw)
In-Reply-To: <1085820898.3932.6.camel@pegasus>

On Saturday 29 of May 2004 10:54, Marcel Holtmann wrote:
> Hi Michal,
>
> > have anybody downloaded firmware from csr dongle? I would like to make
> > research if is possible to change vendor ID in it and then flash it back.
> > I think it is possibly way to upgrade firmware in old dongles.
> >
> > Can somebody give me help how download it? I have now access to 14
> > different csr based dongles from different wendors, which have same
> > firmware version. So I'll try find differences in firmware.
>
> the software you search for is my btdfu tool.
>
> 	http://www.holtmann.org/linux/bluetooth/btdfu-0.2.tar.gz
>
> And you upload a firmware from the dongle (archive mode) and you
> download a new one to a dongle (upgrade mode).
>
> The problem is not the vendor ID. It is the digital signature of the
> firmware file. You can download everything you want onto your dongle,
> but it can happen that the boot loader don't boot the other firmware. In
> that case it will stay in DFU mode. The boot loader can only be changed
> over a SPI connection.

That means, that if I download from dongle original firmware and then flash 
other one into dongle and it will not work I can't flash original fw back?

What is SPI connection?

Any related docs?

Michal


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-05-29  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29  0:56 [Bluez-users] CSR firmware Michal Semler
2004-05-29  8:54 ` Marcel Holtmann
2004-05-29  9:08   ` Michal Semler [this message]
2004-05-30  7:14     ` Marcel Holtmann
2004-05-30 10:29       ` Michal Semler
2004-05-30 11:03         ` Marcel Holtmann
2004-05-30 11:17           ` Michal Semler
2004-05-30 12:07             ` Marcel Holtmann
2004-06-01 11:26       ` Steven Singer
2004-06-01 11:55         ` Marcel Holtmann
2004-06-01 14:08           ` Steven Singer
2004-06-01 14:51             ` 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=200405291108.06457.cijoml@volny.cz \
    --to=cijoml@volny.cz \
    --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