ISP programming the bootloader, wrong order

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use an ISP  programmer and an atmega without external crystal
2. Try to program the atmega using make ..._isp

What is the expected output? What do you see instead?
Because the Makefile sets fuses first (for an external crystal) avrdude
will not be able to upload the bootlader any more.

What version of the Arduino software are you using? On what operating
system?  Which Arduino board are you using?
SVN (read-only), the atmega is not on any board yet.

Please provide any additional information below.
When the lines for uploading the firmware and setting the fuses in the
makefile would be switched this problem will not occur and thus the atmega
bootloader will be uploadable. This change should not have any impact on
systems that do have an external crystal.

Original issue reported on code.google.com by d.engelb...@gmail.com on 7 Jan 2010 at 9:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm not sure I understand.  The bootloader (and associated fuses) are intended 
for a particular board, and thus 
(typically) for an external crystal.  If you want to burn the bootloader to a 
different hardware setup, you may 
need to modify the makefile.

Original comment by dmel...@gmail.com on 8 Jan 2010 at 8:51

• Changed state: Invalid

[GoogleCodeExporter]

That is not the problem, i wish to flash the bootloader onto the AVR before it 
is
inserted into a system that has no ISP port. The programmer i'm using has no 
crystal
for the device that will be programmed. If the fuses are set before the 
bootloader is
flashed the device will therefore be dead in the water. By simply switching the
flashing order, i.e. flash the bootloader first and set the fuses afterwards 
this
problem would not occur.

Original comment by d.engelb...@gmail.com on 8 Jan 2010 at 8:59