avarice-user — AVaRICE Users

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

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

I don't actually have a PC-based Linux installation (would avarice run 
on a Raspberry Pi? If so, then I could try this tomorrow). If I need to 
have a PC based Linux install, it could take a bit longer as I will set 
up and install a virtual PC for this (don't mind doing so), will need to 
take care of it during the coming week. Are there any recommended 
Virtual PC solutions that are better from the point of view that the USB 
will also be virtual?

On 06.03.2016 13:13, Joerg Wunsch wrote:
> As Philip Mulrane wrote:
>
>> I'm on Windows 7, compiling
>> under Cygwin.
> OK, then we have to make sure it's not a Cygwin issue.
>
> Can you try somehow the same board under Linux?
>
> It's not that I wouldn't mind getting it running under Cygwin,
> but my first priority are unixoide systems (Linux, OSX, FreeBSD),
> because Windows users always could resort to Atmel Studio, while
> Unix users can't.

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

[Joerg W. <j...@ur...>]

As Philip Mulrane wrote:

> I'm on Windows 7, compiling 
> under Cygwin.

OK, then we have to make sure it's not a Cygwin issue.

Can you try somehow the same board under Linux?

It's not that I wouldn't mind getting it running under Cygwin, 
but my first priority are unixoide systems (Linux, OSX, FreeBSD), 
because Windows users always could resort to Atmel Studio, while 
Unix users can't.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

OK,
The response of the Sam D20 is of course correct (d'Oh!), BTW, I have 
tried this board with OpenOCD and it's fine. I'm on Windows 7, compiling 
under Cygwin.
The 500ms delay was actually changed to 900ms and not *19 (like the 
others). I redid the test with 5000ms, and now we get a different 
response when using -d:
>
> D:\Dropbox\avarice>avarice.exe -4 -d :4242
> AVaRICE version 2.13svn20160229, Mar  6 2016 00:46:22
>
> Defaulting JTAG bitrate to 250 kHz.
>
> Found HID PID:VID 0x03eb:0x2145Probing for HID max. packet size
> Setting max. packet size to 64 from DAP_Info
> JTAG config starting.HID thread started
>
> command "sign-on" [0x01, 0x10]
> 0E 00 00 00 01 10 00
> Received 0x81 0x11 0x00 0x06 0x0e 0x00
> read:  0e 00 00 01 80 00
>
> Got message seqno 0 (command_sequence == 0)
> response: 01 80 00
>
> command "get info (serial number)" [0x00, 0x00]
> 0E 00 01 00 00 00 00 81
> Received 0x81 0x11 0x00 0x1a 0x0e 0x01
> read:  0e 01 00 00 81 00 41 54 4d 4c 32 32 32 32 30 35 30 32 30 30 30 
> 30 33 36 33 ff
>
> Got message seqno 1 (command_sequence == 1)
> response: 00 81 00 41 54 4D 4C 32 32 32 32 30 35 30 32 30 30 30 30 33 
> 36 33 FF
> Found a device, serial number: ATML222205020000363▒
>
> command "get parameter" [0x01, 0x02]
> 0E 00 02 00 01 02 00 00 00 05
> Received 0x81 0x11 0x00 0x0c 0x0e 0x02
> read:  0e 02 00 01 84 01 00 01 04 3b 00 00
>
> Got message seqno 2 (command_sequence == 2)
> response: 01 84 01 00 01 04 3B 00 00
> ICE hardware version: 0
> ICE firmware version: 1.04 (rel. 59)
>
> command "set parameter" [0x12, 0x01]
> 0E 00 03 00 12 01 00 00 00 01 02
> Received 0x81 0x11 0x00 0x06 0x0e 0x03
> read() timed out
> set paramater command failed: JTAG ICE timeout exception
> initJtagBox() failed: JTAG ICE timeout exception
>
> command "sign-off" [0x01, 0x11]
> 0E 00 03 00 01 11 00
> unexpected message size from pipe: 301990670
>
> command "sign-off" [0x01, 0x11]
> 0E 00 03 00 01 11 00
> Received 0x81 0x11 0x00 0x06 0x0e 0x03
> unexpected message size from pipe: 393344
>
> command "sign-off" [0x01, 0x11]
> 0E 00 03 00 01 11 00
> unexpected message size from pipe: 51249152
>
> command "sign-off" [0x01, 0x11]
> 0E 00 03 00 01 11 00
> Received 0x81 0x11 0x00 0x06 0x0e 0x03
> unexpected message size from pipe: 8388864
>
> command "sign-off" [0x01, 0x11]
> 0E 00 03 00 01 11 00
> read:  0e 03 00 01 80 00
>
> Got message seqno 3 (command_sequence == 3)
> Received 0x81 0x11 0x00 0x06 0x0e 0x03
> response: 01 80 00
>
> D:\Dropbox\avarice>

On 06.03.2016 12:05, Joerg Wunsch wrote:
> As Philip Mulrane wrote:
>
>> In jtag2usb.cc I changed all hid_read_timeout() calls (I assume this is
>> what you meant), increasing the timeout parameter by a factor of 10.
> Ah, yes, of course, hid_read_timeout().  Actually, only one call
> matters here, the one inside the (fragment reassembly) loop after
>
> // Query response
>
> The timeout there is currently 500 ms, which I thought ought to be
> enough, even for things like writing flash pages (which currently
> doesn't work for debugWIRE targets, not even in AVRDUDE – I don't
> know what I'm doing wrong by now).
>
>> The
>> output (-d) looked identical, same error.
> This is quite strange, because apparently, in your original mail, the
> next query for an event (which is always being polled while no command
> request is being worked on) yielded the command response:
>
>> command "AVR sign-on" [0x12, 0x10]
>> 0E 00 06 00 12 10 00 00
>> Querying for response: hid_read() failed (0)
>> Querying for event: unexpected response (0x81)
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> So why does it not arrive at the point where we are asking for it?
>
> Is this on Linux?  Perhaps you could trace the underlying USB
> transport using Wireshark there to get an idea what's happening.
>
> We could perhaps turn this into a state machine that correctly
> files the responses received, depending on their ID field (command
> response vs. event respsonse), but I'd like to try keeps simple if
> possible.  We first have to understand why it's not working in the
> first place.
>
> If you completely fail, I'd kindly ask you for getting me your board
> (I could get you one of mine in exchange, Atmel kindly sponsored me
> some XplainedMini so I could develop AVRDUDE for them).  I've got an
> USB analyzer here, perhaps that helps debugging.
>
>> I also tried with a Sam D20
>> xplained pro, and it fails also, but it fails more or less immediately.
>> This is the output of -d (for the Sam d20):
>>> command "AVR sign-on" [0x12, 0x10]
>>> 0E 00 06 00 12 10 00 00
>>> Received 0x81 0x11 0x00 0x07 0x0e 0x06
>>> read:  0e 06 00 12 a0 00 20
>>>
>>> Got message seqno 6 (command_sequence == 6)
>>> response: 12 A0 00 20
>>> initJtagBox() failed: no answer from target
> Here, the response arrives without any problems within
> those 500 ms timeout.  It's just that the response (in
> essence) tells you that the target does not respond since
> it is not an AVR, but you're trying to talk to it as an AVR
> device.  So, this is expected behaviour.

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

[Joerg W. <j...@ur...>]

As Philip Mulrane wrote:

> In jtag2usb.cc I changed all hid_read_timeout() calls (I assume this is 
> what you meant), increasing the timeout parameter by a factor of 10.

Ah, yes, of course, hid_read_timeout().  Actually, only one call 
matters here, the one inside the (fragment reassembly) loop after

// Query response

The timeout there is currently 500 ms, which I thought ought to be 
enough, even for things like writing flash pages (which currently 
doesn't work for debugWIRE targets, not even in AVRDUDE – I don't 
know what I'm doing wrong by now).

> The 
> output (-d) looked identical, same error.

This is quite strange, because apparently, in your original mail, the 
next query for an event (which is always being polled while no command 
request is being worked on) yielded the command response:

> command "AVR sign-on" [0x12, 0x10]
> 0E 00 06 00 12 10 00 00
> Querying for response: hid_read() failed (0)
> Querying for event: unexpected response (0x81)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So why does it not arrive at the point where we are asking for it?

Is this on Linux?  Perhaps you could trace the underlying USB 
transport using Wireshark there to get an idea what's happening.

We could perhaps turn this into a state machine that correctly 
files the responses received, depending on their ID field (command 
response vs. event respsonse), but I'd like to try keeps simple if 
possible.  We first have to understand why it's not working in the 
first place.

If you completely fail, I'd kindly ask you for getting me your board 
(I could get you one of mine in exchange, Atmel kindly sponsored me 
some XplainedMini so I could develop AVRDUDE for them).  I've got an 
USB analyzer here, perhaps that helps debugging.

> I also tried with a Sam D20 
> xplained pro, and it fails also, but it fails more or less immediately.  

> This is the output of -d (for the Sam d20):
> > command "AVR sign-on" [0x12, 0x10]
> > 0E 00 06 00 12 10 00 00
> > Received 0x81 0x11 0x00 0x07 0x0e 0x06
> > read:  0e 06 00 12 a0 00 20
> >
> > Got message seqno 6 (command_sequence == 6)
> > response: 12 A0 00 20
> > initJtagBox() failed: no answer from target

Here, the response arrives without any problems within 
those 500 ms timeout.  It's just that the response (in 
essence) tells you that the target does not respond since 
it is not an AVR, but you're trying to talk to it as an AVR 
device.  So, this is expected behaviour.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

In jtag2usb.cc I changed all hid_read_timeout() calls (I assume this is 
what you meant), increasing the timeout parameter by a factor of 10. The 
output (-d) looked identical, same error. I also tried with a Sam D20 
xplained pro, and it fails also, but it fails more or less immediately.  
This is the output of -d (for the Sam d20):
> D:\Dropbox\avarice>avarice.exe -d -4 :4242
> AVaRICE version 2.13svn20160229, Mar  6 2016 00:46:22
>
> Defaulting JTAG bitrate to 250 kHz.
>
> Found HID PID:VID 0x03eb:0x2111, serno ATML1873040200010208
> Probing for HID max. packet size
> Setting max. packet size to 512 from DAP_Info
> JTAG config starting.HID thread started
>
>
> command "sign-on" [0x01, 0x10]
> 0E 00 00 00 01 10 00
> Received 0x81 0x11 0x00 0x06 0x0e 0x00
> read:  0e 00 00 01 80 00
>
> Got message seqno 0 (command_sequence == 0)
> response: 01 80 00
>
> command "get info (serial number)" [0x00, 0x00]
> 0E 00 01 00 00 00 00 81
> Received 0x81 0x11 0x00 0x1a 0x0e 0x01
> read:  0e 01 00 00 81 00 41 54 4d 4c 31 38 37 33 30 34 30 32 30 30 30 
> 31 30 32 30 38
>
> Got message seqno 1 (command_sequence == 1)
> response: 00 81 00 41 54 4D 4C 31 38 37 33 30 34 30 32 30 30 30 31 30 
> 32 30 38
> Found a device, serial number: ATML1873040200010208
>
> command "get parameter" [0x01, 0x02]
> 0E 00 02 00 01 02 00 00 00 05
> Received 0x81 0x11 0x00 0x0c 0x0e 0x02
> read:  0e 02 00 01 84 01 f0 01 21 1d 01 00
>
> Got message seqno 2 (command_sequence == 2)
> response: 01 84 01 F0 01 21 1D 01 00
> ICE hardware version: 240
> ICE firmware version: 1.33 (rel. 285)
>
> command "set parameter" [0x12, 0x01]
> 0E 00 03 00 12 01 00 00 00 01 02
> Received 0x81 0x11 0x00 0x06 0x0e 0x03
> read:  0e 03 00 12 80 00
>
> Got message seqno 3 (command_sequence == 3)
> response: 12 80 00
>
> command "set parameter" [0x12, 0x01]
> 0E 00 04 00 12 01 00 00 01 01 02
> Received 0x81 0x11 0x00 0x06 0x0e 0x04
> read:  0e 04 00 12 80 00
>
> Got message seqno 4 (command_sequence == 4)
> response: 12 80 00
>
> command "set parameter" [0x12, 0x01]
> 0E 00 05 00 12 01 00 01 00 01 04
> Received 0x81 0x11 0x00 0x06 0x0e 0x05
> read:  0e 05 00 12 80 00
>
> Got message seqno 5 (command_sequence == 5)
> response: 12 80 00
>
> command "AVR sign-on" [0x12, 0x10]
> 0E 00 06 00 12 10 00 00
> Received 0x81 0x11 0x00 0x07 0x0e 0x06
> read:  0e 06 00 12 a0 00 20
>
> Got message seqno 6 (command_sequence == 6)
> response: 12 A0 00 20
> initJtagBox() failed: no answer from target
>
> command "sign-off" [0x01, 0x11]
> 0E 00 07 00 01 11 00
> Received 0x81 0x11 0x00 0x06 0x0e 0x07
> read:  0e 07 00 01 80 00
>
> Got message seqno 7 (command_sequence == 7)
> response: 01 80 00
>
> D:\Dropbox\avarice>

On 06.03.2016 10:06, Joerg Wunsch wrote:
> As Philip Mulrane wrote:
>
>>> command "AVR sign-on" [0x12, 0x10]
>>> 0E 00 06 00 12 10 00 00
>>> Querying for response: hid_read() failed (0)
> Try increasing the timeout parameter in hid_read().
>
> Actually, when getting a 0 reply, we could probably also
> loop, but then, we could as well increase the timeout, and
> have libhidapi loop instead.


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

Fax: +49 32223945096

HRB 209338 Amtsger. Hannover

Geschäftsführer
Pauline Atkinson

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

[Joerg W. <j...@ur...>]

As Philip Mulrane wrote:

> > command "AVR sign-on" [0x12, 0x10]
> > 0E 00 06 00 12 10 00 00
> > Querying for response: hid_read() failed (0)

Try increasing the timeout parameter in hid_read().

Actually, when getting a 0 reply, we could probably also 
loop, but then, we could as well increase the timeout, and 
have libhidapi loop instead.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

OK,
One step further, set up my Cygwin somewhat better, and now I get this 
(this is on an xplained mini with medbg). Any ideas?
Br,
Philip
> AVaRICE version 2.13svn20160229, Mar  6 2016 00:46:22
>
> JTAG config starting.
> Found a device, serial number: ATML222205020000363▒
> initJtagBox() failed: JTAG ICE timeout exception
With -d. I get this:
> D:\Dropbox\avarice>avarice.exe -d -4 -w :4242
> AVaRICE version 2.13svn20160229, Mar  6 2016 00:46:22
>
> Found HID PID:VID 0x03eb:0x2145Probing for HID max. packet size
> Setting max. packet size to 64 from DAP_Info
> JTAG config starting.HID thread started
>
>
> command "sign-on" [0x01, 0x10]
> 0E 00 00 00 01 10 00
> Received 0x81 0x11 0x00 0x06 0x0e 0x00
> read:  0e 00 00 01 80 00
>
> Got message seqno 0 (command_sequence == 0)
> response: 01 80 00
>
> command "get info (serial number)" [0x00, 0x00]
> 0E 00 01 00 00 00 00 81
> Received 0x81 0x11 0x00 0x1a 0x0e 0x01
> read:  0e 01 00 00 81 00 41 54 4d 4c 32 32 32 32 30 35 30 32 30 30 30 
> 30 33 36 33 ff
>
> Got message seqno 1 (command_sequence == 1)
> response: 00 81 00 41 54 4D 4C 32 32 32 32 30 35 30 32 30 30 30 30 33 
> 36 33 FF
> Found a device, serial number: ATML222205020000363▒
>
> command "get parameter" [0x01, 0x02]
> 0E 00 02 00 01 02 00 00 00 05
> Received 0x81 0x11 0x00 0x0c 0x0e 0x02
> read:  0e 02 00 01 84 01 00 01 04 3b 00 00
>
> Got message seqno 2 (command_sequence == 2)
> response: 01 84 01 00 01 04 3B 00 00
> ICE hardware version: 0
> ICE firmware version: 1.04 (rel. 59)
>
> command "set parameter" [0x12, 0x01]
> 0E 00 03 00 12 01 00 00 00 01 01
> Received 0x81 0x11 0x00 0x06 0x0e 0x03
> read:  0e 03 00 12 80 00
>
> Got message seqno 3 (command_sequence == 3)
> response: 12 80 00
>
> command "set parameter" [0x12, 0x01]
> 0E 00 04 00 12 01 00 00 01 01 02
> Received 0x81 0x11 0x00 0x06 0x0e 0x04
> read:  0e 04 00 12 80 00
>
> Got message seqno 4 (command_sequence == 4)
> response: 12 80 00
>
> command "set parameter" [0x12, 0x01]
> 0E 00 05 00 12 01 00 01 00 01 05
> Received 0x81 0x11 0x00 0x06 0x0e 0x05
> read:  0e 05 00 12 80 00
>
> Got message seqno 5 (command_sequence == 5)
> response: 12 80 00
>
> command "AVR sign-on" [0x12, 0x10]
> 0E 00 06 00 12 10 00 00
> Querying for response: hid_read() failed (0)
> Querying for event: unexpected response (0x81)
> read() timed out
> initJtagBox() failed: JTAG ICE timeout exception
>
> command "sign-off" [0x01, 0x11]
> 0E 00 06 00 01 11 00
> Received 0x80 0x01 0x00 0x07 0x0e 0x06
> Querying for response: unexpected response (0x82)
> Querying for event: unexpected response (0x81)
> read() timed out
>
> -----last block repeats 7 times--------
>
> command "sign-off" [0x01, 0x11]
> 0E 00 06 00 01 11 00
> Received 0x80 0x01 0x00 0x06 0x0e 0x06
> Querying for response: unexpected response (0x82)
> Querying for event: unexpected response (0x81)
> read() timed out

Re: [AVaRICE-user] Atmel ICE issue

[Joerg W. <j...@ur...>]

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 sources for. ;-)

Re: [AVaRICE-user] Atmel ICE issue

[sq5rix <sq...@gm...>]

Hi again! 

Now it works (Ubuntu 14.04) 

Sorry for trouble, it was some transient error. --debug helped! 

I try to connect avr-gdb now :) 

