Page History

...

1. Communicate with XCONF server and get the response.
2. Processing of XCONF response and extract the firmware image details.
3. Download and flash PCI image from the SSR server to device flash memory.
4. Download and flash PDRI image from the SSR server to device flash memory.
5. Download and flash peripheral image from the SSR server to device flash memory.
6. retry download if download fail other than image not found on server error.
7. Trigger RDM Application.
8. Download cert bundle.
9. Support state red recovery download if the download is fail due to invalid certificate.
10. Support incremental download. This feature needs to be enable using "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.IncrementalCDL.Enable" RFC
11. Support Throttle download based on download speed mentioned. This feature needs to be enable using "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.SWDLSpLimit.Enable" RFC
12. Support codebig download. This is use if the device is not in comcast network.

Low Level Design Flow From Start To End

1. In case of X1 device this This module is trigger by system service called swupdate.service and in case of TV this module is trigger by Maintenance Manager. And the trigger time is during boot up and maintenance window time and App trigger.
2. In case of non-RDKE swupdate.service or maintenance manager is calling "swupdate_utils.sh". Then swupdate_utils.sh will call "rdkvfwupgrader" if the RDK Firmware RFC is true else script based download will start. 
3. In case of RDK-E maintenance manager is calling rdkvfwupdater using system call.
4. Once the rdkvfwupgradr rdkvfwupgrader start it gets all device info like MAC, partner id, current running image, pdri image, peripheral image etc and create XCONF query request. Below is the sample XCONF query request.

   eStbMac=D8:3A:DD:0A:43:71&firmwareVersion=lib32-middleware-test-image-RPI4-20251118074027&env=dev&model=RPI4&manufacturer=RaspberryPi&partnerId=community&activationInProgress=false&osClass=Not Available&accountId=1234&serial=10000000e33bf0d4&localtime=Wed Nov 26 13:44:09 UTC 2025&dlCertBundle=&rdmCatalogueVersion=&timezone=Asia/Calcutta&capabilities=rebootDecoupled&capabilities=RCDL&capabilities=supportsFullHttpUrl

5. Once the query request is formed then this module send the request to XCONF server and get the response. This response is in json format.

   { "firmwareDownloadProtocol":"http", "firmwareFilename":"lib32-application-test-image-RPI4-raspberrypi4-64-rdke-feature-RDKECOREMW-863-OTA.wic.tar.gz", "firmwareLocation":"https://tools.rdkcentral.com:8443/images/", "firmwareVersion":"lib32-application-test-image-RPI4-raspberrypi4-64-rdke-feature-RDKECOREMW-863-OTA.wic.tar.gz", "mandatoryUpdate":false, "rebootImmediately":false }

6. Once the XCONF response received then it processes the response and add to the data structure for future use.
7. Then this module does the image validation if image is invalid then this module is exit with error message.
8. Once the image validation pass then it goes for PCI download. If the download fail then it has 3 times retry before make download status fail. If the download completed successfully then this image is flashed to the flash memory. Before image download start this module will check if any chunk of the image already present if it present then download start from where it left last time.
9. If the download is failed due to certificate validation error, then state red recovery download will trigger. This is a kind of recovery server which is use static certificate to download image.
10. If no failure during download and download completed successfully then this image is flashed to flash memory. Before flashing the image sign verification happen.
11. Same above step 7 to 10 repeat for PDRI image and peripheral image.
12. Once the download completed the status of the download is send to maintenance manager and some other service using IARM event.

...