BitBurner requirements - AVRdude
BitBurner AVR Programmer, a full and complete AVRdude GUI for Windows.
Status: Beta
Brought to you by:
prickle
Menu
▾
▴
*Note: As of version 0.1.0 WinAVR is no longer required. An up-to-date version of AVRdude.exe (5.11.1) is now being shipped in the BitBurner installer. Instructions below are for BitBurner v0.0.5 or earlier only.
How to get AVRdude and make BitBurner work with it.
WinAVR contains a precompiled windows binary of AVRdude ready to go. This is the recommended installation as BitBurner can automatically detect and use WinAVR when BitBurner is first installed.
On a fresh setup, it works best to install WinAVR before BitBurner. Detection works by examining the registry to find WinAVR's installation directory and testing for the AVRdude executable therein.
To re-enable autodetection, for instance if WinAVR is installed after BitBurner or WinAVR is moved, ensure the location of the executable as specified in BitBurner's options is blank (empty). Then quit out completely and restart BitBurner to run the detection.
If AVRdude is installed stand-alone the location of the executable needs to be specified in BitBurner's options. BitBurner will try to verify AVRdude's authenticity by requesting it's version.
BitBurner was developed and tested using AVRdude Version 5.10, as provided by WinAVR-20100110. Other versions have not been tested at this stage.
Last edit: Nick Metcalfe 2013-12-01
for now i can confirm working with avrdude5.11 +patch7610 +usbasp + attiny26
BitBurner as of v 0.1.0 no longer has any external requirements beyond the .NET CLR runtime which most of you have already (and is downloaded by the installer if you don't). No special procedures are required to get BitBurner up and running.
BitBurner now includes the latest AVRdude 5 binary and configuration (5.11.1) for the largest selection and best support of programmers and devices as well as more stable and reliable operation.
The new BitBurner will automatically detect and use the embedded AVRdude by default after installation or upgrade. It is still possible to select an alternative AVRdude.exe binary from the Settings dialog if so desired.
If the embedded AVRdude.exe is deleted detection returns to the former behavior and WinAVR will be sought. No need for this though unless new AVRdude totally breaks when old AVRdude worked fine. Should not happen..