Greetings,
Tom 

On 04 Mar 2016, at 21:06, Tomek <sq...@gm...> wrote:

Hi!

I was so happy to see avarice with Atmel ICE support (I stay out of windows till the last drop of blood :) 

I compile hidapi from the source, I could connect to Atmel ICE in the testgui

I compiled latest AVaRICE version 2.13svn20160229 without any problems. 

I set the debugWire fuse with 
~/avrdude-6.3/obj-avr/avrdude -pm328p -catmelice_isp -v -U hfuse:w:0x9E:m

I checked, if it is set, it was.  

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
$

What do I miss? 

Greetings,
Tom

Re: [AVaRICE-user] Atmel ICE issue

[Joerg W. <j...@ur...>]

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 FreeBSD and Linux (Ubuntu 14.04), where it
worked:

% ./src/avarice --edbg --debugwire --ignore-intr :4242
AVaRICE version 2.13svn20160229, Mar  3 2016 21:50:21

JTAG config starting.
Found a device, serial number: ATML2323040200015056
Reported device ID: 0x950F
Configured for device ID: 0x950F atmega328p
JTAG config complete.
Preparing the target device for On Chip Debugging.
Waiting for connection on port 4242.

Here's the trace with --debug:

% ./src/avarice --edbg --debugwire --ignore-intr --debug :4242
AVaRICE version 2.13svn20160229, Mar  3 2016 21:50:21

