powerfail safe env save
Hallo,
as long time u-boot user I have several projects where we have a dual dataflash "sector" in wich we store our env variables. And dual so we always have or the correct old version or the correct new version even if there is a power fail during saveenv.
Is powerfail robust env writing also available in barebox. Or what would be the barebox equifelant of a number of config variables?
Any hints and tips are welcome.
TIA,
Erwin
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Hi Erwin,
Quoted 9 lines · Erwin Rol
Hallo,
as long time u-boot user I have several projects where we have a dual dataflash "sector" in wich we store our env variables. And dual so we always have or the correct old version or the correct new version even if there is a power fail during saveenv.
Is powerfail robust env writing also available in barebox. Or what would be the barebox equifelant of a number of config variables?
We do not have redundant environment right now.
There have been attempts in the past, but they fell short in flexibility and/or robustness. Nowadays we normally do not use environment in products anymore, so this isn't much of an issue.
If you have flash I would consider using UBI for the environment. With atomic LEB change a robust environment could be implemented fairly easily.
Sascha
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox
Hallo Sascha,
Quoted 10 lines · Sascha Hauer
Hi Erwin,
Quoted 7 lines · Erwin Rol
Hallo,
as long time u-boot user I have several projects where we have a dual dataflash "sector" in wich we store our env variables. And dual so we always have or the correct old version or the correct new version even if there is a power fail during saveenv.
Quoted 8 lines
Quoted 2 lines
Is powerfail robust env writing also available in barebox. Or what would be the barebox equifelant of a number of config variables?
We do not have redundant environment right now.
There have been attempts in the past, but they fell short in flexibility and/or robustness. Nowadays we normally do not use environment in products anymore, so this isn't much of an issue.
So what do you use? Some sort of configuration (mac addresses, serial numbers, etc.) will still be needed, or ?
Quoted 4 lines
If you have flash I would consider using UBI for the environment. With atomic LEB change a robust environment could be implemented fairly easily.
It is a phycore imx6 module with NAND, so that should be possible. But I rather stay as close by "mainline" as possible, so I would rather use what ever feature Barebox hhas to offer out of the box.
What I have in U-boot is that we have 2 kernels (and rootfs) and after an update I write in the uboot env which kernel/rootfs is active. This is something that happens in the field and so the writing to the uboot env must be so robuste that the system will not be bricked.
What would be the equivalent of such a setup in Barebox ?
- Erwin
_______________________________________________
barebox mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
Quoted 34 lines · Erwin Rol
Hallo Sascha,
Quoted 10 lines · Sascha Hauer
Hi Erwin,
Quoted 7 lines · Erwin Rol
Hallo,
as long time u-boot user I have several projects where we have a dual dataflash "sector" in wich we store our env variables. And dual so we always have or the correct old version or the correct new version even if there is a power fail during saveenv.
Quoted 8 lines
Quoted 2 lines
Is powerfail robust env writing also available in barebox. Or what would be the barebox equifelant of a number of config variables?
We do not have redundant environment right now.
There have been attempts in the past, but they fell short in flexibility and/or robustness. Nowadays we normally do not use environment in products anymore, so this isn't much of an issue.
So what do you use? Some sort of configuration (mac addresses, serial numbers, etc.) will still be needed, or ?
Quoted 4 lines
If you have flash I would consider using UBI for the environment. With atomic LEB change a robust environment could be implemented fairly easily.
It is a phycore imx6 module with NAND, so that should be possible. But I rather stay as close by "mainline" as possible, so I would rather use what ever feature Barebox hhas to offer out of the box.
Quoted 6 lines
What I have in U-boot is that we have 2 kernels (and rootfs) and after an update I write in the uboot env which kernel/rootfs is active. This is something that happens in the field and so the writing to the uboot env must be so robuste that the system will not be bricked.
What would be the equivalent of such a setup in Barebox ?
We use the state frameowork and bootchooser for this task, see:
https://barebox.org/doc/latest/user/state.html
https://www.barebox.org/doc/latest/devicetree/bindings/barebox/barebox,state.html
https://barebox.org/doc/latest/user/bootchooser.html?highlight=bootchooser
Sascha
Signature · 9 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list [email protected] http://lists.infradead.org/mailman/listinfo/barebox