Hello everyone,
I just migrated the SVN repository to Github.
New location is:
https://github.com/avrdudes/avarice
I have disabled developer write access to the SVN repo, so it remains
merely as a reference for the existing code base (even though I
believe the Git repository to contain
As AVaRICE SVN repository wrote:
> Support code formatting using clang-format
While I agree it's good to have some code formatting rules, please do
not apply code formatting onto arbitrary files just for the purpose of
changing the formatting.
Gratuitously changing just the formatting of some
As Matthias B. wrote:
> I don't know if the output *IDR dirty:... *does have any negative
> effects or how to solve it!? I've just seen this the very first debug
> session, might be not relevant.
It's just an event posted by the ICE, and AVaRICE translates it.
Probably not relevant.
> Starting
As Istvan Retaller wrote:
> > /usr/bin/avr-objcopy -j .text \ -j .data
> > \ -O ihex testburst.out testburst.hex /usr/bin/avrdude -F -c jtag2isp
> > -P usb -B 10 -b 115200 -p t45 -e -U flash:w:testburst.hex -U
> lfuse:w:0x62:m -U hfuse:w:0x9f:m -U efuse:w:0xff:m
Hello *
this is just to inform you that I finally rolled a new release of
AVaRICE, 2.14.
Not much has been done to the code base during the recent four (or so)
years, unfortunately. I've never been fully confident with the state
of EDBG handling (i.e., Atmel-ICE and the EDBG versions found on a
As Marian Buschsieweke wrote:
> the SVN server is now again operational.
Confirmed (as well as the outage before).
--
cheers, Joerg .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)
As Marian Buschsieweke wrote:
> My point is: SourceForge.net is a platform that really scares me away from an
> open source project, no matter how cool it is. Other coders and potential
> contributors may feel the same way about it. Maybe with teahub.io a good
> alternative will (hopefully)
As Stephan Meyer wrote:
> command "reset" [0x12, 0x30]
> 0E 00 0D 00 12 30 00 01
> Received 0x81 0x11 0x00 0x07 0x0e 0x0d
> read: 0e 0d 00 12 a0 00 50
>
> Got message seqno 13 (command_sequence == 13)
> response: 12 A0 00 50
> retrying reset ...
>
> command "reset" [0x12, 0x30]
> 0E 00 0E 00
As Olaf Dreyer wrote:
> But the resulting binary tells me, that it was build without usb support.
> Do I have to make some settings during the configure step?
You need to have a libusb around, including the required headers to
compile against it. On most Linux distributions, this means you'd
As Brian wrote:
> got asynchronous event: 0xf7
> recv: timeout
This is an
#define EVT_ERROR_PHY_RECEIVE_TIMEOUT 0xF7
meaning the debugWIRE transport timed out (between the Dragon
and the target).
> So...is this something to do with telling AVaRICE it's an atmega48 when
> it's
As Tomasz Wawer wrote:
> Please have a look, maybe you could help with this:
Well, I told you that code downloading through debugWIRE
currently doesn't work, neither in AVRDUDE nor in AVaRICE
through GDB's "load" command.
Sorry, I have no real idea so far *why* it fails. It pretends
to
As Philip Mulrane wrote:
> I don't actually have a PC-based Linux installation (would avarice run
> on a Raspberry Pi?
I never tried it, but I think it might run there, provided libusb and
libhidapi are available. In addition, the only resources AVaRICE is
using are pipes and Posix threads,
As sq5rix wrote:
> Now it works (Ubuntu 14.04)
>
> Sorry for trouble, it was some transient error. --debug helped!
I'm glad it works, good luck!
73!
--
cheers, Joerg .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/
Never trust an operating system you don't have
As Tomek wrote:
> Then I invoked
> $ avarice --edbg --debugwire --ignore-intr :4242
>
>
> AVaRICE version 2.13svn20160229, Mar 3 2016 14:04:24
> JTAG config starting.
> Found a device, serial number: J41800031019
> initJtagBox() failed: JTAG ICE timeout exception
Hmm, so far I tried it on
As Philip Mulrane wrote:
> For what it's worth, the XplainedMini appears in Microsofts USB Device
> Viewer utility, and when I installed the filter for libUsb for the
> relevant endpoints of the XplainedMini, they also showed up in
> "install-filter-win.exe"
Yes, it appears there, but it
As Philip Mulrane wrote:
> Can this also be used with the mEDBG of the xlpained mini? It
> apparently supports debug wire?
Yes, I added fragmentation / reassembly support yesterday, which
is required for mEDBG since they only support 64 bytes endpoint
size, and some transfers are (much)
As Element Green wrote:
> Thank you for your reply. I downgraded the firmware to 7.21 (from AVR
> Studio 5).
I just upgraded another Dragon to 7.38 (decimal), and it works without
troubles using AVaRICE (SVN version) on my ATxmega16D4 board.
> I attempted to use the Dragon to connect to 2
As Element Green wrote:
> command[0x02, 1]: 02 03 06
> recv: 0x1b
> recv: 0x01
> recv: 0x00
> recv: 0x01
> recv: 0x00
> recv: 0x00
> recv: 0x00
> recv: 0x0e
> sDATA: reading 1 bytes
> read: ae
> recv: 0xb1
> recv: 0x4b
> CRC OK
> Got message seqno 1 (command_sequence == 1)
> response: AE
> set
As Wiebe Cazemier wrote:
> It is kind of unclear (to me) whether the new Atmel-ICE debugger
> ([2]) is supported by AvaRICE or not.
Unfortunately not (not yet).
> I would get a JTAGICE3
> instead, but it's no longer available. Plus, there is some concern
> ([1]) that Atmel is going to release a
As Wojtek wrote:
I tried to add symlink for my device according to post:
You are not supposed to add that symlink, you completely
misunderstood.
This link is only meaningful for devices which are accessed through a
standard serial port, like the first JTAGICE, or the JTAGICEmkII when
connected
As Andreas Løhre wrote:
I have attached an strace for 4.6.3 (same behaviour as 4.7.2), but I won't
be able to do the one for 4.7/4.4/4.5 before tomorrow.
Thanks to all who helped narrowing this down.
I could eventually reproduce it myself with a GCC 4.7, and then find
and fix it.
It's been a
As Andreas Løhre wrote:
I was still not able to start a session
on the 1284P.
OK, I'm interested in seeing the debug traces for that.
--
cheers, Jorg .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/NIC: JW11-RIPE
Never trust an operating
As Andreas Løhre wrote:
The full output is:
An interesting list, thanks!
[jtag2rw.cc:180]: (error) Memory leak: response
[jtag3rw.cc:182]: (error) Memory leak: response
Both these are actually the same (with the jtag3 code being cloned
from the jtag2 implementation). All this looks
As Francois Lorrain wrote:
That's why I am calling my modification a hack :-) I couldn't even figure
out how to tell the configure script to look for libusb-1.0 instead of
libusb.
Have a look into AVRDUDE's configure.ac, I've already done it there.
For the regular command / response
As threatened before, I just released version 2.13, after applying a
number of outstanding patches. Enjoy!
Here's the top of the NEWS file:
# $Id: NEWS 308 2012-11-05 16:41:14Z joerg_wunsch $
Summary of changes in AVaRICE 2.13
==
. Rearrange the entire error
As Joerg Wunsch wrote:
Given that the changes are a little more intrusive than they used to
be in previous releases, I'd ask everyone to give the release
candidate a try.
According to Sourceforge's download statistics, a number of people
downloaded both, the source tarball as well
Thanks to Detlev Kraft's reverse engineering of the way AVR Studio 5
talks with the JTAGICEmkII/AVRDRAGON, and thanks to his detailed
analysis of that communication, I could add support for ICE firmware
versions 7.x to AVaRICE. (With Detlev's permission, I added his
document to the doc/ folder in
As Joerg Wunsch wrote:
Now that AVaRICE 2.11 has been shipped, I'd consider changing away
from CVS. ...
..., I'd rather simply use Subversion which I'm
most used to.
I finally did it. AVaRICE is using Subversion now!
Please do no longer use the old CVS repository. (I disabled
As Paul Klapperich wrote:
On the other hand, Subversion does have a long known random commit
corruption bug, which makes an old commit and a few after it
unusable.
Interesting, thanks for the warning. I've never heard about (or
experienced) that myself.
That might be
reason enough to stay
As Detlev Kraft wrote:
A communication analysis between Avarice Dragon and on the other
hand Studio5 Dragon shows a lot of differences.
Thanks so much for analyzing this, Detlev!
There are new, undocumented
commands and parameters(Avr-Note 067). Avarice is not usable anymore!
Curious:
30 matches
Mail list logo
