When I tried the 2.4.0beta I found this really cool "AVR Hardware Debugging"
configuration (plugin actually marked as 2.5.0). This was exactly what I was
pondering about for a student's lab. (Keeping avarice running with the proper
options in a terminal seems to be a major challenge for some.) I was, however,
very disapointed when I found that currently only the user interface is
available, nothing actually being started yet when you hit "Debug".
So I completed the code in order to be able to do avarice and remote debugging
(I don't use simulavr). You can pull the required patch from https://github.com/mnlipp/avr-eclipse-fork. I have tested this only on Linux (Ubuntu) with Indigo and CDT
8.0.2, as this is the only configuration I'm going to need. But I haven't used
anything OS specific, so it should run in other environments as well.
This is the most advanced eclipse plugin I have been working with up to now,
so bare with me if I haven't got everything right. If not usable as is, it
should nevertheless be a good starting point for further development of this
great project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes this is great project, I not have avrice debugger for test, but soon I
build a avrice hardware. I am currently working on a code generator for the
plugin.
sorry for my English Please
best regards.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
first of all thank you for taking time to improve the plugin. I can really use
some help.
I have pulled your fork, but unfortunately it does not work for me. :-(
When I try to create a new "AVR Hardware Debugging" launch configuration it
throws an ArrayIndexOutOfBounds Exception. This is caused by line 133 of the
TabDebugging.java file
DEBUGGER_ID has the value "de.innot.avreclipse.debug.core.AVRGDBDebugger", but
there is no commandFactory extension with a debuggerID element with that
id, which in turn causes the #getDefaultDescriptor() method to fail with the
Exception.
Did you forget to commit the file that contains the custom commandFactory?
BTW I have set up a new avr-eclipse-
devel mailing list. Maybe we
can continue the discussion there as this forum is rather limited in
usability.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I tried the 2.4.0beta I found this really cool "AVR Hardware Debugging"
configuration (plugin actually marked as 2.5.0). This was exactly what I was
pondering about for a student's lab. (Keeping avarice running with the proper
options in a terminal seems to be a major challenge for some.) I was, however,
very disapointed when I found that currently only the user interface is
available, nothing actually being started yet when you hit "Debug".
So I completed the code in order to be able to do avarice and remote debugging
(I don't use simulavr). You can pull the required patch from
https://github.com/mnlipp/avr-eclipse-fork. I have tested this only on Linux (Ubuntu) with Indigo and CDT
8.0.2, as this is the only configuration I'm going to need. But I haven't used
anything OS specific, so it should run in other environments as well.
This is the most advanced eclipse plugin I have been working with up to now,
so bare with me if I haven't got everything right. If not usable as is, it
should nevertheless be a good starting point for further development of this
great project.
Yes this is great project, I not have avrice debugger for test, but soon I
build a avrice hardware. I am currently working on a code generator for the
plugin.
sorry for my English Please
best regards.
Hi,
first of all thank you for taking time to improve the plugin. I can really use
some help.
I have pulled your fork, but unfortunately it does not work for me. :-(
When I try to create a new "AVR Hardware Debugging" launch configuration it
throws an ArrayIndexOutOfBounds Exception. This is caused by line 133 of the
TabDebugging.java file
DEBUGGER_ID has the value "de.innot.avreclipse.debug.core.AVRGDBDebugger", but
there is no commandFactory extension with a debuggerID element with that
id, which in turn causes the #getDefaultDescriptor() method to fail with the
Exception.
Did you forget to commit the file that contains the custom commandFactory?
BTW I have set up a new avr-eclipse-
devel mailing list. Maybe we
can continue the discussion there as this forum is rather limited in
usability.
OK, in case somebody comes along here: discussion continued at
https://sourceforge.net/mailarchive/forum.php?forum_name=avr-eclipse-
devel