• Created by Unknown User (rmanoharan), last modified by Anonymous on Jun 28, 2017

Info provided in Training slides:

Refers to a disaster recovery image that is launched if the firmware image is invalid due to corruption of other reasons. When the device is running an DRI image, then it is DRI mode. If a normal firmware image is running, then it is in normal mode. 

On the other hand, RDK Components diagram in the training slides show that the DRI is provided by OEMs.


Question: 

  1.  What does the DRI image actually contain? Is it a copy of the valid firmware image that gets saved in flash after validation?
  2. What is the difference between Normal and DRI mode? Is there any procedure to switch to normal from DRI mode?

 

Thanks in advance!

 

  • No labels

3 Comments

  1. Unknown User (asingh)

    P-DRI image consists of a minimal kernel and minimal filesystem with basic ability to do the following

    1.Perform required DCM interaction to obtain firmware download configuration.

    2.  Perform a firmware upgrade.
    3. Display required graphics to indicate DRI state and update state.
    4. Support diagnostics queries and logs to allow for remote detection and monitoring of DRI state.


    The B-DRI is further stripped in functionality and support only Device Initiated Firmware Download (DIFD).

    P-DRI can be upgraded in the field, but B-DRI is burnt in to the flash and can't upgraded in the field.

  2. Unknown User (rmanoharan)

    Thanks Ajay!

  3. Unknown User (gmartinez)

    I want to understand how necessary it is that the OEM provides the DRI:

    We could have a Client Device without P/B-DRI?
    We could have a Client Device only with P-DRI?
    We could have a Client Device only with B-DRI?

     

    Thanks in advance!