Do you have a question? Post it now! No Registration Necessary
- Dmytro Bablinyuk
January 19, 2004, 9:35 am
Reply
Save
Print
I am working on a firmware upgrade/downgrade procedure for our
embedded board.
The board is running embedded linux, 64Mb ram and 4mb flash.
The software will be downloaded via service kit and should be deployed
on the board. The roll back mechanism in case of failure should be
provided. Basically the board will roll back to the previous software
version through the boot loader notification that upgrade was done and
restart failed, so the boot loader on next re-start will start an old
software.
There can be entire filesystem or a set of folders to upgrade.
Does somebody know any specific/standard procedures or can suggest me
anything about what the best way to do that.
Thank you for any suggestions.
embedded board.
The board is running embedded linux, 64Mb ram and 4mb flash.
The software will be downloaded via service kit and should be deployed
on the board. The roll back mechanism in case of failure should be
provided. Basically the board will roll back to the previous software
version through the boot loader notification that upgrade was done and
restart failed, so the boot loader on next re-start will start an old
software.
There can be entire filesystem or a set of folders to upgrade.
Does somebody know any specific/standard procedures or can suggest me
anything about what the best way to do that.
Thank you for any suggestions.
Site Timeline
- » neat Linux HDD cloning technique (for production)
- — Next thread in » Embedded Linux
-
- » embedded project
- — Previous thread in » Embedded Linux
-
- » Crosscompiling for ARM: reloc type R_ARM_ABS32 is not supported for PIC - ...
- — Newest thread in » Embedded Linux
-
- » Pomiar przepływu
- — The site's Newest Thread. Posted in » Electronics (Polish)
-
- » Communist Chinese Military Companies
- — The site's Last Updated Thread. Posted in » Embedded Programming
-
XML Sitemap