Page History

Build procedure to generate R-Pi image with Firmware upgrade

The build procedure for broadband are as follows:

...

1. repo init -u https://code.rdkcentral.com/r/manifests -b rdk-next -m rdkv-extsrc.xml
2. repo sync -j4 --no-clone-bundle
3. source meta-cmf-raspberrypi/setup-environment (Select option raspberrypi-rdk-hybrid-westeros.conf)
4. bitbake rdk-generic-hybrid-westeros-wpe-image

Flashing the image

Command to flash the image

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

...

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

Creating checksum file

It is necessary to flash the stable image during upgrade. So checksum file has to be created for the image to be uploaded using below command

...

After checksum file is created, place this file in tftp location along with actual image file which is expected by firmware upgrade script. Without which firmware upgrade wont be allowed by scripts

Creating Multi-Boot compatible SD-CARD if RDKB is Flashed for first time

If RDKV is flashed for the first time, please ignore below procedure in current section

...

8. After applying close size increased to 2 GB can be seen

Test Setup Block Diagram for RPI RDKB/V Firmware upgrade

Setting up XCONF Server  

...

               → RPI will support only tftp protocol . No http protocol support is provided yet

Workflow

XConf Server :

1) Create Environment

2) Create Model

...

For ex. http://34.219.243.214:9092/xconf/swu/stb?eStbMac=B8:27:EB:F6:70:8C

TFTP Server:

Configure tftp server and keep the image file and reapective md5 checksum file inside tftp folder. Example given below:

...

/etc/init.d/xinetd restart

RPi - Board :

1. Flash the RDKB image supported for Firmware upgrade feature in the Rpi and verify the 2 partitions(ex. mmcblk0p1, mmcblk0p2) present under dev folder (use command ls /dev)
2. Device auto-reboots and verify there are 2 more additional partitions are created (ex. mmcblk0p3, mmcblk0p4).
3. Open /etc/include.properties file and verify the CLOUDURL parameter where XConf Server URL is configured
4. Verify the image version ( cat /version.txt) displays the flashed image version
5. Open /rdklogs/logs/swupdate.log to verify the communication from RPI board with XConf Server and the download status
6. Verify the tftp download is happening by noticing the change of file size using below command:cd /extblock/tftpimage/imagedwnldls -lh  (use this command frequently to verify the file size change)
7. Once image download completed, the Rpi board will auto reboot and come up with downloaded image
8.  Verify the version of booted image which shows the downloaded image version

Conclusion

Please find the summary on firmware upgrade explained above

...