Jantje:
katekarnage
Thanks for the nice words
katekarnage:
1.) The upload ignores build configurations and always tries to upload from the "Release" Directory no matter what build configuration is active.
I'm surprised you got it going until the upload.
I took the design decision to hard code "Release" as configuration name. Given the fact that all settings are coming from boards.txt and platform.txt I don't see the usage of more configurations and as such the configuration name is irrelevant. Can you explain your use case for having more or another configuration name?
This is partially because I'm an old C/C++ programmer and have always been doing debug/release builds and have a lot of serial-emitted output dependent on a defined DEBUG and other symbols, even though, in this case I'm obviously not needing to change optomisations or debug symbol inclusion. Also I have several projects where the same arduino board is being used in a number of slightly different circumstances with a few compiletime directives to control the created code.
Build configurations are the easiest way of handling these, with adding a few -D direcetives to the compiler EXTRAFLAGS.
As, in this case there is only defines and no other changes to the compile environment, then, if this is too hard, then don;t worry as I can always sort it through altering defines in the main project header file and recompiling like that - more of a nicity really.
Jantje:
katekarnage:
2.) The only way I've got my Leonardo to work is by setting the project preferences to the bootloader com port then doing a manual reset on upload, if I use the normal com port setting, then upload resets the board (the board led starts flashing and windows re-aquirres the bootloader port) but the process then errors saying "Leonardo upload port is not appearing after reset"
katekarnage:
3.) Currently I've not got my Due to work, compile goes fine, upload appears to work fine, but after upload the due freezes and can;t be reset, the only way to make it come back to life is to upload something from the Arduino IDE, then it will work properly - I'm still investigating this one...
I just tried due on Linux and tha works fine. Which os are you using?
Win7 64 bit with 32bit Eclipse Juno.
But...
I have done more investigation of this, I had an idea or 2, and have gone back to basics.
A simple blink program uploads and runs fine, so the basic upoloading is fine.
The problem seems to be when I attempt to use the Scheduler. This code will brick the Due from eclipse and need it to be reset with the arduino IDE:
TestSched.cpp:
// Do not remove the include below
#include "SchedTest.h"
#include <Scheduler.h>
int led = 13;
void setup() {
pinMode(led, OUTPUT);
Scheduler.startLoop(loop2);
}
void loop() {
digitalWrite(led, HIGH);
delay(1000);
}
void loop2() {
delay(1300);
digitalWrite(led, LOW);
}
TestSched.h:
// Only modify this file to include
// - function definitions (prototypes)
// - include files
// - extern variable definitions
// In the appropriate section
#ifndef SchedTest_H_
#define SchedTest_H_
#include "Arduino.h"
//add your includes for the project SchedTest here
//end of add your includes here
#ifdef __cplusplus
extern "C" {
#endif
void loop();
void loop2();
void setup();
#ifdef __cplusplus
} // extern "C"
#endif
//add your function definitions for the project SchedTest here
//Do not add code below this line
#endif /* SchedTest_H_ */
I will delve deeper into the build logs and see if I can isolate this a bit more, and check I haven;t made a galringly obvious mistake!
Thanks again for your good work!