dfutool block size

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Hi Thomas,

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel