Created Mon, 06 Jun 2011 17:16:41 +0000 by ursaminor
Mon, 06 Jun 2011 17:16:41 +0000
alright, let me start by saying there is a serious lack of documentation. I'm running debian (squeeze) amd64 and this has been annoying enough just to rebuild the compiler, figuring out dependency after dependency one at a time.
now that my "sketches" compiles, i can't upload them to the uno32 because of the avrdude.conf file. i'm frustrated and have no clue what to modify after looking at the file.
my error: /avrdude.conf:320 unrecognized character: "a"
this would be the line where it says:
type = arduino;
i'm really not sure what to do in this case, i desperately need some help, the regular arduino how-tos are just not cutting it!
thanks to everyone in advanced,
Mon, 06 Jun 2011 22:52:47 +0000
I'm definitely sorry for the issue you you're havin, it's the reason I've not done a 64 bit build for Linux yet. I had found the issue and filed a bug. https://github.com/chipKIT32/chipKIT32-MAX/issues/45
What I think needs to happen is the version I'm using in the build is the incorrect version avrdude 64bit, and it should be removed from the package. Then the avrdude 64bit 5.10 package should be used for uploading.
Wed, 08 Jun 2011 04:08:25 +0000
thanks for replying ricklon!
I'm about to try compiling the 5.10 version of avrdude and i just copied some of the added lines from the config file as i've noticed that there were definitely no pic lines in the original. i'll keep all my speculations about it and try to debug as much as i can. i'll let you know if it works,
Sat, 11 Jun 2011 02:30:05 +0000
alright, so i've played around with it a little more, not as much as i'd like to, currently on vacation with the g/f
anyways, i'm wondering if you made any changes to the source itself and not just the avrdude.conf. i'm still running into quite a few errors, and i'd really like to weed out a whole tree of unnecessary routes, thanks again.
Sat, 11 Jun 2011 03:37:41 +0000
I'm using the avrdude 5.10 from the standard Ubuntu 32 bit distribution. So it's compiled according to that process. No custom compiling is needed.