RDKV4.0 Firmware Upgrade - User Manual

Introduction

     This document describes the firmware update of RPI board using FirmwareControl plugin.Plugin can be enabled via controller UI once image is booted. Based on the request given to board, tarred firmware image is downloaded to RPI board from the given HTTP server and the image is updated accordingly.

Environment Setup

 The build procedure is as follows:

•  repo init -u https://code.rdkcentral.com/r/manifests -m rdkv-asp-nosrc.xml -b thunder-next
•  repo sync -j4 --no-clone-bundle
•  source meta-cmf-raspberrypi/setup-environment (select option raspberrypi-rdk-hybrid-thunder.conf)
•  bitbake rdk-generic-hybrid-thunder-image

Flashing the image

   Image is flashed to SD card before inserting to RPI board.   

Command to flash the image

    Generated image has to be flashed to an SD card using this command in local PC:

$ sudo dd if=<path to ImageName.rpi-sdimg> of=<path to SD card space> bs=4M

The SD card is then inserted to the Raspberry Pi board and booted to check for containers created.

The Raspberry Pi board is connected to the PC via a USB to serial converter and the logs can be checked in console or can be connected via HDMI cable to a TV and logs will be shown in the terminal

Enabling the FirmwareControl Plugin:

   FirmwareControl plugin is enabled or disabled via Controller UI. Controller UI is launched using browser via http://<board ip>

   Ex: http://192.168.2.20

Upon booting the image, firmwareControl plugin will be disabled

Plugin needs to be enabled before proceeding with firmware update.

• RPi - Board :

  Flash the image supported for FirmwareControl plugin feature in the RPI board and verify the 2 partitions(ex. mmcblk0p1, mmcblk0p2) present under dev folder (use command fdisk -l)

  Execute curl request for firmware update. One more memory partition is created and device auto reboots.

  Once device boots up verify there are 3 partitions in /dev (ex. mmcblk0p1, mmcblk0p2, mmcblk0p3).

  Execute curl request for firmware update for second time.

  Image tar file will be downloaded to a file in /tmp folder (ex. ImageTemp). Verify image is downloaded to /tmp

  Reboot RPI board once firmware update process is completed manually using reboot -f command.

  Once board boots up verify the current image version ( cat /version.txt)

   Verify the version of booted image which shows the downloaded image version

  Conclusion

  Please find the summary on firmware upgrade explained above

• User Access Considerations

<Briefly describe and graphically depict as appropriate the equipment, communications, and network configuration of the system in a way that a non-technical user can understand>

• Accessing the System

<Provide detailed information and describe the procedures necessary to access the system. If applicable, include how to get a user ID and log on to the system, as well as the actions a user must take to change and/or reset a password.>

• System Work Flow

<Describe how system flow is happening mentioning checkpoints which can be verified during flow to ensure system is working as expected>

• Exiting the System

<Mention the validation artifacts that are essential to ensure the functionality is working as expected. Also any limitation while closing the validation process>

Executing System

Describe the specific system function or feature in detail and depict graphically by including screen prints and descriptive narrative as appropriate. Ensure each screen print is captioned and has an associated tag providing appropriate alternative text

Follow the above for sub feature / use cases

Troubleshooting

• Error Messages

<Identify the error messages that a user may receive and the likely cause(s) and/or possible corrective actions for the error>

• Special Considerations

<If applicable, describe any special circumstances, actions, exceptions, etc., that should be considered for troubleshooting.>

Support