Re: [AVaRICE-user] EDBG/ATATMEL-ICE support

[Philip M. <in...@bi...>]

Hi,
Found a bit of time to try it out. I am running under Windows 7 (sorry!).
Compiled the source without any problems, but I am not sure what I am 
doing wrong.
Just for info, avrdude can see the attached xplainedmini, and 
read/writes OK:
>
> D:\Dropbox\avarice>avrdude -p m168pb -c xplainedmini
> avrdude: AVR device initialized and ready to accept instructions
> Reading | ################################################## | 100% 0.07s
> avrdude: Device signature = 0x1e9415 (probably m168pb)
> avrdude: safemode: Fuses OK (E:FF, H:DF, L:E0)
> avrdude done.  Thank you.
When I try avarice I just get this:
> D:\Dropbox\avarice>avarice -d -4 -w -P m168p :4242
> AVaRICE version 2.13svn20160229, Mar  3 2016 11:51:04
And back to the prompt, without any further messages.
I have tried various variations on the syntax, but they all do the same 
(other than those that are plain wrong on the syntax).
Any idea what I can try?
Br,
Philip


On 03.03.2016 09:06, Joerg Wunsch wrote:
> 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) longer.
>
> However, there's currently still some issue where programming over
> debugWIRE (through GDB's "load" command) doesn't work since AVaRICE
> first attempts a flash erase which is not supported in debugWIRE mode,
> and thus triggers an exception.  Attaching to a pre-flashed device,
> and debugging it, is possible though.
>
> There are some other cases where in some situations exceptions are
> thrown.  These have to be cleaned up before a new release can be
> prepared.


-- 
Bittrace14 UG
Immanuel-Kant Str.59b
31812 Bad Pyrmont

Fax: +49 32223945096

HRB 209338 Amtsger. Hannover

Geschäftsführer
Pauline Atkinson