Hi, has anyone else seen uploads from Linux being extremely slow compared to other platforms? I've been working on Mac so far, and uploads happen super fast. Just brought up an environment on Linux, and it takes 1:15 to upload 180k. Using dfu-util 0.3 on Ubuntu 11.10 x64.
Wonder if it has anything to do with this line, "You appear to be using 64-bit Linux. Let us know if this works."
rosendo
Member
I don't know if it is of any help, but I am using windows 7 64 bit and the upload is also very slow! I also noticed that the more I upload the longer it gets! However, if I restart the computer it goes back to the original slowness, which would be around 10 seconds to flash "Blink", and I get the same on both Maple Native or Maple Mini.
After a day flashing many different stuff, flashing to Native was so slow that I decided to flash "Blink" for a test, and took more than 30 seconds!
I would like to add that the slowest part (the one in which the screen spends 95% of the time) is at:
Going to build using 'armcompiler' (ARM)
Compiling core.....
When this one is finished, the verbose goes really fast. I kind of feel like the system is waiting for something, and then looks like it reaches a timeout, where he just proceeds.
I also have a slow upload rate (~10 seconds) on a 64-bit Archlinux for a maple mini. But I thought this is normal as I had no reference until today when I've uploaded some code from my notebook (32-bit, running Archlinux, too, same dfu-util 0.6) and it was 10x faster.
tormod
Member
Since I don't have a maple, I ported(*) and installed the maple bootloader to a development board to verify this issue. Both on 32-bit and 64-bit it takes a little more than 8 seconds to flash 16384 bytes on a medium-density STM32 (128KB of flash). This can be expected since the maple bootloader tells dfu-util to wait 511 ms after each page has been flashed. So if you get something faster it must be because you use an old dfu-util version which does not honour the time given by the bootloader.
This is the "offending" code in the bootloader:
dfuAppStatus.bwPollTimeout0 = 0xFF; /* is this enough? */
dfuAppStatus.bwPollTimeout1 = 0x01; /* is this enough? */
I would answer the question in the code comment with: Yes, more than enough :) For comparison, the example boot loader from ST uses 32 ms. The ST document AN2594 hints to 20 ms for a page erase and 20 us per word write which should add up to 25 ms, so 32 ms sounds reasonable. Note that for larger flash size with larger page sizes there is not necessarily one page write per DFU transfer block.
This ought to be corrected in the maple bootloader, but meanwhile we can consider adding a quirk in dfu-util to overrule the bwPollTimeout returned from the maple.
Tormod
*) It was painful to hunt down the hardcoded port numbers in the bootloader code, and I forgot to remap the disconnect pin for a while. I believe this is improved in Necromant's patches.
You must log in to post.
