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 ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ avarice-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/avarice-user
