From: Thomas H. <th...@in...> - 2012-03-03 19:47:15
|
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 > |