avr-eclipse-user

[Avr-eclipse-user] No source code when debugging using JTAG

[Lukáš Z. <luk...@gm...>]

Hi,

first I would like to thank all the people who are involved in the
development and community around the avr-eclipse. You have done a great
job porting AVR development to Linux world and this is very important to
me. :)

And here comes my question:

I set up avr-eclipse plugin 2.3.4.20100807PRD into Eclipse Indigo
release  20110615-0604 on Linux Ubuntu 10.10 64 bit
Everything seems to be working fine except JTAG debugging. I manually
start avarice server through the JTAG connection to the device
(ATmega32) using JTAG mk I cable clone - works perfectly on windows
using AVR Studio 4. Connection seems to be ok, signature loaded and
waiting for connections.

I prepared debugging configuration using avr-gdb settings from the wiki
page (slightly changed due to different wizards in indigo but
semantically should be the same). Set breakpoint at is set to "main".

When I start debugging, eclipse is properly connected to the avarice,
which communicates with AVR. Code doesn't break at main but runs. When I
break it, I can read registers, explore the memory and see the break
point in the disassembler window.

The problem:

I cannot see any code in the code window, just address into the program
memory. It corresponds correctly with the content of the disassembler
window. When I switch the debugging into the instruction mode, stepping
works fine. But in the disassembler window, code is not included, just
instructions. (in the screenshot on the wiki there are lines of code
included).

I suspected wrong settings of the source tab of the debug wizard, but my
simple testing program is located in the root folder of the project and
this folder cannot be added to the source lookup paths.

Code is compiled with -g3 switch set in the tool chain.

Do please anybody have an idea why this happens?
Can it be related to the version of the Eclipse?
Some bad settings?
Can it be related to the location of the source file being in the root
of project?

I just don't know and I spent few days testing variety of different
settings. I still suspect some wrong connection between the code and the
runtime position in the program memory because of wrong settings of the
project (or compiler).
I don't know if it is of any significance but debugging of the C code
for PC machine in the same Eclipse and workspace works fine.

Thank you for reading this long thing and also thanks for any answer.

Best

Lukas Zaruba

Re: [Avr-eclipse-user] No source code when debugging using JTAG

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

Hello Lukás(,

sorry for the late reply, but I was busy the last few days.

With regard to your problem: Do you have the "Load symbols" flag set on 
the "Startup" Tab in the debug lauch configuration?



If you do not have a "Startup" tab, then you need to install the "C/C++ 
GDB Hardware Debugging" plugin. It is an optional part of CDT and it 
seems that with Eclipse Indigo you must have this installed to do JTAG 
debugging.



On 24.02.2012 19:32, Lukás( Záruba wrote:
> Hi,
>
> first I would like to thank all the people who are involved in the
> development and community around the avr-eclipse. You have done a great
> job porting AVR development to Linux world and this is very important to
> me. :)
>
> And here comes my question:
>
> I set up avr-eclipse plugin 2.3.4.20100807PRD into Eclipse Indigo
> release  20110615-0604 on Linux Ubuntu 10.10 64 bit
> Everything seems to be working fine except JTAG debugging. I manually
> start avarice server through the JTAG connection to the device
> (ATmega32) using JTAG mk I cable clone - works perfectly on windows
> using AVR Studio 4. Connection seems to be ok, signature loaded and
> waiting for connections.
>
> I prepared debugging configuration using avr-gdb settings from the wiki
> page (slightly changed due to different wizards in indigo but
> semantically should be the same). Set breakpoint at is set to "main".
>
> When I start debugging, eclipse is properly connected to the avarice,
> which communicates with AVR. Code doesn't break at main but runs. When I
> break it, I can read registers, explore the memory and see the break
> point in the disassembler window.
>
> The problem:
>
> I cannot see any code in the code window, just address into the program
> memory. It corresponds correctly with the content of the disassembler
> window. When I switch the debugging into the instruction mode, stepping
> works fine. But in the disassembler window, code is not included, just
> instructions. (in the screenshot on the wiki there are lines of code
> included).
>
> I suspected wrong settings of the source tab of the debug wizard, but my
> simple testing program is located in the root folder of the project and
> this folder cannot be added to the source lookup paths.
>
> Code is compiled with -g3 switch set in the tool chain.
>
> Do please anybody have an idea why this happens?
> Can it be related to the version of the Eclipse?
> Some bad settings?
> Can it be related to the location of the source file being in the root
> of project?
>
> I just don't know and I spent few days testing variety of different
> settings. I still suspect some wrong connection between the code and the
> runtime position in the program memory because of wrong settings of the
> project (or compiler).
> I don't know if it is of any significance but debugging of the C code
> for PC machine in the same Eclipse and workspace works fine.
>
> Thank you for reading this long thing and also thanks for any answer.
>
> Best
>
> Lukas Zaruba
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> avr-eclipse-user mailing list
> avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>

Re: [Avr-eclipse-user] No source code when debugging using JTAG

[Lukáš Z. <luk...@gm...>]

Hi Thomas,
thank you for your reply. It was more than helpful.
I had "Load image" checked but not "Load symbols" in the latest
configuration saved when I went strictly by procedures recommended in
the tutorial here
http://avr-eclipse.sourceforge.net/wiki/index.php/Debugging#GDB_Hardware_Debugging
. I would swear that I tried this settings you sent before with no luck.

I suspect one more problem although I am not able to reproduce it and
prove. On the main page in the default (of Indigo Eclipse) in the
section "Build (if required) ... " Select configuration using C/C++
Application is checked together with use workspace settings.

Because I was always building Release builds I suspect Eclipse to create
the Release build automatically when needed and release wouldn't contain
debugging options. I came to this idea because after I checked load
symbols first time it didn't help. I saw in the console something like
"Cannot load symbols, no symbols found in xxxxx.elf" if I remember
right. After that I tried to change settings on the main page to
automatic build of Debug and it started working as a charm. But now when
I turn the main page to the original state it keeps working just fine.
This is just the feeling with no real proof and I may be totally off ;)