Found HID PID:VID 0x03eb:0x2145, serno ATML2323040200015056
Probing for HID max. packet size
Setting max. packet size to 64 from DAP_Info
HID thread started
JTAG config starting.

command "sign-on" [0x01, 0x10]
0E 00 00 00 01 10 00 
Received 0x81 0x11 0x00 0x06 0x0e 0x00
read:  0e 00 00 01 80 00

Got message seqno 0 (command_sequence == 0)
response: 01 80 00 

command "get info (serial number)" [0x00, 0x00]
0E 00 01 00 00 00 00 81 
Received 0x81 0x11 0x00 0x1a 0x0e 0x01
read:  0e 01 00 00 81 00 41 54 4d 4c 32 33 32 33 30 34 30 32 30 30 30 31 35 30 35 36

Got message seqno 1 (command_sequence == 1)
response: 00 81 00 41 54 4D 4C 32 33 32 33 30 34 30 32 30 30 30 31 35 30 35 36 
Found a device, serial number: ATML2323040200015056

command "get parameter" [0x01, 0x02]
0E 00 02 00 01 02 00 00 00 05 
Received 0x81 0x11 0x00 0x0c 0x0e 0x02
read:  0e 02 00 01 84 01 00 01 04 3b 00 00

Got message seqno 2 (command_sequence == 2)
response: 01 84 01 00 01 04 3B 00 00 
ICE hardware version: 0
ICE firmware version: 1.04 (rel. 59)

