| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Some hardware programmers have LEDs, and the firmware controls them fully
without AVRDUDE having a way to influence their LED states. Other
programmers have LEDs and expect the host downloader/uploader to handle
them, for example bit-banging programmers, ftdi-based programmers or
linuxgpio programmers. For those programmers AVRDUDE provides support of
four LEDs (RDY, ERR, PGM and VFY) which can be set via corresponding
subroutines in the code for the respective -c programmer.
The RDY LED is set once the programmer is initialised and switched off when AVRDUDE exits. During reading, writing or erasing the target the PGM LED flashes with around 2.5 Hz, whilst the VFY LED comes on during -U verification of the written contents. Errors are indicated with the ERR LED.
Assuming AVRDUDE got to the point where LEDs are accessible and the RDY LED was switched on then, on exit, AVRDUDE will leave the LEDs in the following states:
| PGM | VFY | ERR | Semantics | |
| off | off | off | OK: all tasks done without errors | |
| off | off | on | Some error not related to read, write or erase | |
| on | off | on | Read, write or erase error | |
| off | on | on | Verification error but no read, write or erase error | |
| on | on | on | Verification error and read, write or erase error |
Other combinations should not show after exit.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Stefan Rueger on August 24, 2024 using texi2html 1.82.