In jtag3::deviceAutoConfig(), fix constructor syntax
Test product_string not nullptr before comparison
ATmega328 entry for avrdude.conf
Correct. Besides, the ATmega328 used to be supported by AVRDUDE already by the time this patch was submitted.
Yep, it is. Feel free to close this bug ticket.
AVaRICE 2.14 won't compile on Arch Linux
Fixed by patch #40
Remove old style exception throw specifier
As simple as such. ;-) Thanks a lot, applied in r391.
patch #40 Remove old style exception throw specifier
I'm willing to review and apply a patch, but my C++ knowledge (in particular regarding modern C++) is close to 0, so without a lot of Internet research, I wouldn't know how to fix that properly right now.
Well, frankly, I'd very much prefer to have a patch fixing the source code so it compiles on a newer compiler without warnings, rather than back-dating the compiler.
2.14 compiling issues and atmel-ice usb not found
You write you are trying to compile AVaRICE 2.14, but your final command messages indicate it's actually 2.12. Also, all the compile errors you mentioned seem to be old ones that have been fixed in the current codebase.
avarice segmentation fault
My own JTAGICEmkI clone is ready now. However, I cannot seem to make it stop at any breakpoint. I don't have the time to track that down right now, but will for sure keep the bug report open so it can be fixed before the next release.
Thanks for the analysis! My own mkI clone is still on its way, once here, I'll test that. @Mate Varga: the fix will the surely be in the next release (whenever that will happen ;). For the time being, you could try whether Kamil's fix solves your issue.
Sorry, since your trace doesn't have debugging symbols - I need to build my own mkI ICE clone first, and then try reproducing the error.
Nope, the current version is supposed to support the "MkI" version, so we either have to declare it unsupported (and refer to an older version then), or we fix the bug. I'd prefer the latter, and as such, your bug report is welcome. But unless you can trace that yourself completely down to the respective source code line, I have to reproduce it first.
Turn that "gdb avarice" into a "gdb ./path/to/your/compiled/avarice". I'm afraid you might debug the one found in $PATH rather than your compilation.
Offhand not. The stack trace has symbols now, but it lacks debugging symbols (compiler option -g). Unfortunately, jtag::layoutBreakpoints() performs a lot of actions on arrays where a memory access violation could happen. Can you verify your compilation included a -g option? I'm afraid I first have to build my own ICE for that.
Unfortunately, I forgot: without AVaRICE having full debugging symbols, the stack trace is pretty useless. :-( Can you compile AVaRICE yourself from sourcecode? If so, please re-run the test, and use the in-tree version (rather than an installed one) for the stack trace.
OK, an old ("mkI") - I don't have one here readily available for testing. Maybe I can jumper some compatible clone on an STK500. In order to debug AVaRICE, you have to run it under control of the host system's GDB (not AVR-GDB). Just start it (in a separate terminal window) like gdb avarice (gdb) run -1 -j /dev/ttyUSB0 :4242 -P atmega32 -d then connect AVR-GDB to it. Once it crashed, type bt in that GDB window.
Well, a lot of information is missing. What kind of debug adapter is used, what's the exact commandline to start AVaRICE? Ideally, I'd be interested in a stack trace from the coredump; GDB can be used to analyze the coredump file
Compilation error in jtag3io.cc: (avarice 2.14)
Well, the AX_GCC_VAR_ATTRIBUTE was missing in my autoconf version. Thus I decided it's easier to simply replace__unused by __attribute__((unused)) in the few places where it's being used.
patch #39 Compilation error in jtag3io.cc: (avarice 2.14)
Bump release number to post-2.14
AVaRICE release 2.14
Bump release number to 2.14.
Fix logic behind the "generic" parameter: true by default
Support for ATMEL ICE debugger?!
The respective code is going to be in the next release, so closing this now.
Unknown device is not clearly named
Added in r385
bug #22 Unknown device is not clearly named
error: use of undeclared identifier 'bfd_get_section_name'
Applied in r384, thanks!
Submitted by Ryan Schmidt:
Deprecated feature used as example of Avarice use
Applied in r383, thanks!
Submitted by Jack Bradach:
Fix build with clang 6
This has been replaced by throwing an exception.
result of comparison of constant 0 with expression of type 'bool' is always false
Fixed in r382 (together with a number of other warnings).
address of array will always evaluate to 'true'
This has been fixed quite some time ago.
Silence all warnings
Fix build error if ENABLE_TARGET_PROGRAMMING is on
Applied in rev 381, thanks!
Submitted by MJH:
Man page fixes
Applied in rev 380, thanks!
Spelling fixes
Applied in rev 380, thanks!
Man pages for start-avarice
Applied in rev 380, thanks!
Man page for kill-avarice
Applied in rev 380, thanks!
Submitted by Christian Kastner:
adds atxmega32e5
Applied in rev 379, thanks!
Add support for atxmega8e5
Applied in rev 379, thanks!
Submitted by Mark Rages and nichtleiter:
Fix inconsistent naming between struct and class jtag
Patch to support XMEGA64A3
Integrated in rev 377, thanks!
Submitted by Uwe Frank:
configure.ac overwrites variable if both enable-warnings and enable-target-programming is specififed
Applied with minor modifications (no need for additional leading whitespace in variables). Thanks!
Submitted by Tobias Frost:
Fix build with llvm 11.0.0
Actually, this bug has been fixed long ago in the tree, as part of merging the EDBG changes. So seems it's really high time to finally roll a new release, even though I'm not fully happy wit hthe stability of EDBG.
Submitted by Fabian Blaese:
Update to match reality.
Bump timeout in HID reads a bit.
Remember you need to run ./Bootstrap before. Please report about any success or failure...
Support for the Atmel-ICE is already in SVN, but I'm not that excited yet about the...
In openhid(), Correctly calculate the part
Debugwire development branch for Jes Bodi Klinke.
The DebugWire protocol does not support setting fuses That's not the point. The point...
in eraseProgramMemory(), bail out if running on...
Merge r362/363 that have accidentally been comm...
Omit chip erase when operating on debugWIRE con...
Mark jtag3::doSimpleJtagCommand() as throwing e...
Implement packet fragmentation and reassembly (...
Determine max. HID transfer size from DAP_Info
Bump version date after merging jwunsch_edbg br...
Merge the jwunsch_edbg branch back to trunk.
Minor fixes:
Fix packet size when passing event upstream.
Implement libhidapi support for EDBG-based devi...
First part of adding libhidapi support.
Summary: Fix ATmega32M1/32C1 IO register entries.
Add hooks for libhidapi.
Attempt from mid-2015 to start an EDBG implemen...
Submitted by Jakub Kramarz:
Submitted by Uwe Frank <frank@drello.de>: