I spent the good part of a day attempting to get a raw AVR cross platform dev environment up and running. It was a challenge to say the least. Your best bet is to do the following:
1) read tuxgraphics.org install instructions here the only thing I added was c++ support and dwarf2
2) I used the latest releases of all three primary items (binutils, gcc, avr-libc) and they seem to hook up okay
3) DO use the paths that the tuxgraphics site specifies.
4) DO create a sub directory in the download directories from your Tar for binutils and gcc to config, make and make install
5) DON’t create a sub directory in the download directory for avr-libc. For some reason the config utility gets confused and the config.log sends you off into lots of red herring directions. I spent the good part of a day in this spot.
6) The avrdude problems. Yes, this did not go as listed in texgraphics. the config command is suppose to discover things you are missing but it does a very poor job of it. In my case I was missing yacc and flex. Finding the right yacc (cause there are more then one) was a bit of a challenge but some web searching found that I needed to install ‘bison’. I got a bit further but config didn’t help. Make came back and was missing some tool which with the error “[lexer.c] Error 1 “after another search on the web I discovered was supplied by ‘flex’ After installing ‘flex’ all was well.
As you can see, it can be a challenge working with the latest releases of AVR tools.
With any luck, you will have an environment ready to test a hello world program and not have burned up a day in the process!
Post a Comment