Additional ways to update the system

This page describes the possible ways to update different elements of the deepsy environment system manually, in case its needed.

Updating the system from /mntDAT/

Install packages using a local repository located in /mntDAT

First it is necessary to create a yum local repository, it can be created in other linux machine different to the OBU using the following command:

createrepo <directory> [options]

Secondly, the repo should be ported to the OBU, specifically, to the /mntDAT folder. By example:

| - /mntDAT/
| - testRepo/
| - repodata
| - basicRPM-0.0.5-noop.noarch.rpm
| - testRPM-0.0.5-noop.noarch.rpm

After that it is necessary to add the repo folder to OTAUpdater service, it can be done using the following command:

dpyotaupdatertool --add deepsy rpm-md file:///mntDAT/testRepo/

Information about the added channel:

root@ep100:/mntDAT# dpyotaupdatertool -ll
repolocal :
- type: rpm
- baseurl: file:///mntDAT/testRepo/

Finally this local repository can be used the same way as a remote one.

Updating the whole RFS

For updating the whole RFs it is necessary to create a rfs.tar.bz2 file with the complete RFS system and must be stored in /mntDAT. After processing the rfs.tar.bz2, the system will automatically reboot and try to load the alternative RFS. Then the system will proceed to autoevaluate the same way than after a single rpm update.

Updating the kernel

For updating the kernel it is necessary to create a zip file with new zImage kernel image. This file should be named zImage.zip (e.g "zip zImage.zip zImage") and stored in /mntDAT. After a few seconds OTAUpdater service will process and the new kernel will be tried to be loaded in next boot. If a boot error happens with new kernel, the system will load the old kernel automatically. After a successful update, it is possible to roll the old kernel image back. It is necessary to create a file called rollbackKernel in /mntDAT (e.g. "touch /mntDAT/rollbackKernel"). After a few seconds, the file will be removed and in next boot the system will try to load the old kernel image.

Used kernel can be checked in /proc/cmdline

Updating from USB

It is possible to manage both rfs.tar.bz2 and zImage.zip from an usb drive. Files must be stores in a folder called gmvupdate in the root usb folder, i.e. /gmvupdate/rfs.tar /gmvupdate/zImage.zip OTA updater will process them same way as stored in /mntDAT

Updating the BIOS

For the equipments that have a BIOS, it is possible to update it following the next procedure:

  1. Download BIOS binary file from the artifacts page. Normally the binary name will contain the version in a format similar to "001.001.001".

  2. Create a file named "release.txt" containing the binary file name and version info. For BIOS version 001.001.001 the content of the file would be similar to this one:

    {
    "name" : "FwuImage_001.001.001.bin",
    "version" : "001.001.001"
    }

  3. Zip these 2 files together into a BIOS.zip file .
  4. Copy these files to /mntDAT/, leading to /mntDAT/BIOS.zip. BIOS update will be triggered automatically for next reboot
  5. Perform a system reboot to finish the update

In order to check the progression/result of the BIOS update, please check OTAUpdater Service logs.

Generated by   GMV