Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Great info, thank you. I looked into my output and found: "avrdude: Using SCK period of 10 usec" So it appears to be set to the default of 10uS. Commented Nov 26, 2020 at 5:23
  • I went into the avrdude.conf file and changed the "default_bitclock" value to 1. Code now uploads in 10 seconds and executes fine on the chip. This is a 66% improvement but still seems like it ought to upload faster based on the math. Commented Nov 26, 2020 at 5:32
  • Or.... maybe this is about right. If we're estimating about 3.5 seconds of spi data and the bitclock is set to pause for 2uS for each bit ... if each bit took about 1uS to write wouldn't that approximately triple the total time it takes? Although I have no idea how much time it actually is taking to write one bit... Commented Nov 26, 2020 at 5:52
  • @codyblanchard, see expanded findings. The "the plain clocking of the SPI data" probably should have been written to say "of the program data". What I was trying to do (and probably failing at) was being conservative in saying rough 3.7 seconds for the irreducible (barring compression) SPI timing associated with program data itself. Beyond what I've just mentioned in the update, I'm sure there are more delays. Though they'll probably be diminishing returns. Commented Nov 26, 2020 at 13:38