From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] dfutool - IBM X23 refuses to update ;)
Date: Fri, 21 Oct 2005 18:43:13 +0200 [thread overview]
Message-ID: <1129912993.11428.20.camel@blade> (raw)
In-Reply-To: <4359178E.3080408@kernelconcepts.de>
Hi Nils,
> Hmm... I just compared the original DFU and the upgrade DFU using the
> verify option:
>
> ./dfutool verify ITSE_00003_07_IBM_BDC_Firmware128_Rev310.dfu
> Filename ITSE_00003_07_IBM_BDC_Firmware128_Rev310.dfu
> Filesize 338168
> Checksum b589a143
> DFU suffix 10 03 ff ff ff ff 00 01 55 46 44 10 43 a1 89 b5
> idVendor ffff
> idProduct ffff
> bcdDevice 310
> bcdDFU 1.0
> ucDfuSignature DFU
> bLength 16
> dwCRC b589a143
> Firmware type CSR-dfu1
> Firmware check valid checksum
>
> ./dfutool verify org.dfu
> Filename org.dfu
> Filesize 320480
> Checksum 8c89a52e
> DFU suffix 15 01 10 03 bf 04 00 01 55 46 44 10 2e a5 89 8c
> idVendor 04bf
> idProduct 0310
> bcdDevice 115
> bcdDFU 1.0
> ucDfuSignature DFU
> bLength 16
> dwCRC 8c89a52e
> Firmware type CSR-dfu1
> Firmware check valid checksum
>
>
> Might the missing product and vendor ID be the problem with upgrade
> file? Can/should I try to change those?
no, because dfutool simply ignores them.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-21 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 16:16 [Bluez-devel] dfutool - IBM X23 refuses to update ;) Nils Faerber
2005-10-21 16:30 ` Nils Faerber
2005-10-21 16:43 ` Marcel Holtmann [this message]
2005-10-21 16:56 ` Nils Faerber
2005-10-21 16:30 ` 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=1129912993.11428.20.camel@blade \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.