command "set parameter" [0x12, 0x01]
0E 00 03 00 12 01 00 00 00 01 01 
Received 0x81 0x11 0x00 0x06 0x0e 0x03
read:  0e 03 00 12 80 00

Got message seqno 3 (command_sequence == 3)
response: 12 80 00 

command "set parameter" [0x12, 0x01]
0E 00 04 00 12 01 00 00 01 01 02 
Received 0x81 0x11 0x00 0x06 0x0e 0x04
read:  0e 04 00 12 80 00

Got message seqno 4 (command_sequence == 4)
response: 12 80 00 

command "set parameter" [0x12, 0x01]
0E 00 05 00 12 01 00 01 00 01 05 
Received 0x81 0x11 0x00 0x06 0x0e 0x05
read:  0e 05 00 12 80 00

Got message seqno 5 (command_sequence == 5)
response: 12 80 00 

command "AVR sign-on" [0x12, 0x10]
0E 00 06 00 12 10 00 00 
Received 0x81 0x11 0x00 0x0b 0x0e 0x06
read:  0e 06 00 12 84 00 0f 95 00 00 00

Got message seqno 6 (command_sequence == 6)
response: 12 84 00 0F 95 00 00 00 
AVR sign-on responded with device ID = 0x950F
Reported device ID: 0x950F
Configured for device ID: 0x950F atmega328p
Automatic device detection: 
command "set parameter" [0x12, 0x01]
0E 00 07 00 12 01 00 02 00 1F 80 00 00 80 00 00 00 00 00 00 00 3F 00 00 00 01 00 04 04 01 01 00 00 00 00 22 21 1F 20 00 46 
Received 0x81 0x11 0x00 0x06 0x0e 0x07
read:  0e 07 00 12 80 00

