Debugging Arduino sketch with STM32 Nucleo in Eclipse .. works !

Michael

The IDE including the Ino file seems like a mistake / bug to me. I suspect they didnt realise there was a reference to it in the elf file as AFIK they its not possible to do in-circuit debugging on AVR and for debugging on the new Arduino Zero people have to use Atmel Studio as their IDE.

I took a quick look on github at the Arduino sources, but there are 168 references to “.ino” so it would take quite a while to figure out precisely which one of those instances is the problem.

I’m not sure but it looks like this commit introduced using ‘#line’ with the .ino source file name the first time:
https://github.com/arduino/Arduino/comm … 359d886ccb

Reason is:
// These #line directives help the compiler report errors with
// correct the filename and line number (issue 281 & 907)

The same function is now in master branch in file: arduino-core/src/processing/app/debug/Compiler.java at around line 1383

and this line most probably makes the compiler to include the .ino file in the .elf too. I’m not an expert in this area but there seems to be a good reason to include the .ino file BUT Eclipse is having a hard time with that

EDIT: Does Atmel Studio handle the .ino file correctly or does it compile it so that it does not include .ino in the .elf at all ?

I’m quite sure now that this looks like a bug in Eclipse under Win32. While debugging I watched trace windows in Eclipse: what is sent to GDB and what GBD responds.

Hitting a breakpoint. this is what GDB prints:

Breakpoint 7, loop () at C:\cygwin\tmp\untitled8842960513440007790.tmp\sketch_sep01a/sketch_sep01a.ino:6
6 void loop() {

The code probably got optimized out of the source. arm-none-eabi-objdump -CS foo.elf is your friend.

you could change the optimization settings in platform.txt, just for debugging.

Yes, I should test this with a code that actually does something. I’ll try the optimization settings too. Would you suggest using -O0 or something else ?

Rick Kimball wrote:The code probably got optimized out of the source. arm-none-eabi-objdump -CS foo.elf is your friend.

But GDB does show the code ? Am I missing something ?

If you run GDB on the command line, it has commands to list the code i.e show the code around the current program counter, and to set breakpoints.

But normally an IDE like Exclipse handles this all for you.

So I’m not to sure what your question is really??

RogerClark wrote:But GDB does show the code ? Am I missing something ?

If you run GDB on the command line, it has commands to list the code i.e show the code around the current program counter, and to set breakpoints.

But normally an IDE like Exclipse handles this all for you.

So I’m not to sure what your question is really??

Sorry Michael

I can’t help with that one. It sounds like a question for the Eclipse forum

RogerClark wrote:Sorry Michael

I can’t help with that one. It sounds like a question for the Eclipse forum

here’s a little bit different situation:

I modified Arduino source code so that full path of .ino file is used

The .cpp generated by Arduino contains now:

#line 1 “c:\\sketch.ino”

in the first line. File is there in c:\sketch.ino

IDE Log:
!ENTRY org.eclipse.cdt.dsf.ui 2 0 2015-09-02 17:25:07.768
!MESSAGE Unable to locate file: c:\sketch.ino

and

Image

So that didn’t work.

Did you press the “Locate File…” button and point it at the source code?

Rick Kimball wrote:Did you press the “Locate File…” button and point it at the source code?

Sounds like you need to setup the file associations in eclipse so that the IDE knows that your .ino file is a C++ file and that the default is to use the Eclipse editor not the System editor (.ino must be associated with the arduino.exe)

A quick search on google indicates it might be a windows only issue, although I haven’t tried on windows. I did test my gdb setup ( command line arm-none-eabi-gdb ) with windows a while back and I was able to make that work. But of course eclipse wasn’t in that mix.

Please let us know exactly what your setup is and maybe we can try to recreate. There are so many places this can fall down, it is hard to guess what is different, what you have changed and what you have set.

-rick

PS I’m often on IRC, and it is often easier to solve these types of problems with a question answer format than a forum.

Rick,

Yeah, would be great to talk in IRC and try out different things. Thanks for your suggestion. I will ll try that too. Actually that really makes sense when I think about that. Eclipse can’t open the file in the IDE because it’s opened by Arduino IDE. However I think Eclipse should just load the file and not try to execute it with default program.

I did test my gdb setup ( command line arm-none-eabi-gdb ) with windows a while back and I was able to make that work. But of course eclipse wasn’t in that mix.

Yes, there’s some small mistake in Eclipse in the file handling part I believe. GBD plays nicely.

In the meanwhile looks like I got this working!! Hacked Arduino IDE sources so that it does not print #line directives:

Here’s the .cpp file produce by Arduino. NOrmally there would be “#line 1 “sketch_02sepb.ino”

#include "Arduino.h"
void setup();
void loop();
void setup() {

}

void loop() {

Serial.println("1234");
Serial.println("5678");
delay(2000);
}

I compiled a simple blink sketch and then loaded the /tmp/xxxx/blink_std.cpp.elf into the eclipse debugger. I didn’t have to modify the arduino ide or mess with #line directives or include a .cpp. When the file associations are correct it should just work …

eclipse_screen.jpg

eclipse_screen.jpg (204.69 KiB) Viewed 812 times

Rick Kimball wrote:I compiled a simple blink sketch and then loaded the /tmp/xxxx/blink_std.cpp.elf into the eclipse debugger. I didn’t have to modify the arduino ide or mess with #line directives or include a .cpp. When the file associations are correct it should just work …

eclipse_screen.jpg

michael, can you post your hacked IDE somewhere, i know a lot of people would be interested in trying it.

michael_l wrote:Tried this and does not work. It still says can’t locate the file. Oh well, I have a hacked Arduino IDE that strips off those ‘#line’ directives and debugging the main sketch file works – this is ok for me for now.