Update: I lied.
Actually, it doesn't behave the same: if the chip isn't programmed, it doesn't
really work at all; no surprise. When the chip is programmed, however, the
single stepping, and running to a breakpoint is still VERY slow.
If you 'cont', the system runs properly at full speed. While running, I can hit
a CTRL-C to stop execution, set a breakpoint, and run to the breakpoint.
So it's working, it's just that the single-step/breakpoint situation is
unbearably slow.
________________________________
From: Bob Wirka <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Friday, March 23, 2012 9:14 AM
Subject: Re: [AVaRICE-user] Slow debugging with Avarice and gdb
Update:
I've got three script files; one will erase the program, a second will program
the chip, and a third will start avarice as a gdb server. Running in Ubuntu
Linux.
erase: avarice --mkII --jtag usb --jtag-bitrate 1000 --part atmega644
--erase
program: avarice --mkII --jtag usb --jtag-bitrate 1000 --part atmega644
--erase --program --verify --file $1
debug: avarice --mkII --jtag usb --jtag-bitrate 1000 --part atmega644 :2345
It **appears** to debug even if the chip is erased, and no program has been
loaded. I can erase the chip, start avarice as gdbserver, run up avr-gdb,
connect with gdbserver, and debug VERY slowly. This can't be right. There
appears to be no difference in behavior between when I've programmed the chip,
and when I haven't.
There HAS to be a simple mistake here...
________________________________
From: Bob Wirka <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Friday, March 23, 2012 8:32 AM
Subject: [AVaRICE-user] Slow debugging with Avarice and gdb
Single stepping, and running to a breakpoint is VERY slow with Avarice and gdb.
AVR Studio doesn't have this problem, so it must be solvable.
Using a JTAGice MKII in Windows and Linux, target is an ATmega644, using
Eclipse with the AVR plugin (what a great item!).
Experiencing the same performance on both Windows (7) and Linux (Ubuntu 11.10).
Have compiled revision 2.12 on Linux, as well as trying revision 2.10 from
Ubuntu. Have tried command line gdb, and gdb from Eclipse.
Hoping this can be fixed by proper command line invocation of avarice, and/or
the right "set remote" commands from within gdb.
Can anyone point me in the right direction?
Thanks,
Bob Wirka
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
avarice-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/avarice-user
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
avarice-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/avarice-user
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
avarice-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/avarice-user
