diff options
| author | Heiko Schocher <hs@denx.de> | 2013-11-04 14:04:59 +0100 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2013-11-11 12:16:28 -0500 |
| commit | eda0ba38a8dfd2572089bd229a027d497c340158 (patch) | |
| tree | acb728760f98bd58b15a0d8d6b36b296ae1fbfe3 /board/Barix | |
| parent | 85b8c5c4bf80025de4632ae6c9a8a606e51508a4 (diff) | |
| download | u-boot-imx-eda0ba38a8dfd2572089bd229a027d497c340158.zip u-boot-imx-eda0ba38a8dfd2572089bd229a027d497c340158.tar.gz u-boot-imx-eda0ba38a8dfd2572089bd229a027d497c340158.tar.bz2 | |
bootcount: store bootcount var in environment
If no softreset save registers are found on the hardware
"bootcount" is stored in the environment. To prevent a
saveenv on all reboots, the environment variable
"upgrade_available" is introduced. If "upgrade_available" is
0, "bootcount" is always 0 therefore no need to save the
environment on u-boot boot, if "upgrade_available" is 1 "bootcount"
is incremented in the environment and environment gets written
on u-boot start.
So the Userspace Applikation must set the "upgrade_available"
and "bootcount" variable to 0 (for example with fw_setenv),
if a boot was successfully.
Signed-off-by: Heiko Schocher <hs@denx.de>
Diffstat (limited to 'board/Barix')
0 files changed, 0 insertions, 0 deletions