External IDE

yoshi_jd · **Joined:** Mon Jul 11, 2011 3:15 am **Posts:** 78

chertu wrote:

educc wrote:

Thanks Michael!.

I take the advantage of this post to tell everybody I have written
an adapted tutorial to program the Waspmote using Eclipse.

Tutorial: http://www.eduardocc.com/EclipseWaspmot ... orial.html

I hope you find it useful!.

Edu.

Hi!

Thanks to Edu for the tutorial!

But I´ve got a problem will trying to follow it. When I do the following in step 8:

Code:

Include in your project the Waspmote core library. To do that, follow these steps:
Start the Waspmote IDE.
Open the Blink sketch (File -> Examples -> Utils -> WaspUtils_2_usingLEDs)
Compile the sketch (Sketch -> Verify/Compile)
Select: (Sketch -> Show Sketch Folder).
Go into the applet folder.
Drag core.a file into your Eclipse BlinkTemplate project to copy it in.
...

I cant´t find anywhere the core.a file. Does anyone know why or where it exactly should be?

Regards,

Aitor

Hi chertu,

The waspmote-ide core.a file can be found under the temporary directory - something similar to:

C:\Users\<user name>\AppData\Local\Temp\build5463396017256948234.tmp

Cryptoman · **Joined:** Wed Oct 05, 2011 12:05 am **Posts:** 60

yoshi_jd wrote:

Hi chertu,

The waspmote-ide core.a file can be found under the temporary directory - something similar to:

C:\Users\<user name>\AppData\Local\Temp\build5463396017256948234.tmp

That's where the binaries get generated after one "compiles" the code. Strangely enough, if you "Upload" the code, a directory called "applet" is autogenerates where your application source files are located. The "Upload" command first compiles the code and then it sends the *.hex file to the Waspmote board.

Maybe for future reference Libelium will change the IDE so that "Compile" command will also generate all the binaries in the applet folder located inside the developer's application source file folder. The above difference is quite confusing to be honest especially for new starters.

Regards...

chertu · **Joined:** Tue Jan 17, 2012 1:53 pm **Posts:** 41

Hi!

Thanks to both of you. I finally make the Eclipse work with the Waspmote. ^^

On step 8.3.7.2 I used "--function-sections -fdata-sections -Wl,--gc-sections"
instead of "--ffunction-sections -fdata-sections -Wl,--gc-sections"

Regards,

Aitor

sinnadyr · **Joined:** Wed Feb 22, 2012 1:34 pm **Posts:** 22

I am having trouble with "cannot find -lcore" and that setLED is "invalid arguments".

Any ideas of what I am doing wrong? Tried following the guide step by step like three times now...

sinnadyr · **Joined:** Wed Feb 22, 2012 1:34 pm **Posts:** 22

Some error code:

Code:

avr-g++ --cref -s -Os -o "new.elf"  ./main.o   -lcore -lm -Wl,-Map,new.map,--cref -L"\mypath\waspmote_eclipse\new" -mmcu=atmega1281
c:/winavr-20100110/bin/../lib/gcc/avr/4.3.3/../../../../avr/bin/ld.exe: cannot find -lcore
make: *** [new.elf] Error 1

libelium-dev · **Joined:** Mon Sep 28, 2009 1:06 pm **Posts:** 7501

Hello sinnadyr,

As you will now, we have not adapted Waspmotes' IDE to Eclipse, but it was another user from the Waspmote Community. That is why we are not experts on that program and cannot help you with that.

We hope other Eclipse users from the Waspmote Community can help you on this thread. Otherwise, we advise to use our normal IDE. It is for sure that you will advance faster.

Best regards

sinnadyr · **Joined:** Wed Feb 22, 2012 1:34 pm **Posts:** 22

Hi!

I have now gotten rid of the error where i cannot find the core library, just by moving from my school computer (which only uses network disks) to my laptop.

Now I only have trouble with that functions are not declared, so there is something wrong with the includes.

Code:

make all 
Invoking: Print Size
avr-size --format=avr --mcu=atmega1281 Template.elf
AVR Memory Usage
----------------
Device: atmega1281

Program:    8960 bytes (6.8% Full)
(.text + .data + .bootloader)

Data:       1001 bytes (12.2% Full)
(.data + .bss + .noinit)


Finished building: sizedummy
 

but still, many errors on "function could not be resolved."

Quote:

Otherwise, we advise to use our normal IDE. It is for sure that you will advance faster.

Unfortunately not. You IDE is encredibly slow, and the time I use for setting up Eclipse will deffinately be worth the wait. Also, with Eclipse we have access to all include-files and functions and have much better control over my application.

libelium-dev · **Joined:** Mon Sep 28, 2009 1:06 pm **Posts:** 7501

Yes, Eclipse adds some adventages, it is true. But the functionality is the same.

Please keep in mind the low speed when uploading with the Libelium's IDE is not due to the IDE, but to hardware reasons inside Waspmote. With Eclipse, the upload time will not be shorter.

Best regards

sinnadyr · **Joined:** Wed Feb 22, 2012 1:34 pm **Posts:** 22

libelium-dev wrote:

Yes, Eclipse adds some adventages, it is true. But the functionality is the same.

Please keep in mind the low speed when uploading with the Libelium's IDE is not due to the IDE, but to hardware reasons inside Waspmote. With Eclipse, the upload time will not be shorter.

Best regards

Okey, the upload time will not be shorter, but compiling will take a lot less time since your IDE includes every library there is when building. I do not need Xbee modules for blinking an LED.
Please stop the discussion of what is better than the other, I just want help with setting up Eclipse.

Cryptoman · **Joined:** Wed Oct 05, 2011 12:05 am **Posts:** 60

sinnadyr wrote:

but still, many errors on "function could not be resolved."

Hi sinnadry,

This may be quite obvious but I would like to suggest the following.

Rather than trying to compile and build your own application, have you tried building a very basic example code first to see what type of errors you get (if any)? This is to isolate your code from the equation until you resolve the source of Eclipse set up related problems. Once you get a baseline code working with Eclipse, you can then bring in your own code.

Also, the function resolution issue may be due to the linker not necessarily the compiler. So I would also look at the linker stage in the Eclipse set up including all the command line arguments and the link options etc.

Just food for thought...

Regards...