Page History

...

Introduction

      This document covers the design of FirmwareControl plugin  for RPI board. 

Limitations

1.           RPI box will reboot twice for Firmware upgrade only during first time, after booted for first time. First reboot creates two more partition if its not available and second reboot activates the new image. 
2.     User has to reboot the box manually after firmware update is completed. Auto reboot after image update is not handled currently.

Design Approach

       Considering the  current requirement, the design approach followed for FirmwareControl plugin is as follows.

...

    During installation,  new directory is created in active memory bank and is mounted to passive bank. the downloaded tar image is untarred to the mounted directory. From the untarred image, kernal and rootfs data is extracted and is loop mounted to  temporary locations in passive memory bank.  The extracted kernal data is copied to memory partition1 (mmcblk0p1) and the existing data is copied to a backup folder.  rootfs is mounted to passive memory bank. cmdline.txt is modified for activating passive memory bank and active memory bank to passive. Device is then rebooted for activating the new image.

• Sequence diagram

Future Enhancements

   1.  Validate requested firmware version with currently implemented firmware version. Firmware upgrade happens only if the versions are different.

...