Field Updates

Hello Everyone…

I’m starting to think about how we are going to handle field updates…
We are using a PC104+ x86 Architecture with a 192MB DOC.
Our QNX OS (v6.1) Image is roughly 64MB…

I was thinking of having the boot process that looks for a presence of
a update file (.tar.gz or image) that will blow away one of two partitions
and overwrite it with the new OS and software… If the update fails
it can somehow revert to booting the last known good partition…

Does anyone have any field update/boot strategies they would like to share?

Thanks,
Brendan

brendan@storagequest.com sed in <apuu7v$c0j$1@inn.qnx.com>

I was thinking of having the boot process that looks for a presence of
a update file (.tar.gz or image) that will blow away one of two partitions
and overwrite it with the new OS and software… If the update fails
it can somehow revert to booting the last known good partition…

Standard “diskboot” renames /boot/fs/*.qf0 to *.qfs and uses it if found,
but I don’t think it’s documented, recommended or standard.
You won’t be using “diskboot” for embedded solution anyway.

kabe