Got message seqno 7 (command_sequence == 7)
response: 12 80 00 
JTAG config complete.
Preparing the target device for On Chip Debugging.

command "set parameter" [0x12, 0x01]
0E 00 08 00 12 01 00 03 00 01 00 
Received 0x81 0x11 0x00 0x06 0x0e 0x08
read:  0e 08 00 12 80 00

Got message seqno 8 (command_sequence == 8)
response: 12 80 00 

command "start debugging" [0x12, 0x13]
0E 00 09 00 12 13 00 01 
Received 0x81 0x11 0x00 0x06 0x0e 0x09
read:  0e 09 00 12 80 00

Got message seqno 9 (command_sequence == 9)
response: 12 80 00 

command "reset" [0x12, 0x30]
0E 00 0A 00 12 30 00 01 
Received 0x81 0x11 0x00 0x06 0x0e 0x0a
read:  0e 0a 00 12 80 00

Got message seqno 10 (command_sequence == 10)
response: 12 80 00 
read:  0e 00 02 00 12 40 c5 01 00 00 01 00 00
Event serial 0x0002
ignoring break event
Waiting for connection on port 4242.

Try finding out where it fails.  Maybe it's some kind of timing issue.

73!
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

[AVaRICE-user] Atmel ICE issue

[Tomek <sq...@gm...>]

