I can compile it on my Linux box and the next step is 'make program' to send the .hex file to my Arduino from the command line. Now because I'm not using the standard dev tools, I am afraid I will kill the standard bootloader with uploading the .hex file. If Avrsh isn't what I was looking for I want to be able to use my Arduino in the 'normal' way.
Is my fear of killing the bootloader by programming Avrsh from the command line realistic? Can I safely upload and reuse my Arduino if I change my mind? I have no ICSP AVR tools.
johnwasser:
If you have a second Arduino you can use it to re-load the bootloader if it gets damaged by the process.
No I haven't, but I like the concept. Any smart keywords to Google for?
johnwasser:
I looked at the makefile and it looks like it doesn't do a Chip Erase or change the flag/lock bytes so it should be safe for your bootloader.
Ah that sounds good!
Just for me to learn a bit more from this, are these simple keywords I can check for myself too in Makefiles or are there pitfalls and do I need a lot of experience?
Also: optiLoader is a sketch that contains several versions of the optiboot bootloader (like on the UNO) which will program a fresh bootloader onto another Arduino without needing a PC.
jippie:
johnwasser:
I looked at the makefile and it looks like it doesn't do a Chip Erase or change the flag/lock bytes so it should be safe for your bootloader.
Ah that sounds good!
Just for me to learn a bit more from this, are these simple keywords I can check for myself too in Makefiles or are there pitfalls and do I need a lot of experience?
It's not very easy to see. What you are looking for is the 'avrdude' command line options for Chip Erase (-e) or fuse setting (-U efuse, hfuse, lfuse, lock). If none appear it is likely that the makefile is NOT asking avrdude to do anything but write the application (non-boot) FLASH.