Anyway I would like to thank you again for the help. No I am able to
debug in C and I am finally free from the AVR Studio :)

There is one more thing in my head:
In the registers view in the debug perspective there is only one section
"General Registers". I wonder if it is possible to show there
(optionally perhaps) other important registers (not really registers but
IO memory) as shown in AVR studio or VMLAB. It would be more than useful
I guess.
While I am much better in developing plugins for Eclipse than in AVR C
development ;) I would like to offer my help creating this feature if
possible. (Off the top of my head -> reuse backend of Memory window, use
definitions for specific MCUs to search for addresses to read and to
translate the loaded data into some human readable output possibly even
with "translations" of applied values like "UART - 9,6k no parity,
....."). I like this feature in the VMLAB but there are obsolete
definitions and it is simulation only.

If you think this is something worth exploring, just let me know and I
will try look into it.

Thanks again

Best regards

Lukas Zaruba
 

Dne 3.3.2012 20:46, Thomas Holland napsal(a):
> Hello Lukáš,
>
> sorry for the late reply, but I was busy the last few days.
>
> With regard to your problem: Do you have the "Load symbols" flag set
> on the "Startup" Tab in the debug lauch configuration?
>
>
>
> If you do not have a "Startup" tab, then you need to install the
> "C/C++ GDB Hardware Debugging" plugin. It is an optional part of CDT
> and it seems that with Eclipse Indigo you must have this installed to
> do JTAG debugging.
>
>
>
> On 24.02.2012 19:32, Lukáš Záruba wrote:
>> Hi,
>>
>> first I would like to thank all the people who are involved in the
>> development and community around the avr-eclipse. You have done a great
>> job porting AVR development to Linux world and this is very important to
>> me. :)
>>
>> And here comes my question:
>>
>> I set up avr-eclipse plugin 2.3.4.20100807PRD into Eclipse Indigo
>> release  20110615-0604 on Linux Ubuntu 10.10 64 bit
>> Everything seems to be working fine except JTAG debugging. I manually
>> start avarice server through the JTAG connection to the device
>> (ATmega32) using JTAG mk I cable clone - works perfectly on windows
>> using AVR Studio 4. Connection seems to be ok, signature loaded and
>> waiting for connections.
>>
>> I prepared debugging configuration using avr-gdb settings from the wiki
>> page (slightly changed due to different wizards in indigo but
>> semantically should be the same). Set breakpoint at is set to "main".
>>
>> When I start debugging, eclipse is properly connected to the avarice,
>> which communicates with AVR. Code doesn't break at main but runs. When I
>> break it, I can read registers, explore the memory and see the break
>> point in the disassembler window.
>>
>> The problem:
>>
>> I cannot see any code in the code window, just address into the program
>> memory. It corresponds correctly with the content of the disassembler
>> window. When I switch the debugging into the instruction mode, stepping
>> works fine. But in the disassembler window, code is not included, just
>> instructions. (in the screenshot on the wiki there are lines of code
>> included).
>>
>> I suspected wrong settings of the source tab of the debug wizard, but my
>> simple testing program is located in the root folder of the project and
>> this folder cannot be added to the source lookup paths.
>>
>> Code is compiled with -g3 switch set in the tool chain.
>>
>> Do please anybody have an idea why this happens?
>> Can it be related to the version of the Eclipse?
>> Some bad settings?
>> Can it be related to the location of the source file being in the root
>> of project?
>>
>> I just don't know and I spent few days testing variety of different
>> settings. I still suspect some wrong connection between the code and the
>> runtime position in the program memory because of wrong settings of the
>> project (or compiler).
>> I don't know if it is of any significance but debugging of the C code
>> for PC machine in the same Eclipse and workspace works fine.
>>
>> Thank you for reading this long thing and also thanks for any answer.
>>
>> Best
>>
>> Lukas Zaruba
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing 
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> avr-eclipse-user mailing list
>> avr...@li...
>> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user
>>
>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing 
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>
>
> _______________________________________________
> avr-eclipse-user mailing list
> avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user

