Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

This Page is under Development

Introduction

Briefly describe in general terms the system/application and the purpose for which it is intended, written in non-technical terminology. Consider including a high-level architecture diagram for the system. The description should include, but is not limited to, the following:

  • Key features or major functions/use cases performed by the system/application
  • Architecture of the system in non-technical terms (e.g., client server, Web-based, etc.)
  • System environment or special conditions

Environment Setup

  • Set-up Considerations

...

     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


sd-card size requisite

It is must to have minimal size of 8GB SD-Card for Firmware upgrade support

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

Ex:

$ sudo dd if=rdk-generic-hybrid-thunder-image_default_20200228064726.rootfs.rpi-sdimg of=/dev/sdb bs=4M


The SD card is 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

Upon booting the image, firmwareControl plugin will be disabled

Image Added

Plugin needs to be enabled before proceeding with firmware update.

 Image Added

  • 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

...