From: Tomas Vanek <Tomas.Vanek@fbl.cz>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] dfutool block size
Date: Wed, 27 Jul 2005 16:27:38 +0200 [thread overview]
Message-ID: <42E799DA.70207@fbl.cz> (raw)
I tryied upgrade an old i-Tec BT dongle (CSR BlueCore2 ext + 4M flash,
ID=0a12:0001, original version 272 - BT 1.1 HCI 14.3) by dfutool.
Archiving old firmware was OK.
dfutool upgrade GenericCSR829.dfu
failed after time-out with message:
Can't upload next block: Broken pipe (32)
No change after upgrading to today's bluez cvs head.
I reduced written block size to 512 (why original length was 1023 and
not 1024??)
and dongle got upgraded OK (tested with archived fw version 272). Then I
tested sizes
in between:
1008 and 992: broken pipe
960: Can't get status: No such device after 9600 bytes
896: dfutool finished upgrade OK but dongle stays in DFU mode
768: upgrade worked
It's clear this is a problem in dfu loader in the dongle. I tested it again
with upgraded firmware and problem persists.
If there is more such dongles, it might be worth to add a block size
parameter to dfutool.
Tom
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-07-27 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 14:27 Tomas Vanek [this message]
2005-07-28 0:38 ` [Bluez-devel] dfutool block size 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=42E799DA.70207@fbl.cz \
--to=tomas.vanek@fbl.cz \
--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.