Hi!

I was so happy to see avarice with Atmel ICE support (I stay out of 
windows till the last drop of blood :)

I compile hidapi from the source, I could connect to Atmel ICE in the 
testgui

I compiled latest AVaRICE version 2.13svn20160229 without any problems.

I set the debugWire fuse with
~/avrdude-6.3/obj-avr/avrdude -pm328p -catmelice_isp -v -U hfuse:w:0x9E:m

I checked, if it is set, it was.

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
$

What do I miss?

Greetings,
Tom

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

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

OK,
Looks like configure removed libhidapi from the build. Some work for me 
to do.....
Br,
Philip
> configure:5899: gcc -o conftest.exe -g -O2   conftest.c -lusb -lbfd 
> -liberty -lintl -liconv >&5
> /tmp/ccJaFs6k.o: In function `main':
> /cygdrive/c/tmp/avarice/conftest.c:27: undefined reference to `hid_init'
> collect2: error: ld returned 1 exit status
> configure:5899: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "avarice"
> ............
> | #define VERSION "2.13svn20160229"
> | #define HAVE_LIBICONV 1
> | #define HAVE_LIBINTL 1
> | #define HAVE_LIBIBERTY 1
> | #define HAVE_LIBBFD 1
> | #define HAVE_LIBUSB 1
> | /* end confdefs.h.  */
> |
> | /* Override any GCC internal prototype to avoid an error.
> |    Use char because int might match the return type of a GCC
> |    builtin and then its argument prototype would still apply. */
> | #ifdef __cplusplus
> | extern "C"
> | #endif
> | char hid_init ();
> | int
> | main ()
> | {
> | return hid_init ();
> |   ;
> |   return 0;


On 03.03.2016 15:13, Joerg Wunsch wrote:
> As Philip Mulrane wrote:
>
>> So my Avarice build was without libhidapi (no files from it are
> I'm not sure, it might be so.
>
> If not, try the example program I've told about.
>
>> installed)? Did my call of configure create a makefile that excludes
>> this functionality?
> Have a look at your config.log file, and/or src/autoconf.h.
>


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

Fax: +49 32223945096

HRB 209338 Amtsger. Hannover

Geschäftsführer
Pauline Atkinson

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

[Joerg W. <j...@ur...>]

As Philip Mulrane wrote:

> So my Avarice build was without libhidapi (no files from it are 

I'm not sure, it might be so.

If not, try the example program I've told about.

> installed)? Did my call of configure create a makefile that excludes 
> this functionality?

Have a look at your config.log file, and/or src/autoconf.h.

-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

OK,
So my Avarice build was without libhidapi (no files from it are 
installed)? Did my call of configure create a makefile that excludes 
this functionality? So I need to add libhidapi, and rebuild from scratch 
(including configure)?
Br,
Philip

On 03.03.2016 14:43, Joerg Wunsch wrote:
> 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 never answers if you try to talk to it.
>
> Been there, done that (in AVRDUDE).  Plain libusb doesn't work
> for HIDs on Windows or OSX.  Only FreeBSD and Linux can access
> it that way.
>
> Thus, for AVaRICE, I simplified the implementation (compared to
> AVRDUDE) by requiring libhidapi for the CMSIS-DAP/EDBG stuff.


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

Fax: +49 32223945096

HRB 209338 Amtsger. Hannover

Geschäftsführer
Pauline Atkinson

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

[Joerg W. <j...@ur...>]

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 never answers if you try to talk to it.

Been there, done that (in AVRDUDE).  Plain libusb doesn't work 
for HIDs on Windows or OSX.  Only FreeBSD and Linux can access 
it that way.

Thus, for AVaRICE, I simplified the implementation (compared to 
AVRDUDE) by requiring libhidapi for the CMSIS-DAP/EDBG stuff.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

OK,
I will try this later, one thing I did check, avarice builds without 
"hidapi.h" being on my system, but this is required for the demo program 
you pointed me to.
My build of avarice went like this:
> $ ./Bootstrap
> + aclocal
> + autoheader
> + autoconf
> + '[' -d config-aux ']'
> + mkdir config-aux
> + automake -a -c
> configure.ac:35: installing 'config-aux/compile'
> configure.ac:38: installing 'config-aux/config.guess'
> configure.ac:38: installing 'config-aux/config.sub'
> configure.ac:31: installing 'config-aux/install-sh'
> configure.ac:31: installing 'config-aux/missing'
> src/Makefile.am: installing 'config-aux/depcomp'
> + rm -f config.cache
> ./configure
> blah...blah....
> make
> blah...blah....
> exe file was ready
The hidlib compiles under windows using VC++, which I do not have, so it 
will take me a little bit longer to build this.
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"
Br,
Philip


On 03.03.2016 14:05, Joerg Wunsch wrote:
> As Philip Mulrane wrote:
>
>> 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.
> Well, AVaRICE has to be built using Cygwin on Windows, so
> maybe there's an issue with Cygwin and libhidapi then?
>
> If you go to the libhidapi home page:
>
> http://www.signal11.us/oss/hidapi/
>
> there's a short example program.  Drop the second part
> (starting at "handle = hid_open(..."), the initial part
> will tell you all HIDs the library could find.  Build that
> example under Cygwin, and run it.
>
> The Atmel-ICE (or XplainedMini) must appear there.


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

Fax: +49 32223945096

HRB 209338 Amtsger. Hannover

Geschäftsführer
Pauline Atkinson

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

[Joerg W. <j...@ur...>]

As Philip Mulrane wrote:

> 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.

Well, AVaRICE has to be built using Cygwin on Windows, so 
maybe there's an issue with Cygwin and libhidapi then?

If you go to the libhidapi home page:

http://www.signal11.us/oss/hidapi/

there's a short example program.  Drop the second part 
(starting at "handle = hid_open(..."), the initial part 
will tell you all HIDs the library could find.  Build that 
example under Cygwin, and run it.

The Atmel-ICE (or XplainedMini) must appear there.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

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

Thanks! I will give it a try at the weekend.
I have used the latest Avrdude (6.3) to read/write the Flash 
successfully, so programming via Avarice will not be essential.
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.

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

[Joerg W. <j...@ur...>]

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.
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

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

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

Hi,
Can this also be used with the mEDBG of the xlpained mini? It apparently 
supports debug wire?
Br,
Philip
On 03.03.2016 06:17, Robin Kauffman wrote:
> Hi-
> 	Works flawlessly so far!  Will keep you posted!  Thank you so
> much!
> (avarice r361 and avrdude r1387)
>
> 		-Robin K.
>
> On Mon, 2016-02-29 at 23:33 +0100, Joerg Wunsch wrote:
>> As Robin Kauffman wrote:
>>
>>> 	I was just wondering if there were any updates to support for
>>> the EDBG (weird, new, HID-based) protocol for newer Atmel debugging
>>> devices.
>> I just merged the branch back into the trunk.
>>
>> Give it a try.
>>
>> The respective option is -4 (--edbg).
>>
>>
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>>
>>
>> _______________________________________________
>> avarice-user mailing list
>> ava...@li...
>> https://lists.sourceforge.net/lists/listinfo/avarice-user


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

Fax: +49 32223945096

HRB 209338 Amtsger. Hannover

Geschäftsführer
Pauline Atkinson

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

[Robin K. <ro...@cr...>]

Hi-
	Works flawlessly so far!  Will keep you posted!  Thank you so
much!
(avarice r361 and avrdude r1387)

		-Robin K.

On Mon, 2016-02-29 at 23:33 +0100, Joerg Wunsch wrote:
> As Robin Kauffman wrote:
> 
> > 	I was just wondering if there were any updates to support for
> > the EDBG (weird, new, HID-based) protocol for newer Atmel debugging
> > devices.
> 
> I just merged the branch back into the trunk.
> 
> Give it a try.
> 
> The respective option is -4 (--edbg).

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

[Joerg W. <j...@ur...>]

As Robin Kauffman wrote:

> 	I was just wondering if there were any updates to support for
> the EDBG (weird, new, HID-based) protocol for newer Atmel debugging
> devices.

I just merged the branch back into the trunk.

Give it a try.

The respective option is -4 (--edbg).
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)

