Menu
▾
▴
avarice-user — AVaRICE Users
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(11) |
Dec
(11) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(5) |
Feb
(3) |
Mar
(3) |
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2003 |
Jan
|
Feb
(11) |
Mar
(29) |
Apr
(27) |
May
(21) |
Jun
(24) |
Jul
(18) |
Aug
(30) |
Sep
(8) |
Oct
(15) |
Nov
(33) |
Dec
(15) |
| 2004 |
Jan
(14) |
Feb
(29) |
Mar
(16) |
Apr
(2) |
May
(8) |
Jun
(3) |
Jul
(1) |
Aug
(29) |
Sep
(16) |
Oct
(8) |
Nov
(53) |
Dec
(47) |
| 2005 |
Jan
(70) |
Feb
(15) |
Mar
(5) |
Apr
(44) |
May
(17) |
Jun
(12) |
Jul
(8) |
Aug
(15) |
Sep
(11) |
Oct
(9) |
Nov
(6) |
Dec
(4) |
| 2006 |
Jan
(6) |
Feb
(20) |
Mar
(5) |
Apr
(35) |
May
|
Jun
(17) |
Jul
(5) |
Aug
(9) |
Sep
(9) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2007 |
Jan
|
Feb
(3) |
Mar
(9) |
Apr
(7) |
May
(9) |
Jun
(7) |
Jul
(15) |
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(5) |
| 2008 |
Jan
(58) |
Feb
(25) |
Mar
(18) |
Apr
(38) |
May
(24) |
Jun
(6) |
Jul
(3) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(2) |
Dec
(2) |
| 2009 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(6) |
May
|
Jun
(4) |
Jul
(5) |
Aug
(21) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2010 |
Jan
(4) |
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(3) |
| 2011 |
Jan
|
Feb
(1) |
Mar
(11) |
Apr
(5) |
May
(2) |
Jun
|
Jul
|
Aug
(12) |
Sep
(11) |
Oct
|
Nov
(1) |
Dec
(13) |
| 2012 |
Jan
(5) |
Feb
(6) |
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(2) |
Oct
(4) |
Nov
(33) |
Dec
(2) |
| 2013 |
Jan
(35) |
Feb
(3) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2014 |
Jan
(6) |
Feb
(10) |
Mar
(10) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(11) |
Nov
|
Dec
(9) |
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(12) |
Nov
(1) |
Dec
|
| 2016 |
Jan
|
Feb
(2) |
Mar
(31) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
(4) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(4) |
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(1) |
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Oliver V. <ov...@ve...> - 2014-01-20 09:50:37
|
Hi Knut, > please retest the problem and add the switch "-d" to avarice command > line. That will print additional debug information into the avarice > window. Please send this output to the list. it seems to go in an endless loop after issuing `(gdb) i io': GDB: <qRavr.io_reg> GDB: (io registers) Read 64 bytes from 0x20 ->GDB: 62 [...] <- loops forever tl;dr Here is the whole session: $ avarice -d -2 -j usb :4242 AVaRICE version 2.13, Jan 19 2014 13:32:42 Defaulting JTAG bitrate to 250 kHz. Found JTAG ICE, serno: 00B000005543 JTAG config starting. Attempting synchronisation at bitrate 19200 command[0x01, 1]: 01 recv: 0x1b recv: 0x00 recv: 0x00 recv: 0x1c recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 28 bytes read: 86 01 ff 24 07 00 ff 24 07 01 00 b0 00 00 55 43 4a 54 41 47 49 43 45 6d 6b 49 49 00 recv: 0xc6 recv: 0x12 CRC OK Got message seqno 0 (command_sequence == 0) response: 86 01 FF 24 07 00 FF 24 07 01 00 B0 00 00 55 43 4A 54 41 47 49 43 45 6D 6B 49 49 00 Found a device: JTAGICEmkII Serial number: xx:xx:xx:xx:xx:xx JTAG ICE mkII sign-on message: Communications protocol version: 1 M_MCU: boot-loader FW version: 255 firmware version: 7.36 hardware version: 0 S_MCU: boot-loader FW version: 255 firmware version: 7.36 hardware version: 1 command[0x02, 1]: 02 03 01 recv: 0x1b recv: 0x01 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xcd recv: 0x83 CRC OK Got message seqno 1 (command_sequence == 1) response: 80 command[0x0a, 1]: 0A 01 recv: 0x1b recv: 0x02 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x1d recv: 0x09 CRC OK Got message seqno 2 (command_sequence == 2) response: 80 recv: 0x1b recv: 0xff recv: 0xff recv: 0x06 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 6 bytes read: e0 a4 00 00 00 00 recv: 0x9a recv: 0xea CRC OKAutomatic device detection: command[0x03, 1]: 03 0E recv: 0x1b recv: 0x03 recv: 0x00 recv: 0x05 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 5 bytes read: 81 3f a0 40 09 recv: 0xc6 recv: 0xc0 CRC OK Got message seqno 3 (command_sequence == 3) response: 81 3F A0 40 09 JTAG id = 0x940A03F : Ver = 0x0 : Device = 0x940a : Manuf = 0x1f Reported JTAG device ID: 0x940A Configured for device ID: 0x940A atmega164p command[0x0c, 1]: 0C FF 0F E0 F8 FF 3D B9 E8 00 00 00 00 01 00 00 00 B6 0D 00 E0 FF 1D B8 E8 00 00 00 00 01 00 00 00 53 FB 09 DF F3 0F 00 00 00 00 5F 3F 37 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 FB 09 D8 F3 0F 00 00 00 00 5F 2F 36 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 31 57 3B 80 00 04 80 1F 00 00 C6 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3E 3D 80 00 00 00 00 00 00 01 00 00 01 00 00 00 00 1F 00 recv: 0x1b recv: 0x04 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xac recv: 0x14 CRC OK Got message seqno 4 (command_sequence == 4) response: 80 JTAG config complete. Preparing the target device for On Chip Debugging. command[0x02, 1]: 02 07 15 recv: 0x1b recv: 0x05 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x13 recv: 0x95 CRC OK Got message seqno 5 (command_sequence == 5) response: 80 command[0x14, 1]: 14 recv: 0x1b recv: 0x06 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xc3 recv: 0x1f CRC OK Got message seqno 6 (command_sequence == 6) response: 80 command[0x14, 1]: 14 recv: 0x1b recv: 0x07 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x7c recv: 0x9e CRC OK Got message seqno 7 (command_sequence == 7) response: 80 jtagRead command[0x05, 1]: 05 B2 03 00 00 00 00 00 00 00 recv: 0x1b recv: 0x08 recv: 0x00 recv: 0x04 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 4 bytes read: 82 62 19 ff recv: 0x10 recv: 0x0c CRC OK Got message seqno 8 (command_sequence == 8) response: 82 62 19 FF command[0x15, 1]: 15 recv: 0x1b recv: 0x09 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x71 recv: 0xae CRC OK Got message seqno 9 (command_sequence == 9) response: 80 command[0x15, 1]: 15 recv: 0x1b recv: 0xff recv: 0xff recv: 0x06 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 6 bytes read: e0 00 00 00 00 00 recv: 0x4e recv: 0x2d CRC OK Got message seqno 65535 (command_sequence == 10) got asynchronous event: 0xe0 recv: 0x1b recv: 0x0a recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xa1 recv: 0x24 CRC OK Got message seqno 10 (command_sequence == 10) response: 80 command[0x0b, 1]: 0B 01 recv: 0x1b recv: 0xff recv: 0xff recv: 0x06 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 6 bytes read: e0 04 00 00 00 00 recv: 0x5e recv: 0x00 CRC OK Got message seqno 65535 (command_sequence == 11) got asynchronous event: 0xe0 recv: 0x1b recv: 0x0b recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x1e recv: 0xa5 CRC OK Got message seqno 11 (command_sequence == 11) response: 80 recv: 0x1b recv: 0xff recv: 0xff recv: 0x06 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 6 bytes read: e0 00 00 00 00 00 recv: 0x4e recv: 0x2d CRC OK command[0x02, 1]: 02 09 00 recv: 0x1b recv: 0x0c recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x10 recv: 0x39 CRC OK Got message seqno 12 (command_sequence == 12) response: 80 Waiting for connection on port 4242. ********************************************************************** Then I log into another terminal: $ avr-gdb -command __avr_gdbinit main.elf Connection opened by host 127.0.0.1, port 43490. GDB: <qSupported:multiprocess+;qRelocInsn+> ->GDB: GDB: <Hg0> ->GDB: GDB: <?> ->GDB: S05 GDB: <Hc-1> ->GDB: GDB: <qC> ->GDB: GDB: <qAttached> ->GDB: GDB: <qOffsets> ->GDB: GDB: <g> GDB: (Registers)Read 32 bytes from 0x800000 jtagRead command[0x05, 1]: 05 20 20 00 00 00 00 00 00 00 recv: 0x1b recv: 0x0d recv: 0x00 recv: 0x21 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 33 bytes read: 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 f6 04 69 00 recv: 0xb3 recv: 0x18 CRC OK Got message seqno 13 (command_sequence == 13) response: 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00 F6 04 69 00 jtagRead command[0x05, 1]: 05 20 03 00 00 00 5D 00 00 00 recv: 0x1b recv: 0x0e recv: 0x00 recv: 0x04 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 4 bytes read: 82 ff 04 00 recv: 0xf0 recv: 0xa5 CRC OK Got message seqno 14 (command_sequence == 14) response: 82 FF 04 00 PC = 0 ->GDB: 00000000000000000000000000000000000000000000000014000000f604690000ff0400000000 GDB: <qSymbol::> ->GDB: GDB: <qTStatus> ->GDB: GDB: <m142,2> GDB: Read 2 bytes from 0x142 jtagRead command[0x05, 1]: 05 A0 02 00 00 00 42 01 00 00 recv: 0x1b recv: 0x0f recv: 0x00 recv: 0x03 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 3 bytes read: 82 0e 94 recv: 0xd0 recv: 0xbb CRC OK Got message seqno 15 (command_sequence == 15) response: 82 0E 94 ->GDB: 0e94 GDB: <qTStatus> ->GDB: ********************************************************************** (gdb) c GDB: <qTStatus> ->GDB: GDB: <Z0,142,2> BP ADD type: 1 addr: 0x142 Slot 0 full ->GDB: OK GDB: <vCont?> ->GDB: GDB: <Hc0> ->GDB: GDB: <c> Slot 0 full Breakpoint added in ICE. slot: 1 type: 1 addr: 0x142 command[0x11, 1]: 11 01 01 A1 00 00 00 03 recv: 0x1b recv: 0x10 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x0a recv: 0x59 CRC OK Got message seqno 16 (command_sequence == 16) response: 80 command[0x08, 1]: 08 recv: 0x1b recv: 0x11 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xb5 recv: 0xd8 CRC OK Got message seqno 17 (command_sequence == 17) response: 80 Waiting for input. recv: 0x1b recv: 0xff recv: 0xff recv: 0x06 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 6 bytes read: e0 a1 00 00 00 01 recv: 0x47 recv: 0xdd CRC OKjtagRead command[0x05, 1]: 05 20 03 00 00 00 5D 00 00 00 recv: 0x1b recv: 0x12 recv: 0x00 recv: 0x04 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 4 bytes read: 82 fd 04 00 recv: 0xf2 recv: 0x83 CRC OK Got message seqno 18 (command_sequence == 18) response: 82 FD 04 00 ->GDB: T0520:00;21:fd04;22:42010000; GDB: <z0,142,2> BP DEL type: 1 addr: 0x142 DISABLED ->GDB: OK ********************************************************************** (gdb) i io GDB: <qRavr.io_reg> GDB: (io registers) Read 64 bytes from 0x20 ->GDB: 62 GDB: <qRavr.io_reg> GDB: (io registers) Read 64 bytes from 0x20 ->GDB: 62 GDB: <qRavr.io_reg> GDB: (io registers) Read 64 bytes from 0x20 ->GDB: 62 GDB: <qRavr.io_reg> GDB: (io registers) Read 64 bytes from 0x20 ->GDB: 62 GDB: <qRavr.io_reg> GDB: (io registers) Read 64 bytes from 0x20 ->GDB: 62 [...] <- loops forever ********************************************************************** ^CQuit (gdb) q GDB: <qTStatus> ->GDB: GDB: <k> gdb exited. command[0x08, 1]: 08 recv: 0x1b recv: 0x13 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xda recv: 0xd3 CRC OK Got message seqno 19 (command_sequence == 19) response: 80 command[0x23, 1]: 23 recv: 0x1b recv: 0x14 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xd4 recv: 0x4f CRC OK Got message seqno 20 (command_sequence == 20) response: 80 command[0x00, 1]: 00 recv: 0x1b recv: 0x15 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x6b recv: 0xce CRC OK Got message seqno 21 (command_sequence == 21) response: 80 -- Cheers, Oliver |
|
From: Knut S. <ks...@we...> - 2014-01-20 07:46:07
|
Hi Oliver, please retest the problem and add the switch "-d" to avarice command line. That will print additional debug information into the avarice window. Please send this output to the list. Cheers, Knut |
|
From: Oliver V. <ov...@ve...> - 2014-01-19 19:12:05
|
Hi, I'm trying to setup a JTAGICE mkII with an ATmega164p on Ubuntu. I compiled avarice and avr-gdb from source to test the latest versions. Debugging basically works fine (single stepping, breakpoints, ...), but `info io_registers' hangs: $ avarice -2 -j usb -P atmega164p :4242 AVaRICE version 2.13, Jan 19 2014 13:32:42 Defaulting JTAG bitrate to 250 kHz. JTAG config starting. Found a device: JTAGICEmkII Serial number: xx:xx:xx:xx:xx:xx Reported JTAG device ID: 0x940A Configured for device ID: 0x940A atmega164p -- Matched with atmega164p JTAG config complete. Preparing the target device for On Chip Debugging. Waiting for connection on port 4242. On another terminal I start avr-gdb: $ avr-gdb -command __avr_gdbinit main.elf GNU gdb (GDB) 7.6.2 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=avr". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/ov/w/laminator/src/main.elf...done. 0x00000000 in __vectors () Breakpoint 1 at 0x1a4: file main.c, line 60. (gdb) c Continuing. Breakpoint 1, main () at main.c:60 60 setup(); /* Setup ports and Interrupt */ (gdb) i reg r0 0x0 0 r1 0x0 0 r2 0x0 0 r3 0x0 0 r4 0x0 0 r5 0x0 0 r6 0x0 0 r7 0x0 0 r8 0x0 0 r9 0x0 0 r10 0x0 0 r11 0x0 0 r12 0x0 0 r13 0x0 0 r14 0x0 0 r15 0x0 0 r16 0x0 0 r17 0x0 0 r18 0x0 0 r19 0x0 0 r20 0x0 0 r21 0x0 0 r22 0x0 0 r23 0x0 0 r24 0x14 20 r25 0x0 0 r26 0x0 0 r27 0x0 0 r28 0xff 255 r29 0x4 4 r30 0x69 105 r31 0x0 0 SREG 0x0 0 SP 0x8004fd 0x8004fd PC2 0x1a4 420 pc 0x1a4 0x1a4 <main> (gdb) info io_registers ^CQuit (gdb) The only thing I can do is to press <C-c>. Debugging is further possible afterwards. $ avrdude -p m164p -c jtag2 -P usb -v [...] JTAG ICE mkII sign-on message: Communications protocol version: 1 M_MCU: boot-loader FW version: 255 firmware version: 7.36 hardware version: 0 S_MCU: boot-loader FW version: 255 firmware version: 7.36 hardware version: 1 [...] Am I doing something wrong? -- Regards, Oliver |
|
From: Joerg W. <j...@ur...> - 2013-10-24 21:19:39
|
As Seth Traend wrote: > > $ avarice --erase --program -f X16A4HelloWorld.elf --part atmega16 -2 > > -g -x :4242 As Knut already mentioned: --erase and --program are deprecated. You did download your firmware by AVRDUDE before anyway, so they aren't necessary at all. > set paramater command failed In order to see *which* "set parameter" command actually failed, please add option -d. Hmm, I just saw your AVRDUDE call uses dragon_pdi. In order to make AVaRICE talk PDI, use -X rather than -x. The latter is to talk to Xmega devices through JTAG. -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) |
|
From: Knut S. <ks...@we...> - 2013-10-24 19:36:29
|
Hi Seth, is there any reason why avrdude and avarice should share an identical syntax on the command line? Now anyway did you checked that your XM16A4 has a JTAG port or does it only have a PDI port instead? Here is the command line for debugging a XM32E4 with PDI using ICE-3: avarice -I --jtag usb -3 -X :4242 Here comes the command line for an M32 using JTAG via ICE-3 avarice -I --jtag usb -3 -B1800khz :4242 "-I" skips interrupts which make debugging easier while a timer is running This syntax is valid for the current version of avarice as available from the repository on a linux system. My avarice show a 2.13 version. avr-gdb is initiated with the command file "__avr_gdbinit" as created by the Makefile. My Makefile is generated by mfile. cat __avr_gdbinit define reset SIGNAL SIGHUP end file debug_object.elf target remote localhost:4242 break main The parameter "--erase --program -f*.elf" are obsolete and not used any more, because avr-gdb can do. Best regards, Knut On 24.10.2013 14:32, Seth Traend wrote: >> $ avarice --erase --program -f X16A4HelloWorld.elf --part atmega16 -2 >> -g -x :4242 > but it fails with: > > AVaRICE version 2.11, Jan 12 2013 23:58:31 > > Defaulting JTAG bitrate to 250 kHz. > > JTAG config starting. > Found a device: AVRDRAGON > |
|
From: Seth T. <set...@co...> - 2013-10-24 12:51:34
|
Hello, Just got the Code Blocks IDE with avr-gdb and avarice compiled on linux. I program the firmware with avrdude and avr-dragon with pdi mode like this and succeed: > $ avrdude -c dragon_pdi -p x16a4 -v -P usb -U > flash:w:X16A4HelloWorld.hex:i the firmware runs on target. But I would like to use the debugging feature so. I tried it from the bottom up on the commandline by starting avarice like this: > $ avarice --erase --program -f X16A4HelloWorld.elf --part atmega16 -2 > -g -x :4242 but it fails with: AVaRICE version 2.11, Jan 12 2013 23:58:31 Defaulting JTAG bitrate to 250 kHz. JTAG config starting. Found a device: AVRDRAGON Serial number: 00:a2:00:00:0f:bc set paramater command failed I could not find any tutorials or anything which points me in the right direction, so please help all the best Seth |
|
From: Joerg W. <j...@ur...> - 2013-07-13 20:16:59
|
As István Rétallér wrote: > avarice -d -2 -r -P at90usb162 -j usb The AT90USB162 does not have JTAG. You have to use debugWIRE for it -- which involves fuse toggling, and if your configuration cannot talk debugWIRE at all (e.g. since you've got too much capacitive load at /RESET), this fuse becomes one-way street. (In order to turn that fuse off, you have to talk debugWIRE first, to re-assign the /RESET pin as reset again, so you can talk ISP.) That's the reason why AVaRICE does not touch this fuse by itself, so you have to program it manually in AVRDUDE. -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) |
|
From: István R. <ist...@gm...> - 2013-07-13 19:14:07
|
Hi all, I can read/write my chip via avrdude, but the same configuration cannot be handled by avarice. /usr/bin/avrdude -F -c jtag2isp -P usb -B 10 -b 115200 -p usb162 -U flash:r:/dev/tty:i avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.15s avrdude: Device signature = 0x1e9482 avrdude: reading flash memory: Reading | ################################################## | 100% 10.71s avrdude: writing output file "/dev/tty" :200000000C94A6000C94B8000C94B8000C94B8000C94B8000C94B8000C94B8000C94B80032 :200020000C94B8000C94B8000C94B8000C94D1030C9408040C94B8000C94B8000C94B80090 ... :200F600040EA56E861E070E049835A836B837C835A9A0BC089819A81AB81BC810197A10953 :200F8000B10989839A83AB83BC8389819A81AB81BC81892B8A2B8B2B39F3ECCFF894FFCF13 :200FA0000000000000010001000100010064640000000000000000E803E803E803E8038D2C :0A0FC000058D058D058D050000006C :00000001FF avrdude: safemode: Fuses OK avrdude done. Thank you. ------------------------------------------------------------------------------------------------------------------------------------------------- Then - without changing anything - I try avarice: ------------------------------------------------------------------------------------------------------------------------------------------------- avarice -d -2 -r -P at90usb162 -j usb AVaRICE version 2.11, Jan 12 2013 23:42:03 Defaulting JTAG bitrate to 250 kHz. Found JTAG ICE, serno: 00B0000024CF JTAG config starting. Attempting synchronisation at bitrate 19200 command[0x01, 1]: 01 recv: 0x1b recv: 0x00 recv: 0x00 recv: 0x1c recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 28 bytes read: 86 01 ff 06 06 00 ff 06 06 01 00 b0 00 00 24 cf 4a 54 41 47 49 43 45 6d 6b 49 49 00 recv: 0xef recv: 0x11 CRC OK Got message seqno 0 (command_sequence == 0) response: 86 01 FF 06 06 00 FF 06 06 01 00 B0 00 00 24 CF 4A 54 41 47 49 43 45 6D 6B 49 49 00 Found a device: JTAGICEmkII Serial number: 00:b0:00:00:24:cf JTAG ICE mkII sign-on message: Communications protocol version: 1 M_MCU: boot-loader FW version: 255 firmware version: 6.06 hardware version: 0 S_MCU: boot-loader FW version: 255 firmware version: 6.06 hardware version: 1 command[0x02, 1]: 02 03 01 recv: 0x1b recv: 0x01 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xcd recv: 0x83 CRC OK Got message seqno 1 (command_sequence == 1) response: 80 command[0x0a, 1]: 0A 01 recv: 0x1b recv: 0x02 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0x1d recv: 0x09 CRC OK Got message seqno 2 (command_sequence == 2) response: 80 Automatic device detection: command[0x03, 1]: 03 0E recv: 0x1b recv: 0xff recv: 0xff recv: 0x06 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 6 bytes read: e0 00 00 00 00 00 recv: 0x4e recv: 0x2d CRC OK Got message seqno 65535 (command_sequence == 3) got asynchronous event: 0xe0 recv: 0x1b recv: 0x03 recv: 0x00 recv: 0x05 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 5 bytes read: 81 ff ff ff ff recv: 0x24 recv: 0x19 CRC OK Got message seqno 3 (command_sequence == 3) response: 81 FF FF FF FF JTAG id = 0xFFFFFFFF : Ver = 0xf : Device = 0xffff : Manuf = 0x7ff Reported JTAG device ID: 0xFFFF Looking for device: at90usb162 Configured for device ID: 0x9482 at90usb162 -- FORCED with at90usb162 command[0x0c, 1]: 0C F8 0F 60 F8 FF 3F B9 F0 00 00 00 00 00 00 00 00 B0 0D 00 E0 FF 1F B8 F0 00 00 00 00 00 00 00 00 7F DF 00 00 F7 3F 00 00 00 00 00 00 00 3F 07 01 7F FF 15 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 34 DF 00 C8 F7 3F 40 00 00 00 00 00 00 7F 03 01 0F 7F 11 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3B 80 00 04 00 1F 00 00 FB 00 00 40 00 00 BD F2 BD E1 BB CF B4 00 BE 01 B6 01 BC 00 BB BF 99 F9 BB AF B6 01 11 3E 3D 80 00 31 00 00 00 1F 01 00 00 01 00 00 00 3C 1F 00 recv: 0x1b recv: 0x04 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: 80 recv: 0xac recv: 0x14 CRC OK Got message seqno 4 (command_sequence == 4) response: 80 JTAG config complete. command[0x14, 1]: 14 recv: 0x1b recv: 0x05 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0xd0 recv: 0x29 CRC OK Got message seqno 5 (command_sequence == 5) response: A9 command[0x14, 2]: 14 recv: 0x1b recv: 0x06 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0x00 recv: 0xa3 CRC OK Got message seqno 6 (command_sequence == 6) response: A9 command[0x14, 3]: 14 recv: 0x1b recv: 0x07 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0xbf recv: 0x22 CRC OK Got message seqno 7 (command_sequence == 7) response: A9 command[0x14, 4]: 14 recv: 0x1b recv: 0x08 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0x0d recv: 0x93 CRC OK Got message seqno 8 (command_sequence == 8) response: A9 command[0x14, 5]: 14 recv: 0x1b recv: 0x09 recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0xb2 recv: 0x12 CRC OK Got message seqno 9 (command_sequence == 9) response: A9 command[0x14, 6]: 14 recv: 0x1b recv: 0x0a recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0x62 recv: 0x98 CRC OK Got message seqno 10 (command_sequence == 10) response: A9 command[0x14, 7]: 14 recv: 0x1b recv: 0x0b recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0xdd recv: 0x19 CRC OK Got message seqno 11 (command_sequence == 11) response: A9 command[0x14, 8]: 14 recv: 0x1b recv: 0x0c recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0xd3 recv: 0x85 CRC OK Got message seqno 12 (command_sequence == 12) response: A9 command[0x14, 9]: 14 recv: 0x1b recv: 0x0d recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0x6c recv: 0x04 CRC OK Got message seqno 13 (command_sequence == 13) response: A9 command[0x14, 10]: 14 recv: 0x1b recv: 0x0e recv: 0x00 recv: 0x01 recv: 0x00 recv: 0x00 recv: 0x00 recv: 0x0e sDATA: reading 1 bytes read: a9 recv: 0xbc recv: 0x8e CRC OK Got message seqno 14 (command_sequence == 14) response: A9 JTAG ICE: Cannot synchronise Adjacent info: If I want to use avrdude reading again, I have to disconnect/reconnect my MKII. Any idea? Steve |
|
From: Joerg W. <j...@ur...> - 2013-03-11 07:47:51
|
As Wojtek wrote:
> I have no problem with programming chip via avrdude like:
> avrdude -p atxmega32a4 -c avrispmkII -P usb -D -U flash:w:main.hex
^^^^^^^^^^
> but can't conect to my jtag via avarice. Command:
> avarice --jtag usb --mkII :4242
^^^^^^
> gives output:
> AVaRICE version 2.10
> Defaulting JTAG bitrate to 250kHz
> did not find any USB device "usb"
> USB device not fount
>
> Could you suggest me where to search a problem?
Sorry for not spotting it right at the beginning: an AVRISPmkII is
something *completely* different than a JTAGICEmkII. You cannot debug
with the AVRISPmkII, it's only suitable for ISP (or PDI) programming.
--
cheers, Joerg .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)
|
|
From: Knut S. <ks...@we...> - 2013-03-10 18:07:23
|
I would suggest to run avarice as root for the first test. If you have a
problem with access rights it might be easy on the first glance to use
the user root either via su or sudo.
At Suse you find in /etc/udev/rules.d several files. While I had USBPROG
installed I extended this file for MKII and ICE3
__________________________
BUS!="usb", ACTION!="add", SUBSYSTEM!=="usb_device",
GOTO="usbprog_rules_end"
# USBprog with Atmel AVR ISP mkII firmware
ATTR{idVendor}=="03eb", ATTR{idProduct}=="2104", MODE="664", GROUP="dialout"
# USBprog with Atmel AVR ISP mkII firmware
ATTR{idVendor}=="03eb", ATTR{idProduct}=="2110", MODE="664", GROUP="dialout"
LABEL="usbprog_rules_end"
_____________________________________
After changing this file and a reread of the configuration (see man)
your user needs to be a member of the group "dialout". If you change the
account a new login is necessary and next your account is allowed to
access Jtag ICE without root permission.
HTH
Knut
Am 10.03.2013 15:11, schrieb Joerg Wunsch:
> 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 through RS-232.
>
>> did not find any USB device "usb"
>> USB device not fount
>>
>> Could you suggest me where to search a problem?
> Does /sbin/lsusb find the device?
>
> Did you tell your udev configuration to pass ownership of the device
> to you, so it can be accessed without root-only permissions?
>
|
|
From: Joerg W. <j...@ur...> - 2013-03-10 14:29:02
|
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 through RS-232. > did not find any USB device "usb" > USB device not fount > > Could you suggest me where to search a problem? Does /sbin/lsusb find the device? Did you tell your udev configuration to pass ownership of the device to you, so it can be accessed without root-only permissions? -- cheers, Joerg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-) |
|
From: Wojtek <br...@gm...> - 2013-03-10 12:05:06
|
I tried to add symlink for my device according to post: http://sourceforge.net/mailarchive/forum.php?thread_name=20111215140952.GD2063%40uriah.heep.sax.de&forum_name=avarice-user and try to: / avarice -2 -j /dev/avrjtag/ But the output is: / VaRICE version 2.10, Feb 8 2010 07:22:54 Defaulting JTAG bitrate to 250 kHz. JTAG ICE communication failed: Inappropriate ioctl for device/ On man page http://linux.die.net/man/1/avarice there is example with specify serial number of usb device. I've found out that my device iSerial is 000200012345. So I try with / avarice --jtag usb:2345 --mkII / but still have output like: / AVaRICE version 2.10, Feb 8 2010 07:22:54 Defaulting JTAG bitrate to 250 kHz. did not find any (matching) USB device "usb:2345" USB device not found / Regards Woj -------- Original Message -------- Subject: Ubuntu no usb device Date: Sun, 10 Mar 2013 11:28:16 +0100 From: Wojtek <br...@gm...> To: ava...@li... Hi I'm on ubuntu 12_04_x64 and work with mkII clone and atxmega32a4. I have no problem with programming chip via avrdude like: avrdude -p atxmega32a4 -c avrispmkII -P usb -D -U flash:w:main.hex but can't conect to my jtag via avarice. Command: avarice --jtag usb --mkII :4242 gives output: AVaRICE version 2.10 Defaulting JTAG bitrate to 250kHz did not find any USB device "usb" USB device not fount Could you suggest me where to search a problem? Regards Woj \\ |
|
From: Wojtek <br...@gm...> - 2013-03-10 10:28:25
|
Hi
I'm on ubuntu 12_04_x64 and work with mkII clone and atxmega32a4.
I have no problem with programming chip via avrdude like:
avrdude -p atxmega32a4 -c avrispmkII -P usb -D -U flash:w:main.hex
but can't conect to my jtag via avarice. Command:
avarice --jtag usb --mkII :4242
gives output:
AVaRICE version 2.10
Defaulting JTAG bitrate to 250kHz
did not find any USB device "usb"
USB device not fount
Could you suggest me where to search a problem?
Regards
Woj
\\
|
|
From: Pink B. <da...@ya...> - 2013-02-04 23:10:32
|
I didn't get it, try again. ________________________________ From: "Weddington, Eric" <Eri...@at...> To: Jakub Ladman <la...@vo...>; "ava...@li..." <ava...@li...> Sent: Sunday, February 3, 2013 11:42 AM Subject: Re: [AVaRICE-user] test - please ignore Duly ignored. > -----Original Message----- > From: Jakub Ladman [mailto:la...@vo...] > Sent: Sunday, February 03, 2013 12:16 PM > To: ava...@li... > Subject: [AVaRICE-user] test - please ignore > > please ignore > > ----------------------------------------------------------------------- > ------- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_jan > _______________________________________________ > avarice-user mailing list > ava...@li... > https://lists.sourceforge.net/lists/listinfo/avarice-user ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ avarice-user mailing list ava...@li... https://lists.sourceforge.net/lists/listinfo/avarice-user |
|
From: Weddington, E. <Eri...@at...> - 2013-02-03 19:42:50
|
Duly ignored. > -----Original Message----- > From: Jakub Ladman [mailto:la...@vo...] > Sent: Sunday, February 03, 2013 12:16 PM > To: ava...@li... > Subject: [AVaRICE-user] test - please ignore > > please ignore > > ----------------------------------------------------------------------- > ------- > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_jan > _______________________________________________ > avarice-user mailing list > ava...@li... > https://lists.sourceforge.net/lists/listinfo/avarice-user |
|
From: Jakub L. <la...@vo...> - 2013-02-03 19:38:48
|
please ignore |
|
From: Joerg W. <j...@ur...> - 2013-01-15 22:33:47
|
As Omar Choudary wrote: > I should have updated avarice before starting the discussion, sorry > about that. No problem, glad it works now! I've got plans to also implement watchpoints (data breakpoints) for the Xmega. They are currently still missing. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) |
|
From: Omar C. <cho...@gm...> - 2013-01-15 22:28:36
|
Thanks for the details Joerg. After the update it works fine. I should have updated avarice before starting the discussion, sorry about that. Cheers, Omar On Tue, Jan 15, 2013 at 9:11 PM, Joerg Wunsch <j...@ur...> wrote: > As Omar Choudary wrote: > > > and after a bit of looking through the manpage I've added the "--xmega" > > flag but got a similar error. > > This is the output: > > AVaRICE version 2.10, Feb 8 2010 07:22:54 > ... > > Reported JTAG device ID: 0x9842 > > No configuration available for device ID: 9842 > > OK, that looks much better than your first attempt. > > Well, AVaRICE is meanwhile at version 2.13 :), yours is 2.10. > > If you look into the current src/devdescr.cc, you'll notice that an > entry with device ID 0x9842 does exist now. So I'd really recommend > an upgrade. > > > c) In the avarice manpage says that the atxmega128a1 is only supported > > through the JTAG ICE mkII device. Will this device work for the xmegas? > > I'm not sure if you could force an ATxmega128A1 in place of your 256 > KiB device. It might work to some degree, but I'd really ask you to > upgrade instead. There are many bugfixes now, too. > > There's one other thing to keep in mind: for all AVR Dragon (and > JTAGICEmkII) firmware versions *prior* to 7.x, AVaRICE has no chance > to set breakpoints for Xmega devices. The Xmega breakpoint handling > in these earlier firmware revisions was completely undocumented, and > has never been reverse-engineered. Starting with firmware 7.x, the > Xmega breakpoint handling is still undocumented but could reasonably > be reverse-engineered, so AVaRICE can handle them now. However, this > *requires* AVaRICE with at least version 2.12, and you have to find a > Windows machine with Atmel Studio 6 installed in order to have them > upgrade your Dragon's firmware. > > -- > cheers, J"org .-.-. --... ...-- -.. . DL8DTL > > http://www.sax.de/~joerg/ NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > |
|
From: Joerg W. <j...@ur...> - 2013-01-15 21:12:05
|
As Omar Choudary wrote: > and after a bit of looking through the manpage I've added the "--xmega" > flag but got a similar error. > This is the output: > AVaRICE version 2.10, Feb 8 2010 07:22:54 ... > Reported JTAG device ID: 0x9842 > No configuration available for device ID: 9842 OK, that looks much better than your first attempt. Well, AVaRICE is meanwhile at version 2.13 :), yours is 2.10. If you look into the current src/devdescr.cc, you'll notice that an entry with device ID 0x9842 does exist now. So I'd really recommend an upgrade. > c) In the avarice manpage says that the atxmega128a1 is only supported > through the JTAG ICE mkII device. Will this device work for the xmegas? I'm not sure if you could force an ATxmega128A1 in place of your 256 KiB device. It might work to some degree, but I'd really ask you to upgrade instead. There are many bugfixes now, too. There's one other thing to keep in mind: for all AVR Dragon (and JTAGICEmkII) firmware versions *prior* to 7.x, AVaRICE has no chance to set breakpoints for Xmega devices. The Xmega breakpoint handling in these earlier firmware revisions was completely undocumented, and has never been reverse-engineered. Starting with firmware 7.x, the Xmega breakpoint handling is still undocumented but could reasonably be reverse-engineered, so AVaRICE can handle them now. However, this *requires* AVaRICE with at least version 2.12, and you have to find a Windows machine with Atmel Studio 6 installed in order to have them upgrade your Dragon's firmware. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) |
|
From: Omar C. <cho...@gm...> - 2013-01-15 20:27:00
|
Hello, I am in a situation where it would be extremely helpful to be able to use my dragon to debug an xmega256A3U. Unfortunately, after running my avarice script (which used to work for the AT90USB1287), I got the following error: No configuration available for device ID: 4c0 Then I found this post: http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=108389 where Jörg said (2 years ago) that there was no code in avarice to handle this device. Then I found also this more recent post: http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&p=871867 and after a bit of looking through the manpage I've added the "--xmega" flag but got a similar error. This is the output: AVaRICE version 2.10, Feb 8 2010 07:22:54 Defaulting JTAG bitrate to 250 kHz. JTAG config starting. Found a device: AVRDRAGON Serial number: 00:a2:00:01:16:94 Reported JTAG device ID: 0x9842 No configuration available for device ID: 9842 I would like to know: a) Are there any updates in this direction so that I can use the dragon with the xmega? b) What can I use to debug the xmega? I use ubuntu with avr-gcc tools, not Windows/AS. c) In the avarice manpage says that the atxmega128a1 is only supported through the JTAG ICE mkII device. Will this device work for the xmegas? Any comments are welcome. Thanks. Omar |
|
From: Joerg W. <j...@ur...> - 2013-01-11 14:40:16
|
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 pointer aliasing problem. The device parameter field was
filled in like:
uchar *param, paramsize;
...
{
jtag3_device_desc_type d3;
param = (uchar *)&d3;
paramsize = sizeof d3;
memset((void *)&d3, 0, sizeof d3);
// fill in params here:
d3.flash_size ...
d3.flash_page_size
...
}
setJtagParameter(SCOPE_AVR, 2, PARM3_DEVICEDESC, param, paramsize);
GCC 4.7 decided that every assignment to d3 after the initial
memset() would result in values that are not used, as d3 was out
of scope at that point. Thus, a null parameter block has been
sent.
Moving the definition of d3 to the next outer scope helped.
OK, I'd like to hear about any other issues people have with it ...
In case it dies after some debugging actions, it would be interesting
to see the -d trace of the actions taken.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
|
|
From: Joerg W. <j...@ur...> - 2013-01-10 21:55:54
|
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 confusing, and I have to think about it again (there's a usage of "resp" versus "response" inside these functions). > [jtag2usb.cc:422]: (error) Mismatching allocation and deallocation: > devnamecopy Created as an array, but deleted as a non-array. Fixed. > [jtag2usb.cc:302]: (error) Memory leak: devnamecopy Yes, in cas of an error; fixed. > [jtag3io.cc:495]: (error) Array 'cmd[4]' accessed at index 4, which is out > of bounds As you've guessed, 0, 1, 2, 3 is the correct sequence. Besides accessing the array out of bounds, the bug lead to the request for applying an external reset (throgh nSRST) not being obeyed at all. Fixed. I'm afraid the next step would be to strace both invocations, and see what is done differently in the version as compiled by GCC 4.7. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) |
|
From: Andreas L. <al...@gm...> - 2013-01-10 21:25:30
|
I did a check with cppcheck and found one out of bounds array access in the jtag3 code: jtag3io.cc:495 The full output is: [jtag2rw.cc:180]: (error) Memory leak: response [jtag2usb.cc:422]: (error) Mismatching allocation and deallocation: devnamecopy [jtag2usb.cc:302]: (error) Memory leak: devnamecopy [jtag3io.cc:495]: (error) Array 'cmd[4]' accessed at index 4, which is out of bounds [jtag3rw.cc:182]: (error) Memory leak: response I don't know if these are false positives or not though, and changing the array indexed to 0,1,2,3 still doesn't fix the 1284P problems. On Thu, Jan 10, 2013 at 9:15 PM, Andreas Løhre <al...@gm...> wrote: > > > > On Thu, Jan 10, 2013 at 8:50 PM, Joerg Wunsch <j...@ur...> wrote: > >> As Andreas Løhre wrote: >> >> > I was still not able to start a session >> > on the 1284P. I will try some more on the different computers I have and >> > send the logs tonight. >> >> Someone reported on avrfreaks.net that he had similar problems on >> Ubuntu 12.x, but the problems disappeared when he used an older >> compiler to compile AVaRICE. So this might be a hidden problem in the >> AVaRICE code which we should better find ... >> >> > That's interesting; I will do some more testing with different compiler; > The one I have been testing with is 4.7.2, but I have 4.4.5 that I can test > on another computer when time allows. > > I have attached the log of the failing 1284P, on ubuntu 12.10 with gcc > 4.7.2 > > > >> -- >> cheers, J"org .-.-. --... ...-- -.. . DL8DTL >> >> http://www.sax.de/~joerg/ NIC: JW11-RIPE >> Never trust an operating system you don't have sources for. ;-) >> >> >> ------------------------------------------------------------------------------ >> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, >> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current >> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft >> MVPs and experts. ON SALE this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122712 >> _______________________________________________ >> avarice-user mailing list >> ava...@li... >> https://lists.sourceforge.net/lists/listinfo/avarice-user >> > > > > -- > Mvh. Andreas Løhre > > -- Mvh. Andreas Løhre |
|
From: Joerg W. <j...@ur...> - 2013-01-10 20:46:03
|
As jo...@ma... wrote:
> command "leave progmode" [0x12, 0x16]
> 0E 00 0B 00 12 16 00
> read() timed out
So it's the same timeouts Andreas Løhre is also seeing.
I wonder whether there's a missing "volatile" or such.
> g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread
> -MT jtag2usb.o -MD -MP -MF .deps/jtag2usb.Tpo -c -o jtag2usb.o jtag2usb.cc
> jtag2usb.cc: In function »void* usb_thread_event(void*)«:
> jtag2usb.cc:973:52: warning: ignoring return value of »ssize_t write(int,
> const void*, size_t)«, declared with attribute warn_unused_result
> [-Wunused-result]
> jtag2usb.cc: In function »void* usb_thread_read(void*)«:
> jtag2usb.cc:921:52: warning: ignoring return value of »ssize_t write(int,
> const void*, size_t)«, declared with attribute warn_unused_result
> [-Wunused-result]
These are basically expected, yes. In both receiver threads, the
message written to the upstream pipe gets the message length
prepended, and the write() calls for the message length are not
checked.
As I intend to combine these write calls with the subsequent packet
write itself (so the entire write() operation to the pipe is atomic),
I don't want to touch this now. I don't think this is related to the
problems you are seeing.
> g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread
> -MT jtagrw.o -MD -MP -MF .deps/jtagrw.Tpo -c -o jtagrw.o jtagrw.cc
> jtagrw.cc: In member function »virtual uchar* jtag1::jtagRead(long
> unsigned int, unsigned int)«:
> jtagrw.cc:134:13: warning: converting »false« to pointer type »uchar* {aka
> unsigned char*}« [-Wconversion-null]
OK, there's a point in this warning. Instead of returning false, the
function should better throw an exception. However, it's for the
original JTAGICE ("mkI") only, so unrelated here.
I've fixed this in the source, anyway.
Too bad the warnings don't give us a hint about what might be the problem.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
|
|
From: <jo...@ma...> - 2013-01-10 20:33:12
|
This is a continuation of this thread at avrfreaks: http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&p=1026487#1026487 where Jörg wrote: > and also send a debugging trace with the -d option there. Ok. Here it come: --- $ avarice -P atmega1284p -d -3 -j usb :4242 AVaRICE version 2.13svn20130104, Jan 10 2013 20:47:35 Defaulting JTAG bitrate to 250 kHz. Found JTAG ICE, serno: J30200013923 JTAG config starting. command "sign-on" [0x01, 0x10] 0E 00 00 00 01 10 00 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 read: 0e 01 00 00 81 00 4a 33 30 32 30 30 30 31 33 39 32 33 Got message seqno 1 (command_sequence == 1) response: 00 81 00 4A 33 30 32 30 30 30 31 33 39 32 33 Found a device, serial number: J30200013923 command "get parameter" [0x01, 0x02] 0E 00 02 00 01 02 00 00 00 05 read: 0e 02 00 01 84 01 02 02 0c c9 00 00 Got message seqno 2 (command_sequence == 2) response: 01 84 01 02 02 0C C9 00 00 ICE hardware version: 2 ICE firmware version: 2.12 (rel. 201) command "set parameter" [0x12, 0x01] 0E 00 03 00 12 01 00 00 00 01 02 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 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 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 read: 0e 06 00 12 84 00 3f 50 70 19 00 Got message seqno 6 (command_sequence == 6) response: 12 84 00 3F 50 70 19 00 AVR sign-on responded with device ID = 0x1970503F : Ver = 0x1 : Device = 0x9705 : Manuf = 0x1f Automatic device detection: Reported device ID: 0x9705 Looking for device: atmega1284p Configured for device ID: 0x9705 atmega1284p -- Matched with atmega1284p command "set parameter" [0x12, 0x01] 0E 00 07 00 12 01 00 02 00 1F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 01 21 02 FA 00 read: 0e 08 00 12 80 00 Got message seqno 8 (command_sequence == 8) response: 12 80 00 jtagRead command "enter progmode" [0x12, 0x15] 0E 00 09 00 12 15 00 read: 0e 09 00 12 80 00 Got message seqno 9 (command_sequence == 9) response: 12 80 00 command "read memory" [0x12, 0x21] 0E 00 0A 00 12 21 00 B2 00 00 00 00 03 00 00 00 read: 0e 0a 00 12 84 00 ff 19 ff 00 Got message seqno 10 (command_sequence == 10) response: 12 84 00 FF 19 FF 00 command "leave progmode" [0x12, 0x16] 0E 00 0B 00 12 16 00 read() timed out command "leave progmode" [0x12, 0x16] 0E 00 0B 00 12 16 00 read() timed out command "leave progmode" [0x12, 0x16] 0E 00 0B 00 12 16 00 read: 0e 00 00 00 12 40 00 00 00 00 02 08 00 Event serial 0x0000 Got message seqno 65535 (command_sequence == 11) got asynchronous event: 0x12, 0x40 read: 0e 0b 00 12 80 00 Got message seqno 11 (command_sequence == 11) response: 12 80 00 command "set parameter" [0x12, 0x01] 0E 00 0C 00 12 01 00 03 00 01 00 read: 0e 0b 00 12 a0 00 12 Got message seqno 11 (command_sequence == 12) got wrong sequence number, 11 != 12 read: 0e 0c 00 12 80 00 Got message seqno 12 (command_sequence == 12) response: 12 80 00 command "reset" [0x12, 0x30] 0E 00 0D 00 12 30 00 01 read() timed out retrying reset ... command "reset" [0x12, 0x30] 0E 00 0D 00 12 30 00 01 read() timed out command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 read: 0d 00 00 00 0e 0d 00 Got message seqno 0 (command_sequence == 13) got wrong sequence number, 0 != 13 unexpected message size from pipe: 1006673938 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 65620 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 16402 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 0 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 0 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 read() timed out command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 read: 07 00 00 00 0e 0d 00 12 a0 00 3c 54 00 Got message seqno 0 (command_sequence == 13) got wrong sequence number, 0 != 13 unexpected message size from pipe: 1074921474 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 0 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 100663296 command "stop debugging" [0x12, 0x14] 0E 00 0D 00 12 14 00 unexpected message size from pipe: 234881024 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: -2146303987 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 1536 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 855552 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 100696082 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 234881024 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: -2146303987 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 1536 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 855552 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 100696082 command "AVR sign-off" [0x12, 0x11] 0E 00 0D 00 12 11 00 unexpected message size from pipe: 234881024 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: -2146303987 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 1536 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 855552 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 100696082 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 234881024 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: -2146303987 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 1536 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 855552 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 100696082 command "sign-off" [0x01, 0x11] 0E 00 0D 00 01 11 00 unexpected message size from pipe: 234881024 --- > Are there any compiler warnings which could be related? Here's the output from make (without entering/leaving directories) --- gcc -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -MT crc16.o -MD -MP -MF .deps/crc16.Tpo -c -o crc16.o crc16.c mv -f .deps/crc16.Tpo .deps/crc16.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT devdescr.o -MD -MP -MF .deps/devdescr.Tpo -c -o devdescr.o devdescr.cc mv -f .deps/devdescr.Tpo .deps/devdescr.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT ioreg.o -MD -MP -MF .deps/ioreg.Tpo -c -o ioreg.o ioreg.cc mv -f .deps/ioreg.Tpo .deps/ioreg.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2bp.o -MD -MP -MF .deps/jtag2bp.Tpo -c -o jtag2bp.o jtag2bp.cc mv -f .deps/jtag2bp.Tpo .deps/jtag2bp.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2io.o -MD -MP -MF .deps/jtag2io.Tpo -c -o jtag2io.o jtag2io.cc mv -f .deps/jtag2io.Tpo .deps/jtag2io.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2misc.o -MD -MP -MF .deps/jtag2misc.Tpo -c -o jtag2misc.o jtag2misc.cc mv -f .deps/jtag2misc.Tpo .deps/jtag2misc.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2prog.o -MD -MP -MF .deps/jtag2prog.Tpo -c -o jtag2prog.o jtag2prog.cc mv -f .deps/jtag2prog.Tpo .deps/jtag2prog.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2run.o -MD -MP -MF .deps/jtag2run.Tpo -c -o jtag2run.o jtag2run.cc mv -f .deps/jtag2run.Tpo .deps/jtag2run.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2rw.o -MD -MP -MF .deps/jtag2rw.Tpo -c -o jtag2rw.o jtag2rw.cc mv -f .deps/jtag2rw.Tpo .deps/jtag2rw.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag2usb.o -MD -MP -MF .deps/jtag2usb.Tpo -c -o jtag2usb.o jtag2usb.cc jtag2usb.cc: In function void* usb_thread_event(void*): jtag2usb.cc:973:52: warning: ignoring return value of ssize_t write(int, const void*, size_t), declared with attribute warn_unused_result [-Wunused-result] jtag2usb.cc: In function void* usb_thread_read(void*): jtag2usb.cc:921:52: warning: ignoring return value of ssize_t write(int, const void*, size_t), declared with attribute warn_unused_result [-Wunused-result] mv -f .deps/jtag2usb.Tpo .deps/jtag2usb.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag3bp.o -MD -MP -MF .deps/jtag3bp.Tpo -c -o jtag3bp.o jtag3bp.cc mv -f .deps/jtag3bp.Tpo .deps/jtag3bp.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag3io.o -MD -MP -MF .deps/jtag3io.Tpo -c -o jtag3io.o jtag3io.cc mv -f .deps/jtag3io.Tpo .deps/jtag3io.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag3misc.o -MD -MP -MF .deps/jtag3misc.Tpo -c -o jtag3misc.o jtag3misc.cc mv -f .deps/jtag3misc.Tpo .deps/jtag3misc.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag3prog.o -MD -MP -MF .deps/jtag3prog.Tpo -c -o jtag3prog.o jtag3prog.cc mv -f .deps/jtag3prog.Tpo .deps/jtag3prog.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag3run.o -MD -MP -MF .deps/jtag3run.Tpo -c -o jtag3run.o jtag3run.cc mv -f .deps/jtag3run.Tpo .deps/jtag3run.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtag3rw.o -MD -MP -MF .deps/jtag3rw.Tpo -c -o jtag3rw.o jtag3rw.cc mv -f .deps/jtag3rw.Tpo .deps/jtag3rw.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtagbp.o -MD -MP -MF .deps/jtagbp.Tpo -c -o jtagbp.o jtagbp.cc mv -f .deps/jtagbp.Tpo .deps/jtagbp.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtaggeneric.o -MD -MP -MF .deps/jtaggeneric.Tpo -c -o jtaggeneric.o jtaggeneric.cc mv -f .deps/jtaggeneric.Tpo .deps/jtaggeneric.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtagio.o -MD -MP -MF .deps/jtagio.Tpo -c -o jtagio.o jtagio.cc mv -f .deps/jtagio.Tpo .deps/jtagio.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtagmisc.o -MD -MP -MF .deps/jtagmisc.Tpo -c -o jtagmisc.o jtagmisc.cc mv -f .deps/jtagmisc.Tpo .deps/jtagmisc.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtagprog.o -MD -MP -MF .deps/jtagprog.Tpo -c -o jtagprog.o jtagprog.cc mv -f .deps/jtagprog.Tpo .deps/jtagprog.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtagrun.o -MD -MP -MF .deps/jtagrun.Tpo -c -o jtagrun.o jtagrun.cc mv -f .deps/jtagrun.Tpo .deps/jtagrun.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT jtagrw.o -MD -MP -MF .deps/jtagrw.Tpo -c -o jtagrw.o jtagrw.cc jtagrw.cc: In member function virtual uchar* jtag1::jtagRead(long unsigned int, unsigned int): jtagrw.cc:134:13: warning: converting false to pointer type uchar* {aka unsigned char*} [-Wconversion-null] mv -f .deps/jtagrw.Tpo .deps/jtagrw.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.cc mv -f .deps/main.Tpo .deps/main.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT remote.o -MD -MP -MF .deps/remote.Tpo -c -o remote.o remote.cc mv -f .deps/remote.Tpo .deps/remote.Po g++ -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -pthread -MT utils.o -MD -MP -MF .deps/utils.Tpo -c -o utils.o utils.cc mv -f .deps/utils.Tpo .deps/utils.Po gcc -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -MT gnu_getopt.o -MD -MP -MF .deps/gnu_getopt.Tpo -c -o gnu_getopt.o gnu_getopt.c mv -f .deps/gnu_getopt.Tpo .deps/gnu_getopt.Po gcc -DHAVE_CONFIG_H -I. -DENABLE_TARGET_PROGRAMMING=0 -g -O2 -MT gnu_getopt1.o -MD -MP -MF .deps/gnu_getopt1.Tpo -c -o gnu_getopt1.o gnu_getopt1.c mv -f .deps/gnu_getopt1.Tpo .deps/gnu_getopt1.Po g++ -g -O2 -pthread -o avarice crc16.o devdescr.o ioreg.o jtag2bp.o jtag2io.o jtag2misc.o jtag2prog.o jtag2run.o jtag2rw.o jtag2usb.o jtag3bp.o jtag3io.o jtag3misc.o jtag3prog.o jtag3run.o jtag3rw.o jtagbp.o jtaggeneric.o jtagio.o jtagmisc.o jtagprog.o jtagrun.o jtagrw.o main.o remote.o utils.o gnu_getopt.o gnu_getopt1.o -lusb -lbfd -liberty make[2]: Leaving directory `/home/joakim/tmp/avarice-code/avarice/src' --- Another note is that it works fine with a Dragon. Regards /Joakim |
13 messages has been excluded from this view by a project administrator.
