AVR Downloader/UploaDEr - Bugs: bug #44848, OS X and avrmkII, again
You are not allowed to post comments on this tracker with your current authentication level.
bug #44848: OS X and avrmkII, again
Submitter: | Juergen Eckert <jesid> | ||
Submitted: | Wed 15 Apr 2015 03:18:01 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | jesid |
Open/Closed: | Open | Release: | None |
Programmer hardware: | Device type: |
Thu 15 Oct 2015 07:55:52 AM UTC, comment #4: |
Richard Falk <richfalk> |
Thu 15 Oct 2015 07:40:14 AM UTC, comment #3: I just tested the patch mentioned in comment #1 (from Hisashi ITO) and it works to fix the problem for me so that seems to be the source of the problem so ignore my comment #2 and instead apply the simple patch to the file stk500v2.c. |
Richard Falk <richfalk> |
Thu 15 Oct 2015 07:26:40 AM UTC, comment #2: I have found that the problem occurs due to some missing cleanup (closing?) at the end of execution because the first time avrdude 6.1 is run the problem does not occur, but then it occurs on every subsequent execution. If I then run avrdude 6.0.1 the problem still occurs only for that execution while every subsequent 6.0.1 execution is fine. If I then run 6.1 again it is OK the first time, but every subsequent 6.1 execution shows the problem.
|
Richard Falk <richfalk> |
Wed 05 Aug 2015 02:47:17 PM UTC, comment #1: Maybe this patch will work for your mac, too.
|
Hisashi ITO <orangkucing> |
Wed 15 Apr 2015 03:18:01 PM UTC, original submission:
Hi
|
Juergen Eckert <jesid> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-f8d8.
Corresponding source code
Sorry, ignore my comment #3. I got fooled by the ping-pong nature of this bug. The patch referred to in comment #1 did not fix the problem. My comment #2 is still relevant.