Opened 10 years ago
Closed 9 years ago
#47816 closed defect (invalid)
avrdude: fix ftdi_syncbb to bring Programming Enable time delay into spec
| Reported by: | beck.dac@… | Owned by: | g5pw (Aljaž Srebrnič) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | haspatch | Cc: | beck.dac@… |
| Port: | avrdude |
Description
When using the FTDI bit banging programmer, chips will reply to signature requests and even program with -D (disable chip erase). However, when -D is left out and the default action -e (chip erase) occurs, the chip will not reply to a subsequent program enable in time.
This happens because the datasheet specified delay (20ms) has not been observed. The current version of avrdude 6.1 only waits for 5 ms. For chips with slow oscillators this is a problem.
The attached patch (patch-245r.diff) to be applied to the source corrects this problem as described in this post from avrdude-dev: https://lists.nongnu.org/archive/html/avrdude-dev/2013-09/msg00160.html
I have also included a Portfile patch (Portfile-avrdude.diff) that applies the attached patch.
Attachments (2)
Change History (7)
Changed 10 years ago by beck.dac@…
| Attachment: | Portfile-avrdude.diff added |
|---|
Changed 10 years ago by beck.dac@…
| Attachment: | patch-ft245r.diff added |
|---|
Source code patch that corrects the out of spec delay
comment:2 follow-up: 3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | beck.dac@… removed |
|---|---|
| Keywords: | haspatch added; avrdude ftdi removed |
| Owner: | changed from macports-tickets@… to g5pw@… |
| Summary: | patch avrdude for ftdi_syncbb fix to bring Programming Enable time delay into spec → avrdude: fix ftdi_syncbb to bring Programming Enable time delay into spec |
If this changes runtime behavior, the revision must be increased.
The mailing list post you reference is from 2013. Why haven't the developers released a new version fixing this problem?
comment:3 Changed 10 years ago by beck.dac@…
Thanks for looking at this...
Replying to ryandesign@…:
If this changes runtime behavior, the revision must be increased.
I've not submitted to macports before so I'm not sure I know what you mean. I understand the words, but I don't know if you mean the macports revision or avrdude...
The mailing list post you reference is from 2013. Why haven't the developers released a new version fixing this problem?
It was briefly fixed in an earlier version but it appears there was a reversion at 6.1. My guess is that since there have been no new releases since 6.1 this patch has not been applied.
comment:4 Changed 10 years ago by beck.dac@…
| Cc: | beck.dac@… added |
|---|
comment:5 Changed 9 years ago by g5pw (Aljaž Srebrnič)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I'm sorry, I'm not very familiar with that programmer, so I wouldn't know if the code fixes and does not have side effects on other hardware (as per this response). You should submit this patch upstream.
Portfile patch that applies the source code patch