avr-eclipse-user

[Avr-eclipse-user] What versions of eclipse/cdt are known to work with AVREclipse?

[Steve J. <st...@is...>]

Hi,

I'm cannot get debugging to work with more recent versions of eclipse than 3.4 (Ganymede).

I'm using an ATMEL/AVR JTAG MK2 on windows with WinAVR-20100110. Even on Ganymede single stepping is 
very slow (5 seconds per step).

On eclipse 3.5 and 3.6 hardware debugging fails to start on both. I can download using AVRDude OK. 
WinAVR/avr-gdb starts up and acknowledges a connection but eclipse fails to enter the debug perspective.

Are there known issues with later versions of eclipse or am I doing something wrong?

Thank, Steve.

Re: [Avr-eclipse-user] What versions of eclipse/cdt are known to work with AVREclipse?

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

  Hi Steve,

so far I haven't had any problems with debugging on any Eclipse Version 
up to and including Helios.
Could you post the console output of avr-gdb and of avarice to see what 
is going on? You can use the little icon that looks like a computer 
screen on the top right of the 'Console' view to switch between the 
different consoles.

Also debugging with avarice and AVR processors is generally slow, AFAIK 
due to inefficient protocols (reverse engineered because Atmel has not 
released the MK2 communication protocol). This is aggravated by Eclipse 
as it tries to read all AVR registers after each step.
However 5 seconds per step seems rather slow. With my AVRDragon (usually 
connected to an AVR Butterfly for testing) It takes maybe 0,5 to 1 sec 
per step.

Maybe you can increase the JTAG bitrate to improve the speed. Take a 
look at the '--jtag-bitrate' option of avarice any see if it helps.
Another thing to improve single stepping is to change to 'Instruction 
step mode'. Instead of single stepping the C source this mode will step 
single assembler instructions, which is usually faster. IIRC this is 
activated by clicking on the little 'I' Icon next to the 'Step in', 
'Step over' and 'Step out' icons.

Cheers,

Thomas


On 08.10.2010 14:43, Steve Jones wrote:
> Hi,
>
> I'm cannot get debugging to work with more recent versions of eclipse than 3.4 (Ganymede).
>
> I'm using an ATMEL/AVR JTAG MK2 on windows with WinAVR-20100110. Even on Ganymede single stepping is
> very slow (5 seconds per step).
>
> On eclipse 3.5 and 3.6 hardware debugging fails to start on both. I can download using AVRDude OK.
> WinAVR/avr-gdb starts up and acknowledges a connection but eclipse fails to enter the debug perspective.
>
> Are there known issues with later versions of eclipse or am I doing something wrong?
>
> Thank, Steve.
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> avr-eclipse-user mailing list
> avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>

Re: [Avr-eclipse-user] What versions of eclipse/cdt are known to work with AVREclipse?

[Steve J. <st...@is...>]

Hi Thomas,

On Ganymede (which works), I enter the Debug perspective and halt on main(). The console views(s) 
for the debug session are empty.

Using the same eclipse workspace and project, If I try the same on Helios I just stay in the C/C++ 
perspective. The console view for "C/C++ Attach to Application gdb traces" contains the following:

315,583 1-environment-cd D:/ubuntu/contiki/eclipse/world
315,598 1^done
315,598 (gdb)
315,598 2-file-exec-and-symbols D:/ubuntu/contiki/eclipse/world/Debug/world.elf
315,614 2^done
315,614 (gdb)
315,614 3-gdb-set auto-solib-add on
315,629 3^done
315,629 (gdb)
315,661 4-environment-directory D:/ubuntu/contiki/eclipse/world D:/ubuntu/contiki/eclipse/world/.set\
tings D:/ubuntu/contiki/eclipse/world/Debug D:/ubuntu/contiki/eclipse/world/Debug/src D:/ubuntu/cont\
iki/eclipse/world/src
315,676 4^done,source-path="D:/ubuntu/contiki/eclipse/world;D:/ubuntu/contiki/eclipse/world/.setting\
s;D:/ubuntu/contiki/eclipse/world/Debug;D:/ubuntu/contiki/eclipse/world/Debug/src;D:/ubuntu/contiki/\
eclipse/world/src;$cdir;$cwd"
315,676 (gdb)
315,676 5-target-select extended-remote localhost:4242
316,706 5^connected,thread-id="0",frame={addr="0x00000000",func="__vectors",args=[]}
316,706 (gdb)

