Go Down

Topic: arduino.mk (new arduino makefile, works with 1.0) (Read 10 times) previous topic - next topic

tex_


olikraus

Hi

The due makefile in the u8glib project is working. It took me some time to figure out all the gcc and ld options. Also note that bossac has been patched for Arduino. The normal bossac distribution will not work.

Oliver

tex_

Hi,

sounds great, I tried it, but could not get to work so far

stuck with some enum warnings ...

can you post your Makefile?

tex

olikraus

But you have already refered to it. I just wanted to confirm that it works.

Oliver

tex_

Hi,

I was looking for a Makefile and found that one. I refered to it as a starting point because it seemed that some one figured out the new structure of the arduino 1.5.2

I thought it might help people here

I tried to get it to work for me, but so far no success, I still have problems with the gcc and ld options ... where did you fix that?


tex_

Asche ├╝ber mein Haupt


.... sorry for the confusion, the Makefile I refered to works fine, I had some problems with the filesystem



olikraus

Kein Problem.
I just checked the Makefile and it works just fine for me :-)

Oliver

pauldreik

Hi!
I tried to use the Due Makefile by olikraus but got into trouble.

Here is a trivial sketch I use to try out the Makefile:
Quote

void setup() {
  // put your setup code here, to run once:
Serial.begin(115200);
}

void loop() {
  // put your main code here, to run repeatedly:
  Serial.println("hello");
  delay(1000);
}



which works as expected in the 1.5.2 IDE, but not with the Makefile. make runs without complaints, but the arduino does not output anything on the serial port, as it does when using the IDE. I work in Ubuntu, but this should be irrelevant to the problem.
I attach the Makefile.

Thankful for help!

edam

I don't mean to be rude, but this is a bit off-topic for this thread (which is about a different Arduino makefile).  Why not start another thread about it and link to that from here?

pauldreik

#24
Apr 25, 2013, 08:04 pm Last Edit: Apr 26, 2013, 08:11 pm by pauldreik Reason: 1
I thought this was an appropriate place since the due specific Makefile is discussed here, but I will follow your advice and post in the due section instead. I hope this will not violate the cross posting policy.

edit: see http://arduino.cc/forum/index.php/topic,162959.0.html

mafro

Hey y'all, I've been trying to use the make file on OSX with one of these arduino clones - http://www.freetronics.com/pages/leostick-getting-started-guide

I edited the Arduino app's boards.txt to include the two new board profiles, but I get an exception running make. The board profile zip for the Leostick has a "bootloaders" dir and a "cores" dir that I need to somehow include.

Can I use the LIBRARYPATH variable for this?

My current Makefile:
Code: [Select]
BOARD := leostick
include ~/Development/Arduino/arduino.mk

edam

Hey y'all, I've been trying to use the make file on OSX with one of these arduino clones - http://www.freetronics.com/pages/leostick-getting-started-guide


Cool.  They look quite similar to the Minimus USBs. I'd never considered trying to get the Arduino library to work on them, though.

Quote
I edited the Arduino app's boards.txt to include the two new board profiles, but I get an exception running make. The board profile zip for the Leostick has a "bootloaders" dir and a "cores" dir that I need to somehow include.


According to the instructions on the page you linked to, you're supposed to unzip the zip-file somewhere and then tell the IDE to use that instead of its own library directory.  I think, for the makefile, just changing the ARDUINODIR parameter to the path of wherever you've unzipped the zip-file will work.

The zip-file contains its own boards.txt, which has a profile for leostick and leostickv2.  But, unless I'm wrong, I think it has some errors.  There are two problems:

   1) For version 1 LeoSticks, "leostick.bootloader.path=diskloader" tells the IDE/makefile to look in "bootloaders/diskloader", which doesn't exist.  I don't think that "make bootloader" will work (and I would imagine uploading the bootloader from the IDE is also broken).

   2) For version 2 LeoSticks, I think "leostickv2.build.core=arduino:arduino" should be "leostickv2.build.core=arduino".  The makefile will certainly complain if this is not changed.

Finally, in order for the makefile to know to use the leostickv1 core, it has to read the leostick.build.core parameter from boards.txt.  Unfortunately, this isn't done in the last release of the makefile.  But I've just patched it, so it will now!  :o)  So you'll have to download the latest development version of the makefile for this to work.

mafro

Hey edam, thanks for the reply.

I tried the latest arduino.mk you posted and set the ARDUINODIR to the extracted board profile path. Unfortunately it didn't work!

Code: [Select]
arduino.mk:169: *** ARDUINODIR is not set correctly; arduino software not found.  Stop.

I currently have the board profile working with the IDE, but presumably it picks up the additional files as they're the special "hardware" subdirectory of the IDE's configured sketchbook directory. Perhaps setting ARDUINODIR is replacing the IDE core files with the board profile, rather than appending to the them? (*vague guess work*)

As for your other points.. I'm on the Leostick V1, so I'm okay on point 2. As for point 1, would that only be relevant if I was updating my board's bootloader?

Thanks again for your help
Matt

edam

#28
May 31, 2013, 06:10 pm Last Edit: May 31, 2013, 06:31 pm by edam Reason: 1

I currently have the board profile working with the IDE, but presumably it picks up the additional files as they're the special "hardware" subdirectory of the IDE's configured sketchbook directory. Perhaps setting ARDUINODIR is replacing the IDE core files with the board profile, rather than appending to the them? (*vague guess work*)


Hmmm.  OK, I'll have to look at adding support for this properly then, by the sounds of it.  (Edit: if you're interested, you can follow my progress here)

In the meantime, you could always copy the arduino cirectory, then copy-in the leostick files (over the top) and point ARDUINODIR at that.  Not the nicest of solutions.  :o(

Quote

As for your other points.. I'm on the Leostick V1, so I'm okay on point 2. As for point 1, would that only be relevant if I was updating my board's bootloader?


Yes, that's right.

Go Up
 

Quick Reply

With Quick-Reply you can write a post when viewing a topic without loading a new page. You can still use bulletin board code and smileys as you would in a normal post.

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.
Name:
Email:

shortcuts: alt+s submit/post or alt+p preview