RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
1. Firmware config can be created via Firmware - > Firmware Configs -> Create. Enter a description for this config. It will be used in the rule. Here we can define the file name and version of the image/firmware that need to be downloaded to the CPE device. The models that we defined in Common → Models section will be available here, We can select the needed models by clicking on it.
Panel | ||
---|---|---|
| ||
2. To create a firmware template, go to Firmware → Firmware templates. Enter the ID name. Select priority from the 'Priority' drop down menu. Add conditions.If you are using the existing Firmware Templates for configuration ,you can skip this step.
Panel | ||
---|---|---|
| ||
...
After we select the required template, 'Add firmware Rule' page will be displayed. Here the build conditions will be present from the 'template' that we added and in addition to that we can add additional Build Conditions also. To add firmware config , go to the 'Actions' tab and select the firmware config from 'Firmware config' drop down list.
Panel |
---|
4. The download location needs to be specified so that it can be returned in the response. Choose Firmware -> Download location filter-> Edit, where we can specify the location from where we can download the firmware. Enter the FQDN and Full http location for the firmware download server . For TFTP , we can enter the IP address and percentage. For where TFTP applies, a device will get back one of the locations below based on the percent listed for the location.
The FQDN location https://xconf.rdkcentral.com/xconf/upload/ can be used for the firmware download server.
Panel | ||
---|---|---|
| ||
a. Verification of Firmware test page.
After creating the Firmware configs and Firmware rules , go to Firmware->Test page and give a parameter that will match the one of the rule that you have created. Then matched rule will be displayed like below.
Panel | ||
---|---|---|
| ||
b. Verification via curl command
The curl command mocks the request being sent from an STB like below and sample response is also given. It can be given as a curl command or as a get request via postman or browser.
eg :
$ curl 'http://<XCONF_IP>: 19092/loguploader/getSettings?estbMacAddress=B8:27:EB:BE:D7:12’
Sample Response :
Code Block |
---|
{
"firmwareDownloadProtocol": "http",
"firmwareFilename": "rdkb-generic-broadband-image_default_20201222054544.rootfs.rpi-sdimg",
"firmwareLocation": "xconf.rdkcentral.com",
"firmwareVersion": "rdkb-generic-broadband-image_default_20201222054544",
"rebootImmediately": false
} |
CURL Command | curl 'http://<XCONF_IP>:19092/xconf/swu/stb?eStbMac=B8:27:EB:BE:D7:12&model=ARMv7&capabilities=RCDL&capabilities=supportsFullHttpUrl' |
---|---|
CPE Script (RDK-V) | /lib/rdk/ /lib/rdk/ |
CPE Service (RDK-V) | /lib/systemd/system/swupdate.service |
...