I know switching between eclipse versions on the same workspace is not a good idea but I originally 
started with Helios. When that failed I want back to Ganymede and it worked.

I'm not sure which of the debug launch configurations it is best to use. I've been using "C/C++ 
Attach to Application". The "GDB Hardware Debugging" configuration is not in the standard Helios/CDT 
download, see:

http://download.eclipse.org/tools/cdt/releases/helios/

I also have Ubuntu 10.4 running under VMWare on the same PC. Would it be better to use that as my 
base system instead of Windows?

Anyway, now that I know it should be work on Helios I'll persevere a while longer though any 
suggestions would be most welcome.

Cheers, Steve.



On 09/10/2010 21:47, Thomas Holland wrote:
>    Hi Steve,
>
> so far I haven't had any problems with debugging on any Eclipse Version
> up to and including Helios.
> Could you post the console output of avr-gdb and of avarice to see what
> is going on? You can use the little icon that looks like a computer
> screen on the top right of the 'Console' view to switch between the
> different consoles.
>
> Also debugging with avarice and AVR processors is generally slow, AFAIK
> due to inefficient protocols (reverse engineered because Atmel has not
> released the MK2 communication protocol). This is aggravated by Eclipse
> as it tries to read all AVR registers after each step.
> However 5 seconds per step seems rather slow. With my AVRDragon (usually
> connected to an AVR Butterfly for testing) It takes maybe 0,5 to 1 sec
> per step.
>
> Maybe you can increase the JTAG bitrate to improve the speed. Take a
> look at the '--jtag-bitrate' option of avarice any see if it helps.
> Another thing to improve single stepping is to change to 'Instruction
> step mode'. Instead of single stepping the C source this mode will step
> single assembler instructions, which is usually faster. IIRC this is
> activated by clicking on the little 'I' Icon next to the 'Step in',
> 'Step over' and 'Step out' icons.
>
> Cheers,
>
> Thomas
>
>
> On 08.10.2010 14:43, Steve Jones wrote:
>> Hi,
>>
>> I'm cannot get debugging to work with more recent versions of eclipse than 3.4 (Ganymede).
>>
>> I'm using an ATMEL/AVR JTAG MK2 on windows with WinAVR-20100110. Even on Ganymede single stepping is
>> very slow (5 seconds per step).
>>
>> On eclipse 3.5 and 3.6 hardware debugging fails to start on both. I can download using AVRDude OK.
>> WinAVR/avr-gdb starts up and acknowledges a connection but eclipse fails to enter the debug perspective.
>>
>> Are there known issues with later versions of eclipse or am I doing something wrong?
>>
>> Thank, Steve.
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&   L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> avr-eclipse-user mailing list
>> avr...@li...
>> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>>
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> avr-eclipse-user mailing list
> avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>

Re: [Avr-eclipse-user] What versions of eclipse/cdt are known to work with AVREclipse?

[Steve J. <st...@is...>]

Hi,

I can confirm that avrEclipse works with Helios. My set-up is Ubuntu 10.04 running under VMWare on a 
WIN7 host. On the host the ATMEL jtag USB driver has been replaced with the usblib driver from 
winAVR (C:\WinAVR-20100110\utils\libusb\bin)

On Ubuntu I have:

eclipse-cpp-helios-SR1-linux-gtk.tar.gz

and (just, no other plugins)

avreclipse-p2-repository-2.3.4.20100807PRD

To setup for debugging using an ATMEL JTAG ICE MK2 I load the hex onto my target and kick off 
avarice in a linux terminal window with:

avarice --erase --file myprog.hex -2 --ignore-intr --jtag usb :4242

OR if the target is already flashed:

avarice -2 --ignore-intr --jtag usb :4242

Then follow the "Debugging on the target/Helios" instructions in

http://embedded-linux.co.uk/tutorial/eclipse-cross-compile

The only difference being:

GDB Debugger: avr-gdb
Connection: TCP, localhost, 4242

Pressing "Debug" brings up the debug perspective with the source code window on main(). Breakpoints 
work.

I imagine the same set up will work directly on Windows/WinAVR/Helios though I've not tried it.


Cheers, Steve.


