mirror of
https://github.com/arduino/Arduino.git
synced 2024-12-10 21:24:12 +01:00
6f7687b0f9
http://code.google.com/p/optiboot/issues/detail?id=33 Fix high-value watchdog timeouts on ATmega8 http://code.google.com/p/optiboot/issues/detail?id=38 Change "start app on bad commands" code to start the app via the watchdog timer, so that the app is always started with the chip in fully reset state. http://code.google.com/p/optiboot/issues/detail?id=37 |
||
---|---|---|
.. | ||
boot.h | ||
makeall | ||
Makefile | ||
omake | ||
omake.bat | ||
optiboot_atmega328_pro_8MHz.hex | ||
optiboot_atmega328_pro_8MHz.lst | ||
optiboot_atmega328.hex | ||
optiboot_atmega328.lst | ||
optiboot_diecimila.hex | ||
optiboot_diecimila.lst | ||
optiboot_lilypad_resonator.hex | ||
optiboot_lilypad_resonator.lst | ||
optiboot_lilypad.hex | ||
optiboot_lilypad.lst | ||
optiboot_luminet.hex | ||
optiboot_luminet.lst | ||
optiboot_pro_8MHz.hex | ||
optiboot_pro_8MHz.lst | ||
optiboot_pro_16MHz.hex | ||
optiboot_pro_16MHz.lst | ||
optiboot_pro_20mhz.hex | ||
optiboot_pro_20mhz.lst | ||
optiboot.c | ||
pin_defs.h | ||
README.TXT | ||
stk500.h |
This directory contains the Optiboot small bootloader for AVR microcontrollers, somewhat modified specifically for the Arduino environment. Optiboot is more fully described here: http://code.google.com/p/optiboot/ and is the work of Peter Knight (aka Cathedrow), building on work of Jason P Kyle, Spiff, and Ladyada. Arduino-specific modification are by Bill Westfield (aka WestfW) Arduino-specific issues are tracked as part of the Arduino project at http://code.google.com/p/arduino ------------------------------------------------------------ Building optiboot for Arduino. Production builds of optiboot for Arduino are done on a Mac in "unix mode" using CrossPack-AVR-20100115. CrossPack tracks WINAVR (for windows), which is just a package of avr-gcc and related utilities, so similar builds should work on Windows or Linux systems. One of the Arduino-specific changes is modifications to the makefile to allow building optiboot using only the tools installed as part of the Arduino environment, or the Arduino source development tree. All three build procedures should yield identical binaries (.hex files) (although this may change if compiler versions drift apart between CrossPack and the Arduino IDE.) Building optiboot in the arduino IDE install. Work in the .../hardware/arduino/bootloaders/optiboot/ and use the "omake <targets>" command, which just generates a command that uses the arduino-included "make" utility with a command like: make OS=windows ENV=arduino <targets> or make OS=macosx ENV=arduino <targets> On windows, this assumes you're using the windows command shell. If you're using a cygwin or mingw shell, or have one of those in your path, the build will probably break due to slash vs backslash issues. On a Mac, if you have the developer tools installed, you can use the Apple-supplied version of make. The makefile uses relative paths ("../../../tools/" and such) to find the programs it needs, so you need to work in the existing optiboot directory (or something created at the same "level") for it to work. Building optiboot in the arduino source development install. In this case, there is no special shell script, and you're assumed to have "make" installed somewhere in your path. Build the Arduino source ("ant build") to unpack the tools into the expected directory. Work in Arduino/hardware/arduino/bootloaders/optiboot and use make OS=windows ENV=arduinodev <targets> or make OS=macosx ENV=arduinodev <targets>