RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
The build procedure for broadband are as follows:
sd-card size requisite
It is must to have minimal size of 8GB SD-Card for Firmware upgrade support
Generated image has to be flashed to an SD card using this command in local PC:
|
Ex:
|
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
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
md5sum checksum creation
md5sum "<imagefile_name>.rootfs.rpi-sdimg" > imagefile_name.txt
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
If firmware upgrade is intended for multi-boot, it is necessary to have partizion size matching to RDKB image size ( especially rootfs ).
To make compatible, size of RDKB rootfs partition should be increased to 2 GB ( 2098 MB) from 300MB default
This resize can be achieved using gpartedui tool which should be available in host pc
gparted tool Install and usage
sudo apt-get install gparted
https://gparted.org/display-doc.php%3Fname%3Dmoving-space-between-partitions
Please resize the rootfs partition to 2098 MB or 2GB (/dev/sdb1) accordingly from below procedure as captured in various stages
2. Select the rootfs partition of format ext3 for resize/move option
3. Resize the rootfs partition by giving new size image to 2098 MiB
4. After resize , position stands as below
5.After modifying size, "Apply all operations" using tick symbol in UI which displays icon as below
6. After giving "Apply icon" position stands as below
7. After resizing is completed
8. After applying close size increased to 2 GB can be seen
Using the below command to re-start the firmware service.
systemctl restart swupdate.service |
---|
Firmware logs generation path.
cat /rdklogs/logs/swupdate.log |
---|
Please follow the below procedure in xconf server for placing new firmware for upgrade to specific device and model ( RPI in this case ) as a reference:
Create the Firmware Configuration by providing Firmware Description, File name as Image name to be downloaded from Xconf server, and version is the same image name without the extension (.rootfs.rpi-sdimg) and select Model(ARMV7) form the listed Models
Create MAC rule by providing rule name, Build condition is eStbMac, choose the option IN_LIST and for next field, select the MAC list created for RPi board, verify that based on the MAC list selection, Firmware Config will be automatically displayed under Action section.
Server Set-up :
XCONF side :
1.Select Download Location filter under the firmware tab in XCONF UI
2.click the edit button
3.Enter the "Location (FQDN)" field is local/Public http server (fully qualified domain name ) (ex : www.myfirmware.com)
4.Enter the "Location (full URL)" field is full location path of local/Public http server (ex : http://www.myfirmware.com)
5.Unclick the check box of Never use HTTP
6. Removed the model name from Rogue Models.
7.Removed the firmware version (If it's not updated earlier, please ignore this step).
8. click the save button.
RPI Target :
9.In DUT, please edit the following file with below format,If it's local http server
i) Open the /etc/hosts
ii) Add your local http server ip with DNS ( Ex : 192.168.0.128 www.myfirmware.com)
iii) Save the file.
Note : Every reboot, You need to add the above three steps if it's local http server.
Verify that XConf Server configuration displays the Json response from the mentioned URL:
Using the below url to view the JSON Format result of http protocol ,
http://35.155.171.121:9092//xconf/swu/stb?eStbMac=<RPI MAC ADDRESS>&model=<model_name>&capabilities=RCDL&capabilities=supportsFullHttpUrl
1. Select Download Location filter under the firmware tab in XCONF UI
2. Click the edit button
3. Added the model name under the Rogue Model .
4. Click the save button.
Verify that XConf Server configuration displays the Json response from the mentioned URL:
Using the below url to view the JSON Format result of http protocol ,
http://35.155.171.121:9092//xconf/swu/stb?eStbMac=<RPI MAC ADDRESS>&model=<model_name>&capabilities=RCDL&capabilities=supportsFullHttpUrl
Verify that image file and its respective md5 checksum file is present in the http folder:
keerthana@keerthana-INVALID:/var/www/html$ ls
rdkb-generic-broadband-image_default_20200529140558.rootfs.rpi-sdimg
folder rdkb-generic-broadband-image_default_20200529140558.txt
Please find the summary on firmware upgrade explained above
Note : 1. RPI will go for reboot while booting for the first time, since two more partition needs to be created which requires reboot. Depends on the image present in xconf and RPI, further reboot will happen for upgrade. Please refer to design (RDKB RPI Firmware Upgrade with support of HTTP protocol - Design - 2020 M6) for how firmware upgrade works with bank switching
2. SD card should be zero filled formatted before starting the firmware upgrade procedure. DriveWipe software is used for this. Please refer the you-tube video link for the SD card full format process.
3. If the user wants to view swupdate.log file then follow below steps:
a) Disable log rotation feature - This wipes out the log file if size exceeds after 1min
For B image command - systemctl disable rdkbLogMonitor
b) Reboot the box - This will make swupdate.service restart and user can start getting swupdate.log for B image
4. Broadband(size 292MB) image takes roughly 20 min time from Cloud server(Xconf).
5. Minimum extended partition should be 1GB, to verify firmware feature.