On 10/10/2010 09:03, Steve Jones wrote:
> Hi Thomas,
>
> On Ganymede (which works), I enter the Debug perspective and halt on main(). The console views(s)
> for the debug session are empty.
>
> Using the same eclipse workspace and project, If I try the same on Helios I just stay in the C/C++
> perspective. The console view for "C/C++ Attach to Application gdb traces" contains the following:
>
> 315,583 1-environment-cd D:/ubuntu/contiki/eclipse/world
> 315,598 1^done
> 315,598 (gdb)
> 315,598 2-file-exec-and-symbols D:/ubuntu/contiki/eclipse/world/Debug/world.elf
> 315,614 2^done
> 315,614 (gdb)
> 315,614 3-gdb-set auto-solib-add on
> 315,629 3^done
> 315,629 (gdb)
> 315,661 4-environment-directory D:/ubuntu/contiki/eclipse/world D:/ubuntu/contiki/eclipse/world/.set\
> tings D:/ubuntu/contiki/eclipse/world/Debug D:/ubuntu/contiki/eclipse/world/Debug/src D:/ubuntu/cont\
> iki/eclipse/world/src
> 315,676 4^done,source-path="D:/ubuntu/contiki/eclipse/world;D:/ubuntu/contiki/eclipse/world/.setting\
> s;D:/ubuntu/contiki/eclipse/world/Debug;D:/ubuntu/contiki/eclipse/world/Debug/src;D:/ubuntu/contiki/\
> eclipse/world/src;$cdir;$cwd"
> 315,676 (gdb)
> 315,676 5-target-select extended-remote localhost:4242
> 316,706 5^connected,thread-id="0",frame={addr="0x00000000",func="__vectors",args=[]}
> 316,706 (gdb)
>
> I know switching between eclipse versions on the same workspace is not a good idea but I originally
> started with Helios. When that failed I want back to Ganymede and it worked.
>
> I'm not sure which of the debug launch configurations it is best to use. I've been using "C/C++
> Attach to Application". The "GDB Hardware Debugging" configuration is not in the standard Helios/CDT
> download, see:
>
> http://download.eclipse.org/tools/cdt/releases/helios/
>
> I also have Ubuntu 10.4 running under VMWare on the same PC. Would it be better to use that as my
> base system instead of Windows?
>
> Anyway, now that I know it should be work on Helios I'll persevere a while longer though any
> suggestions would be most welcome.
>
> Cheers, Steve.
>
>
>
> On 09/10/2010 21:47, Thomas Holland wrote:
>>     Hi Steve,
>>
>> so far I haven't had any problems with debugging on any Eclipse Version
>> up to and including Helios.
>> Could you post the console output of avr-gdb and of avarice to see what
>> is going on? You can use the little icon that looks like a computer
>> screen on the top right of the 'Console' view to switch between the
>> different consoles.
>>
>> Also debugging with avarice and AVR processors is generally slow, AFAIK
>> due to inefficient protocols (reverse engineered because Atmel has not
>> released the MK2 communication protocol). This is aggravated by Eclipse
>> as it tries to read all AVR registers after each step.
>> However 5 seconds per step seems rather slow. With my AVRDragon (usually
>> connected to an AVR Butterfly for testing) It takes maybe 0,5 to 1 sec
>> per step.
>>
>> Maybe you can increase the JTAG bitrate to improve the speed. Take a
>> look at the '--jtag-bitrate' option of avarice any see if it helps.
>> Another thing to improve single stepping is to change to 'Instruction
>> step mode'. Instead of single stepping the C source this mode will step
>> single assembler instructions, which is usually faster. IIRC this is
>> activated by clicking on the little 'I' Icon next to the 'Step in',
>> 'Step over' and 'Step out' icons.
>>
>> Cheers,
>>
>> Thomas
>>
>>
>> On 08.10.2010 14:43, Steve Jones wrote:
>>> Hi,
>>>
>>> I'm cannot get debugging to work with more recent versions of eclipse than 3.4 (Ganymede).
>>>
>>> I'm using an ATMEL/AVR JTAG MK2 on windows with WinAVR-20100110. Even on Ganymede single stepping is
>>> very slow (5 seconds per step).
>>>
>>> On eclipse 3.5 and 3.6 hardware debugging fails to start on both. I can download using AVRDude OK.
>>> WinAVR/avr-gdb starts up and acknowledges a connection but eclipse fails to enter the debug perspective.
>>>
>>> Are there known issues with later versions of eclipse or am I doing something wrong?
>>>
>>> Thank, Steve.
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&    L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>> _______________________________________________
>>> avr-eclipse-user mailing list
>>> avr...@li...
>>> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&   L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> avr-eclipse-user mailing list
>> avr...@li...
>> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>>
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> avr-eclipse-user mailing list
> avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>