From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] DBT-120 firmware upgrade
Date: Sat, 27 Nov 2004 19:22:11 +0100 [thread overview]
Message-ID: <1101579731.27074.8.camel@pegasus> (raw)
In-Reply-To: <200411271655.27322.pavouk@pavouk.org>
Hi Pavel,
> when I compare original backuped firmware with downloaded, that
> there are few differences:
> --------------
> Filename backup.dfu
> bcdDevice 443
> Firmware type CSR-dfu2
> --------------
> Filename GenericCSR.dfu
> bcdDevice ffff
> Firmware type CSR-dfu1
> --------------
>
> Can somebody explain me, what does it means and if it is not problem
> for flashing?
the filename difference should be clear, I think. The bcdDevice is the
build id. Uploaded files are filled with the current build id of the
running firmware. The generic firmware files don't contains a build id,
because they are not build to replace a specific one. CSR has two types
of firmware files and you can use type 1 and 2 to download a new one,
but if you upload a firmware you will get the latest type and this is 2.
> Downloaded firmware is much longer than backuped. Is it OK?
The GenericCSR.dfu contains two firmware files. One HCI 18.x for chips
with 8 Mbit flash and a HCI 16.x for chips with 4 Mbit flash.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-27 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 10:52 [Bluez-users] DBT-120 firmware upgrade Pavel Ruzicka
2004-11-26 17:25 ` Marcel Holtmann
2004-11-27 15:55 ` Pavel Ruzicka
2004-11-27 18:22 ` Marcel Holtmann [this message]
2004-11-27 20:30 ` Pavel Ruzicka
2004-11-27 20:50 ` Marcel Holtmann
2004-11-29 12:23 ` Steven Singer
2004-11-29 12:33 ` Marcel Holtmann
2004-11-29 12:49 ` Steven Singer
2004-11-29 17:30 ` Marcel Holtmann
2004-11-29 18:15 ` Peter Stephenson
2004-11-29 18:33 ` Marcel Holtmann
2004-11-29 18:44 ` Peter Stephenson
2004-11-29 18:46 ` Michal Semler
2004-11-27 0:58 ` Michal Semler
2004-11-27 3:03 ` Marcel Holtmann
2004-11-27 15:12 ` Pavel Ruzicka
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=1101579731.27074.8.camel@pegasus \
--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