Hi gang,
normally I'm friendly and happy with tools I get for free. But this
time,... I use AS6 and ICE3 in Win 7-64 and I don't know what I have to
take to like it but I know I don't have THAT and I expect it is not
legal in Germany. So back to the headline: I would like to see avarice
to handle ICE3. To find out how AS6 is operating the ICE3 it is the best
to create a virtual machine with the windows version of your preference
and install AS6. If you connect your ICE3 for the first time I could not
update ICE3 with the VM and had to do it under native Windows! All of
the rest detail tests I did under Linux. It does not matter which
distribution you use, but you should have a look to Wireshark
<http://wiki.wireshark.org/CaptureSetup/USB> and check if your kernel is
fit for purpose.
The major trick with a VM and Linux is: For the Windows application
everything is transparent and no Windows hooks or so on are needed.
Next to check is what makes the difference to ICE2 and ICE3: ICE2 is a
serial device with a USB extension. It seems that ICE2 is the major part
of the Jtag-debugging and only command are display information are
exchanged between the Jtag-ICE2 and the PC .
ICE3 looks different on the USB-Bus. Here is the trace from my system:
Bus 002 Device 003: ID 03eb:2110 Atmel Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x03eb Atmel Corp.
idProduct 0x2110
bcdDevice 1.01
iManufacturer 1 ATMEL
iProduct 2 JTAGICE3
iSerial 3 J30xxxxxxxxx
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 255
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 255
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 255
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
As one can see the ICE3 has now 2 ports for communication inputs. While
analyzing the telegrams we will see what they are used for.
That's it for today. Next will follow when I have finished the current
project - if AS6 is not making me crazy before...
Cheers,
Knut
ps: Does anyone know why AS6 is always reprogramming the CPU or while
ICE3 is able to move a Mega32A to a status where only a power-off of the
CPU is able to proceed with debugging?
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
avarice-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/avarice-user
