Dear Robert,
In message alpine.LFD.2.20.1607231318540.16761@localhost.localdomain you wrote:
so this tells me that there's not a whole lot of that feature being used, so i won't spend much time on it.
Right, it is only a last resort when you cannot find any better place to storeit (in a hardware register that survives resets).
also, just to confirm, the "upgrade_available" variable is used *exclusively* for the case of bootcount in the environment and nowhere else, correct? so, again, if i'm not using the environment, i don't care about it.
Right. It is only needed to reduce the number of writes to the environment.
now, i can see where one wants to reset "bootcount" to zero once you boot successfully, but why would you also set "upgrade_available" to zero? don't you want to keep using that feature when you boot in the future?
--> Heiko ?
Best regards,
Wolfgang Denk