Flasher - Limit programming cycles
Flasher provides a mechanism to limit the number of programming cycles that can be performed in standalone mode with the configuration that is stored on the Flasher.
Usage
To make use of this feature, a file called Cntdown.txt needs to be placed on the Flasher. This file simply contains a decimal number (32-bit unsigned integer) that describes how many programming cycles can be performed with the current setup. This feature especially makes sense when used in combination with authorized flashing. For more information about authorized flashing, please refer to Flasher - Authorized flashing.
When using managed projects, a programming cycle limit can be configured independently for each project by placing a Cntdown.txt file in the project folder. For more information see Flasher - Project Management.
The number in the Cntdown.txt is only updated on a successful programming cycle. Programming cycles that failed, do not affect the Cntdown.txt.
LED indicator behavior
In case a Cntdown.txt is found at boot time, the "Not ready / Fail" LED of the Flasher behaves different from normal. See LED status indicators for more information.
Required Flasher hardware version
Older Flasher models do not support the limiting of programming cycles. The Flashers with the following serial number ranges do not support limiting of programming cycles:
- 1621xxxxx (Flasher ARM V2)
- 1630xxxxx (Flasher ARM V3)
- 4210xxxxx (Flasher PPC V1)
- 4110xxxxx (Flasher RX V1)
All other models / hardware versions support limiting of programming cycles.