Difficult to build custom optiboot images

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Try to build a non-standard optiboot using a command like:
   make BAUD_RATE=19200 atmega8

What is the expected output? What do you see instead?
I would hope to see an atmega8 image built with the specified custom baudrate.  
However, the makefile hard-wires the baud_rate based on the target name, so you 
have to actually create a new target to get a custom baudrate.

Please use labels and text to provide additional information.
The current makefile behavior might be a good idea; it prevents optiboot hex 
files with the same name but different behaviors from floating around.  
However, it would be nice to have a "custom" target that could have parameters 
defined on the make command line (while defaulting the others.)

Original issue reported on code.google.com by wes...@gmail.com on 30 Oct 2011 at 8:28

GoogleCodeExporter commented 8 years ago

Issue 69 has been merged into this issue.

Original comment by wes...@gmail.com on 16 Aug 2012 at 10:51

GoogleCodeExporter commented 8 years ago

Fixed as part of the Makefile restructure.
http://code.google.com/p/optiboot/source/detail?r=10fc00cb5232490b5acc9414d0212f
e013343872

Original comment by wes...@gmail.com on 11 Mar 2013 at 9:23

Changed state: Fixed

dritcey / optiboot

Difficult to build custom optiboot images #48