From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] dfutool block size
Date: Thu, 28 Jul 2005 02:38:01 +0200 [thread overview]
Message-ID: <1122511081.916.4.camel@notepaq> (raw)
In-Reply-To: <42E799DA.70207@fbl.cz>
Hi Thomas,
> 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.
feel free to send in a patch that adds a parameter for a different block
size.
Regards
Marcel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-07-28 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 14:27 [Bluez-devel] dfutool block size Tomas Vanek
2005-07-28 0:38 ` Marcel Holtmann [this message]
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=1122511081.916.4.camel@notepaq \
--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.