Re: [Avr-eclipse-devel] AVR Hardware debugging continued

[Thomas H. <th...@in...>]

Yes, it works now. Looks great!

Can I talk you into doing a few improvements? :-)

1. There is still a minor bug that causes the launch to fail if the JTAG 
bitrate has not been set.
In AvariceGDBServerFactory.java line 52 you should check if the bitrate 
has been set and only add the -B option if required.

2. It would be nice to have some options to control where the debugger 
will stop for the first time. Default should be "main", with the option 
to switch it off.
Currently the debugger halts at the very first instruction (address 
0x00000, the reset vector). This should be optional and be off by 
default as most C developers probably won't care about anything 
happening before main().
GDBJtagStartupTab.java in org.eclipse.cdt.debug.gdbjtag.ui should 
contain all the needed code.


3. The "Build before start" feature should be off by default, as makes 
no sense to build the project if it is not uploaded to the device afterward.

4. Of course it would be nice to have an auto-upload feature :-)
But this should best be done with avrdude, as avarice is both slow and 
buggy with regard to uploading flash memory.

5. AVRGDBFinalLaunchSequence.java could probably be streamlined a bit, 
it has some steps that are not necessary for AVR debugging (e.g. 
Executable Arguments, Shared Libraries)


I could do this myself, but I would rather finish the other big change 
that working on, multiple paths support (to make it easy to switch 
between different compiler versions).


Cheers,

Thomas


On 03.03.2012 23:58, Michael Lipp wrote:
> OK, I found the problem. Please sync again with 
> gi...@gi...:mnlipp/avr-eclipse-fork.git, it should work now.
>
> Regards,
>
>     Michael
>
> Am 03.03.2012 21:56, schrieb Michael Lipp:
>> [Regarding 
>> https://sourceforge.net/projects/avr-eclipse/forums/forum/664382/topic/5071000]
>>
>> Hi,
>>
>> well, I'm afraid this is part of the "haven't done such an advanced 
>> plugin before". I had created a Hardware Debugging Tab at some time 
>> during my development (before I have done anything, actually) and 
>> used this all the time. I get the same error as you do now when I try 
>> to create a new tab (had not tried that up to now).
>>
>> I still have to understand that. Right now, I don't know what 
>> extension I should have provided where and why.
>>
>>  - Michael