[avrdude-dev] [bug #52963] -U option with flash memory doesn't perform chip erase with arduino programmer

Update of bug #52963 (project avrdude): Status:None => Invalid Assigned to:None => joerg_wunsch ___ Follow-up Comment #1: IMHO this is entire

[avrdude-dev] [patch #8444] Proposal for modifications in -B and -U command options managment

Update of patch #8444 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #8954] Enable usage of libusb-1.0 for stk500v2 (aka avrispmkii)

Update of patch #8954 (project avrdude): Status:None => Need Info ___ Follow-up Comment #1: This does unfortunately not compile under FreeBSD where the OS offers a libusb-1.0 API compatib

[avrdude-dev] [patch #9254] Adds support for selecting USB devices to USBasp

Update of patch #9254 (project avrdude): Status:None => Need Info ___ Follow-up Comment #1: Somehow, it doesn't seem to work for me. The USBasp can be found (no target connected, thus fa

[avrdude-dev] [patch #9127] Support for CH341A programmer.

Follow-up Comment #5, patch #9127 (project avrdude): I can understand that you are mainly interested in fast programming - but if it fails to operate on AVRs the way they are shipped (i.e., clocked with 1 MHz), it doesn't make much sense to include it. You'd need something else then to reprogram t

[avrdude-dev] [patch #8436] Remove HAVE_STDINT_H guards in flip1.c and flip2.c

Update of patch #8436 (project avrdude): Status: Need Info => Wont Do Open/Closed:Open => Closed ___ Follow-up Comment #2: "Need info" timed

[avrdude-dev] [patch #8128] Added new option to configure.ac script

Update of patch #8128 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #8504] buspirate: Also support "cpufreq" extended parameter in binary mode

Update of patch #8504 (project avrdude): Open/Closed:Open => Closed ___ Reply to this item at: ___

[avrdude-dev] [patch #8529] 2 more ftdi_syncbb devices

Update of patch #8529 (project avrdude): Open/Closed:Open => Closed ___ Reply to this item at: ___

[avrdude-dev] [patch #8511] Fix reset on FT245R

Update of patch #8511 (project avrdude): Open/Closed:Open => Closed ___ Reply to this item at: ___

[avrdude-dev] [patch #9542] Correct "usersig" on avr8x devices

Update of patch #9542 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9185] Add extended_param to usbasp.c - erasing configuration section in ATtiny 4...40 (TPI)

Update of patch #9185 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed

[avrdude-dev] [patch #7543] config file template with xslt

Update of patch #7543 (project avrdude): Status:None => Wont Do Open/Closed:Open => Closed ___ Follow-up Comment #1: patch #9506 obsole

[avrdude-dev] [patch #7321] usbasp: filter usb serial number

Update of patch #7321 (project avrdude): Status:None => Need Info Assigned to: fischl => joerg_wunsch ___ Follow-up Comment #2: Unfortunately, Tho

[avrdude-dev] [patch #8311] Add IPv6 support to the -Pnet:host:port option

Update of patch #8311 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9185] Add extended_param to usbasp.c - erasing configuration section in ATtiny 4...40 (TPI)

Follow-up Comment #1, patch #9185 (project avrdude): Committed in r1419, thanks! I changed the variable names from capitals to lowercase, as capitals are conventionally used for macros. I slightly reworded the documentation, but formatting looked good. __

[avrdude-dev] [patch #8437] [PATCH] Serial-over-ethernet for Win32

Update of patch #8437 (project avrdude): Open/Closed:Open => Closed ___ Follow-up Comment #2: No feedback for almost four years. ___

[avrdude-dev] [patch #7774] ATxmega32A4: fixed page sizes and usersig settings

Update of patch #7774 (project avrdude): Status: Need Info => Wont Do Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #8717] pattch for mcprog and libhidapi support

Update of patch #8717 (project avrdude): Status:None => Need Info ___ Follow-up Comment #1: Well, libhidapi support meanwhile entered the tree already, as part of EDBG support. I'd ask f

[avrdude-dev] [patch #8922] Fix linuxgpio

Update of patch #8922 (project avrdude): Status:None => Duplicate Open/Closed:Open => Closed ___ Reply to this item at:

[avrdude-dev] [patch #8219] Fix boot_start for xmega devices on jtagmkII

Update of patch #8219 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9507] Fix UPDI chip erase

Follow-up Comment #10, patch #9507 (project avrdude): Applied in r1417 (with minor modifications). Flash byte read is used in terminal mode (avrdude -t), and I can confirm it appears to be broken now. Unlocking my unresponsive XplainedPro board worked without trouble. __

[avrdude-dev] [patch #8910] ATxmega32c4 and ATxmega16c4 have wrong signatures

Update of patch #8910 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [bug #41388] ATxmega32c4 and ATxmega16c4 have wrong signatures

Update of bug #41388 (project avrdude): Status:None => Fixed Assigned to:None => joerg_wunsch Open/Closed:Open => Closed Release:

[avrdude-dev] [patch #8580] FT245r support to select device by serial number

Update of patch #8580 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9033] avrdoper backend uses libhidapi instead of libusb

Update of patch #9033 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #8924] Enable TPI for usbtiny

Update of patch #8924 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9222] Enable silent build

Update of patch #9222 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9317] Support atmega64m1 as part

Update of patch #9317 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9530] Update URL to Ladyada's USBtinyISP page.

Update of patch #9530 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [bug #49455] support for tiny441

Update of bug #49455 (project avrdude): Status:None => Fixed Assigned to:None => joerg_wunsch Open/Closed:Open => Closed __

[avrdude-dev] [bug #47376] ATtiny841 description missing in configuration file

Update of bug #47376 (project avrdude): Status:None => Fixed Assigned to:None => joerg_wunsch Open/Closed:Open => Closed Release:

[avrdude-dev] [patch #9423] Support ATtiny841 and ATtiny441

Update of patch #9423 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [patch #9506] Script to create device configuration stub from Atmel ATDF files

Update of patch #9506 (project avrdude): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #6: Thanks for updatin

[avrdude-dev] [patch #9507] Fix UPDI chip erase

Follow-up Comment #7, patch #9507 (project avrdude): Thanks, looks good. Commited in r1405. Only thing: after chip erase, my XplainedPro doesn't want to update its flash anymore: avrdude: jtag3_paged_write(.., flash, 64, 64) avrdude: jtag3_paged_write(): block_size at addr 32768 is 64 avrdude:

[avrdude-dev] [patch #9506] Script to create device configuration stub from Atmel ATDF files

Update of patch #9506 (project avrdude): Status:None => In Progress Assigned to:None => joerg_wunsch ___ Follow-up Comment #4: New config file co

[avrdude-dev] [patch #9506] Script to create device configuration stub from Atmel ATDF files

Follow-up Comment #3, patch #9506 (project avrdude): Thanks for the script! I'd appreciate some kind of redistributions conditions for it. By default, no permission is granted, so I could thus not include it into the AVRDUDE source code (though I could, of course, keep it sitting here in the trac

[avrdude-dev] [bug #52826] help with ID

Update of bug #52826 (project avrdude): Status:None => Invalid Assigned to:None => joerg_wunsch Open/Closed:Open => Closed __

Re: [avrdude-dev] Bug in AVR8X XPlained Mini FW preventing Avrdude connection

As janegil.r...@microchip.com wrote: > Any views on this? If not I'll leave it at this. At least you are > aware of it now. I agree to leave it as it is. The number of Xplained Mini users with UPDI devices is by now probably neglicible, and once their firmware is upgraded, nobody would notice an

[avrdude-dev] [patch #9507] Fix UPDI chip erase

Follow-up Comment #5, patch #9507 (project avrdude): Thanks for the explanation. I suggest the following strategy then: The UPDI-capable devices get their Family_ID added to the config file ("tinyAVR"), so there is something to minimally compare against when the signature is unreadable. Then, i

[avrdude-dev] [bug #52687] avrdude eeprom uploader always uploads 0xff if line terminator is LF not CRLF

Follow-up Comment #3, bug #52687 (project avrdude): The question is not about removing whitespace but reimplementing fgets() rather than using the system/library version. ___ Reply to this item at:

[avrdude-dev] [patch #9507] Fix UPDI chip erase

Follow-up Comment #2, patch #9507 (project avrdude): Committed in r1403, except for the changes in main.c (by now, until discussed). ___ Reply to this item at: ___

[avrdude-dev] [patch #9507] Fix UPDI chip erase

Update of patch #9507 (project avrdude): Status:None => In Progress Assigned to:None => joerg_wunsch ___ Follow-up Comment #1: Why did you put th

[avrdude-dev] [patch #9508] Add PowerDebugger and XPlained Mini in UPDI mode

Update of patch #9508 (project avrdude): Status:None => Done Assigned to:None => joerg_wunsch Open/Closed:Open => Closed _

[avrdude-dev] [bug #52687] avrdude eeprom uploader always uploads 0xff if line terminator is LF not CRLF

Follow-up Comment #1, bug #52687 (project avrdude): I'd have replied that Intel Hex files are by definition to be terminated with CR-LF, but it seems Intel indeed never specified this. The behaviour you are mentioning does by no means to be intended by the way the code is written. Curious, are y

[avrdude-dev] [bug #52645] (0xc000007b) with last windows update

Follow-up Comment #1, bug #52645 (project avrdude): Here's the reply Bob Paddock sent to the mailinglist: This can happen if a 32-bit DLL is still lingering in the PATH for some reason. Open a DOS box, create an empty directory. Copy avrdude.exe and config file to the empty directory. Set PATH

Re: [avrdude-dev] [patch #9482] Add support for UPDI and AVR8X

As Joerg Wunsch wrote: > Follow-up Comment #5: > > Thanks a lot, good work! > > Just committed to SVN, with only few changes (white space only). Let me introduce Jan Egil Ruud to the rest of the audience. Jan Egil works for Microchip (former Atmel) in Trondheim, Norway. He sub

[avrdude-dev] [patch #9482] Add support for UPDI and AVR8X

Update of patch #9482 (project avrdude): Status: In Progress => Done Open/Closed:Open => Closed ___ Follow-up Comment #5: Thanks a lot, good

[avrdude-dev] [patch #9482] Add support for UPDI and AVR8X

Update of patch #9482 (project avrdude): Status:None => In Progress Assigned to:None => joerg_wunsch ___ Follow-up Comment #3: After digging a bi

[avrdude-dev] [patch #9482] Add support for UPDI and AVR8X

Follow-up Comment #2, patch #9482 (project avrdude): I had to dig around for all this, too. The offsets used in the linker scripts are based on historical decisions, to merge all the distinct AVR Harvard address spaces into a single, flat 32-bit address space which used to be the default for GNU

[avrdude-dev] [bug #48084] Avoid compiled-in timestamp for reproducible release builds

Update of bug #48084 (project avrdude): Status:None => Fixed Assigned to:None => joerg_wunsch Open/Closed:Open => Closed Release:

Re: [avrdude-dev] Signed dummy kext for AtmelICE for MacOS X High Sierra

As Nick Sayer wrote: > So I ponied up for a year of the Apple dev program and asked Apple > for the ability to sign kexts, which they graciously have > allowed. And thus, voila, I’ve made a signed dummy kext for the > AtmelICE. Do you want me to put it into the AVRDUDE download area, too? If so,

[avrdude-dev] [bug #51497] avrdude not writing high byte using linuxgpio when data byte count is less than 0x10

Follow-up Comment #2, bug #51497 (project avrdude): Quite possible this might be valid. My guess is that linuxgpio simply isn't used very widely by many people. ___ Reply to this item at: __

[avrdude-dev] [bug #52318] Fuse progamming error

Follow-up Comment #4, bug #52318 (project avrdude): Thanks for the response. I'll see to try it myself, too. I do have some ad-hoc USBasp somewhere, but I'm afraid I have to find a recent firmware for it that handles the ATtiny10. ___ Reply

[avrdude-dev] [bug #52318] Fuse progamming error

Follow-up Comment #1, bug #52318 (project avrdude): Question is whether this is actually related to the USBasp firmware or to AVRDUDE itself. Do you have a reference to the German forum post you mentioned? Configuration byte 0 bits 7:3 are "reserved", so if you program them away from their defau

[avrdude-dev] [patch #9315] Add PRUSS programmer type for xmega pdi

Follow-up Comment #1, patch #9315 (project avrdude): Basically, a good idea. Documentation patches are missing (either to the .texi or the man page file, preferrably for both). I see a couple of problems with the firmware files though: First, we are guests on the FSF's servers, and they only a

[avrdude-dev] [bug #51015] How to build AVRDUDE with original libftdi

Update of bug #51015 (project avrdude): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: My search engine sa

[avrdude-dev] [patch #9222] Enable silent build

Follow-up Comment #2, patch #9222 (project avrdude): Personally, I'm used to see the verbose messages, but I'm not oppsed to hiding them a bit, as long as there is some clear documentation on how to enable the full messages when anyone wants to see them. It's one of the patches likely to go in

[avrdude-dev] [bug #40831] LUFA AVRISP-MKII fails with avrdude 6.0.1

Update of bug #40831 (project avrdude): Release:None => 6.3 ___ Follow-up Comment #14: The question is not as much as what the state of this bug, but rather when there will be any r

Re: [avrdude-dev] [RFC] XMEGA PDI programming with a AM335x processor

As Enric Balletbo Serra wrote: > Andy, at this point, I also tested the programming several times, I think > is a good idea if I prepare the patches, rebase on top of mainline and send > to the list, so people can give us feedback. Filing them into a patch tracker makes more sense. The list gets

[avrdude-dev] [bug #45115] avrdude 6.0.1 fuse bit display incorrect

Update of bug #45115 (project avrdude): Release:None => 6.0.1 ___ Follow-up Comment #5: It would be good if you spent a couple of more words than being that terse. Maybe you are refer

[avrdude-dev] [bug #50517] Reading fails if "immediate mode" for output file format is selected - fileio: invalid operation=1

Update of bug #50517 (project avrdude): Status:None => Invalid ___ Follow-up Comment #1: Well, "immediate mode" means that instead of providing a filename, you provide the actual data ⨪

Re: [avrdude-dev] [bug #50480] Add support of at*****A devices

As Vasily Trotskyi wrote: > output: > ATmega324PA.atdf > > > > ATmega324P.atdf > > > > > > so only one MCU signatures is not equal for A and non-A versions. Спасибо большое! -- cheers, Joerg .-.-. --... ...-- -

[avrdude-dev] [bug #50480] Add support of at*****A devices

Follow-up Comment #3, bug #50480 (project avrdude): I think there are actually a few devices where Atmel indeed changed the IDs for the A devices. They weren't very consistent in that, alas. That's why I've been asking for someone to take a small survey, and add the result to this bug report

[avrdude-dev] [bug #50480] Add support of at*****A devices

Follow-up Comment #1, bug #50480 (project avrdude): Please, make a survey which devices actually need a different ID at all. I think there are a number of A devices which just use the same ID as their non-A counterparts. Of course, there's nothing wrong with also adding those as aliases as we

[avrdude-dev] [bug #47718] "lfuse reads as" not displayed in verbose mode - SOLUTION

Update of bug #47718 (project avrdude): Status:None => Fixed Assigned to:None => joerg_wunsch Open/Closed:Open => Closed Release:

[avrdude-dev] [bug #50338] avrdude 6.3 fails to set configuration when opening usb device

Update of bug #50338 (project avrdude): Status:None => Fixed ___ Follow-up Comment #1: This is a known issue. Fixed in current code base, by using an entirely different approach tow

[avrdude-dev] [bug #50340] avrdude 6.3 claims that ATXMEGA32A4U has no ISP interface

Update of bug #50340 (project avrdude): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: Xmegas don'{t have

[avrdude-dev] [bug #50087] option parse error: after -U flash:w:program_to_upload.hex, subsequent -V ignored

Update of bug #50087 (project avrdude): Severity: 3 - Normal => 2 - Minor Status:None => Confirmed ___ Follow-up Comment #1: The problem is that

[avrdude-dev] [bug #49898] Config file error for many parts

Update of bug #49898 (project avrdude): Status:None => Duplicate ___ Follow-up Comment #1: This seems to be a duplicate of bug #22248 to me. _

[avrdude-dev] [bug #49740] Bad EEPROM write on Linux 64

Follow-up Comment #5, bug #49740 (project avrdude): That's what I excpected. So it's an issue with recent AVRDUDE versions. ___ Reply to this item at: ___

[avrdude-dev] [bug #49740] Bad EEPROM write on Linux 64

Follow-up Comment #1, bug #49740 (project avrdude): > I tried the same code and the same operations on Windows7 > 64-bit and everything works fine. Same AVRDUDE version, too? ___ Reply to this item at:

[avrdude-dev] [bug #49376] Resource busy error on El Capitan

Follow-up Comment #1, bug #49376 (project avrdude): Maybe the operating system now has some service (or whatever) that is immediately grabbing a TTY device once it appears? Alas, I'm afraid that's nothing which can be solved in AVRDUDE, rather a kind of OS issue. At the very least, it requires s

Re: [avrdude-dev] linuxgpio: typo in snprintf() format string

As 4ernov wrote: > Oh, thank you for pointing out, I've tried to search for some similar > bug in the bugzilla before writing, but missed this one for some > reason. Sorry for disturbing) No problem. Searching the closed bugs in order to see whether it's been reported before is not quite an obv

Re: [avrdude-dev] linuxgpio: typo in snprintf() format string

Привет Алексей, > But it have turned > out, that the problem is with the typo in format string used in > "snprintf()" calls to create gpio pin filename: it specifies "%ud" for > unsigned integer value instead of just "%u" This has already been reported before: https://savannah.nongnu.org/bugs/in

[avrdude-dev] [bug #48776] avrdude attempts to free() an invalid address

Update of bug #48776 (project avrdude): Release:None => 6.3 ___ Follow-up Comment #1: Well, my major problem I'm having with this bug report is, I cannot reproduce it. I've got an

[avrdude-dev] [bug #48776] avrdude attempts to free() an invalid address

Update of bug #48776 (project avrdude): Severity: 3 - Normal => 6 - Security ___ Reply to this item at: ___

[avrdude-dev] [bug #49082] avrdude 6.3 fails with AT90S8515

Update of bug #49082 (project avrdude): Severity: 3 - Normal => 4 - Important ___ Reply to this item at: ___

[avrdude-dev] [bug #49082] avrdude 6.3 fails with AT90S8515

Update of bug #49082 (project avrdude): Release:None => 6.3 ___ Reply to this item at: ___

[avrdude-dev] [bug #49082] avrdude 6.3 fails with AT90S8515

Update of bug #49082 (project avrdude): Status:None => Confirmed ___ Follow-up Comment #1: This appears to have been broken with the elimination of the old "ISP multi" command in SVN r13

[avrdude-dev] [bug #49013] Timeout when using from linux for an arduino uno

Update of bug #49013 (project avrdude): Status: Need Info => None ___ Follow-up Comment #4: So it's at least a recent version. bug #46005 mentions something that looks rather similar to

[avrdude-dev] [bug #48967] incorrect labels on -v output

Update of bug #48967 (project avrdude): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: This bug has been f

[avrdude-dev] [bug #45115] avrdude 6.0.1 fuse bit display incorrect

Update of bug #45115 (project avrdude): Open/Closed:Open => Closed ___ Follow-up Comment #3: Since people report this over and over again, I added a hint about this old bug in the issue tr

[avrdude-dev] [bug #49013] Timeout when using from linux for an arduino uno

Update of bug #49013 (project avrdude): Status:None => Need Info ___ Follow-up Comment #2: Well, the first question here is: which AVRDUDE version are you using, and what is the Arduino

Re: [avrdude-dev] Incorrect FT245R/FT232R Synchronous BitBangMode Programmer shutdown

As Ivan Frederiks wrote: > I noticed that avrdude frequently crashes or hangs on exit when using > 'ftdi_syncbb' based programmers. I investigated this issue and found out > that it is caused by incorrect reader thread cancellation in > ft245r_close(). In attachment you can find patch that solves

[avrdude-dev] [bug #48697] make fails: yacc not found

Follow-up Comment #2, bug #48697 (project avrdude): p.s.: Of course, if someone would want to submit an idea how to rewrite configure.ac to work around that autoconf problem, I'm willing to accept it. However, I'm not in the mood to spend my time into automake workarounds myself, as I've got e

[avrdude-dev] [bug #48697] make fails: yacc not found

Update of bug #48697 (project avrdude): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: Not an AVRDUDE issu

Re: [avrdude-dev] Does powering down SPI disable ISP?

As Rick Mann wrote: > I don't think so, since ISP is done in reset, right? Exactly. -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) ___ avrdu

Re: [avrdude-dev] Creating new parts

As Rick Mann wrote: > In particular, I don't know how to make sure I have the right values > for things like flash_instr, eeprom_instr, pagel, all the myriad > timing properties, proper instruction formatting, etc. Most of that relates to the handling of the various Atmel tools, and best would b

Re: [avrdude-dev] "probably" m16m1?

As Rick Mann wrote: > avrdude: Device signature = 0x1e9484 (probably m16m1) > > Why does it say "probably"? I've defined the part in my .avrduderc. Because the reverse lookup is not guaranteed to be unique. There is no requirement that all devices in avrdude.conf have a unique signature, so d

Re: [avrdude-dev] using HIDAPI for avrdoper

As Axel Simon wrote: > in answer to my own mail, here is a patch that replaces the use of > libusb for interfacing with avrdoper wtih libhidapi. Thanks! Please file it under https://savannah.nongnu.org/task/?func=additem&group=avrdude That makes it easier for me to eventually find it once I ca

Re: [avrdude-dev] [bug #48134] ft245r.c : dispatch/dispatch.h: No such file or directory

As Michal Suchanek wrote: > Presumably the posix semaphore code would work on OSX without > dispatch. I would assume that, too. Anybody willing to test that? -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't h

[avrdude-dev] [bug #48134] ft245r.c : dispatch/dispatch.h: No such file or directory

Follow-up Comment #1, bug #48134 (project avrdude): I'd welcome if you provide the diff output as a so-called "context diff" (diff -u). That makes it a lot easier to follow it. Make sure to specify the original file first, and the modified file second. Can you provide a pointer to OSX docume

[avrdude-dev] [bug #48131] Problem with EEprom address of avrdude for different processors!

Update of bug #48131 (project avrdude): Status:None => Confirmed Assigned to:None => bdean ___ Follow-up Comment #1: The problem is appa

[avrdude-dev] [bug #47988] Can't export GPIO nn, already exported/busy?: Invalid argument

Update of bug #47988 (project avrdude): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: If you look at the

Re: [avrdude-dev] Reading/writing 256rfr2 user signature pages

(Better subscribe to the list to not miss replies.) As Raido Pahtma wrote: > My guess is that it should be possible to achieve without any changes to > avrdude code by simply defining a new memory area in avrdude.conf for > this chip? Unfortunately not. I've opened a placeholder bug report fo

[avrdude-dev] [bug #47780] Single byte read/dump results in zero byte file written [usbtiny]

Update of bug #47780 (project avrdude): Summary: Single byte read/dump results in zero byte file written => Single byte read/dump results in zero byte file written [usbtiny] ___ Follow-up Comment #1: Thanks for the analysi

Re: [avrdude-dev] [patch #8967] Change ft2xx library to ftdi_syncbb instead of libusb

As Didrik Madheden wrote: > I think there is a point to having an official binary with support > FT2xx. It would be for the benefit of exactly those who don't have the > skill or time to build their own avrdude. Well, I already find it quite ironic that there's apparently nobody else but me who i

Re: [avrdude-dev] [patch #8967] Change ft2xx library to ftdi_syncbb instead of libusb

As Xiaofan Chen wrote: > libusb-win32 and libusb-1.0 for Windows are both quite stable now > and have been used by many project. Maybe you are still based > your opinion on the old version of libusb-win32 (0.1.x version) which > was unstable under Windows Vista/7/etc. Алексей, any opinion on that

Re: [avrdude-dev] New programmer support

As Dmitriy Kanareykin wrote: > And the programmer works with Chinese software, so it seems to be the > intended behaviour. OK, in that case, someone would really have to write a new implementation for AVRDUDE. Any chance to ask the Chinese guys for some documentation about the protocol? After

<    1   2   3   4   5   6   7   8   9   10   >