Re: [Avr-eclipse-user] No source code when debugging using JTAG

[Jon E. <li...@dr...>]

On 17/03/12 14:53, Lukáš Záruba wrote:

> There is one more thing in my head:
> In the registers view in the debug perspective there is only one section
> "General Registers". I wonder if it is possible to show there
> (optionally perhaps) other important registers (not really registers but
> IO memory) as shown in AVR studio or VMLAB. It would be more than useful
> I guess.
> While I am much better in developing plugins for Eclipse than in AVR C
> development ;) I would like to offer my help creating this feature if
> possible. (Off the top of my head -> reuse backend of Memory window, use
> definitions for specific MCUs to search for addresses to read and to
> translate the loaded data into some human readable output possibly even
> with "translations" of applied values like "UART - 9,6k no parity,
> ....."). I like this feature in the VMLAB but there are obsolete
> definitions and it is simulation only.
>
> If you think this is something worth exploring, just let me know and I
> will try look into it.
>
> Thanks again
>
> Best regards
>
> Lukas Zaruba
>

Hi Lukas,

I think an IO / register view would be a great feature to add. I looked 
into it myself once, but found the Eclipse plugin learning curve too steep!

Regards,
Jon

Re: [Avr-eclipse-user] No source code when debugging using JTAG

[Lukáš Z. <luk...@gm...>]

Hi,
I gave it a look and few minutes of stepping into it and found out that
Registry view is created in the very strange fashion which practically
disallow any add-ons while it is hardcoded and not loaded from
contributions as one would expect from Eclipse Plugin. (My humble
opinion after very short examination).
But I checked how the register data and memory view data are gathered
from the gdb interface and it shouldn't be too hard to use. I will
probably hack the AVR Device Explorer view to reflect selected project
MCU and add once column with value. It seems to be the easiest place to
plug into because there already is a list of registers, its addresses.
Special view can be created later which could cover general purpose
register as well and it would be replacement of the current Registers view.

If anyone has some idea please share. I am happy to create something
what could be useful for the community but I don't have many
opportunities to do so. I will enjoy this one :)

Best Regards

LZ

Dne 20.3.2012 20:51, Jon Escombe napsal(a):
> On 17/03/12 14:53, Lukáš Záruba wrote:
>
>> There is one more thing in my head:
>> In the registers view in the debug perspective there is only one section
>> "General Registers". I wonder if it is possible to show there
>> (optionally perhaps) other important registers (not really registers but
>> IO memory) as shown in AVR studio or VMLAB. It would be more than useful
>> I guess.
>> While I am much better in developing plugins for Eclipse than in AVR C
>> development ;) I would like to offer my help creating this feature if
>> possible. (Off the top of my head -> reuse backend of Memory window, use
>> definitions for specific MCUs to search for addresses to read and to
>> translate the loaded data into some human readable output possibly even
>> with "translations" of applied values like "UART - 9,6k no parity,
>> ....."). I like this feature in the VMLAB but there are obsolete
>> definitions and it is simulation only.
>>
>> If you think this is something worth exploring, just let me know and I
>> will try look into it.
>>
>> Thanks again
>>
>> Best regards
>>
>> Lukas Zaruba
>>
>
> Hi Lukas,
>
> I think an IO / register view would be a great feature to add. I
> looked into it myself once, but found the Eclipse plugin learning
> curve too steep!
>
> Regards,
> Jon