[AVaRICE-user] EDBG/ATATMEL-ICE support

[Robin K. <ro...@cr...>]

Hi all-
	I was just wondering if there were any updates to support for
the EDBG (weird, new, HID-based) protocol for newer Atmel debugging
devices.  I have an ATATMEL-ICE debugger/ICSP, as well as an
ATmega256RFR2 Xplained Pro kit (with a USB interface and a debugging IC
(not as sophisticated as the ICE) which speaks EDBG exclusively).  I
would *love* to be able to debug software from my Linux machine (which
also has a much newer and more capable toolchain, and would in general
make for a more productive development platform), but currently I have
to attach the board or debugger to a Windows machine running Atmel
studio to be able to fiddle about with software as it's running on an
AVR.
	I realize that EDBG is somewhat different from the previous
(saner, it sounds like) protocols, but my hope was that there was at
least something preliminary that had been done in terms of scaffolding
for (at some point) supporting the newer protocol.
	Thank you guys so much for your time and all of your hard work.

		-Robin K.

Re: [AVaRICE-user] EDBG support

[Joerg W. <j...@ur...>]

As Jessica Creighton wrote:

> Has there been any work recently to support EDBG?

Unfortunately, so far nobody bothered to start the project.

> It's rather annoying not
> being able to debug using my Atmel-ICE on Linux.

Agreed.

I wonder whether it might even make more sense to implement (or 
extend) the AVR backend part in OpenOCD, and in turn reuse their 
already existing CMSIS-DAP transport and tool handler.

(Please subscribe to the mailinglist for continuing the discussion.)
-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)