Operation Manual

67
 Factory Image, Image 1, and Image 2: These contain version and release date
information for the corresponding firmware images. If no image is present, this field will
indicate No Image. This field also shows the required DSP image for each of the
firmware images.
 Upload Location: This field contains the location where the image upload will go. The
BRD automatically chooses a location that will not overwrite the currently running image.
 Boot Location: This field indicates which image will be used in the next boot. If an
image is successfully uploaded through Dashboard, this automatically changes to point to
that image. It can also be manually changed.
 Auto-Reboot After Update: This field controls whether or not the BRD will
automatically reboot after a successful firmware upload through Dashboard. By default,
the BRD will not reboot after an update. You can upload the firmware at any time, and
reboot later during a maintenance window.
 Available DSP Images: this field has a list of loaded DSP images.
Admin Config Files Tab
As you make configuration changes to the BRD, they are automatically persisted in non-volatile
storage. If the card is rebooted or power-cycled, it will come back in the same configuration.
In addition to automatic configuration persistency, the BRD also offers the ability to save up to 5
complete configurations, load them, and even export them. This can be used to quickly
configure it for different scenarios, or for saving configuration “checkpoints” as a complex
configuration is built. Since configurations can be exported, they can be archived outside the
card as well.
Finally, the BRD also offers 5 pre-saved configuration templates for some common scenarios.
The layout of the Admin Config Files tab is shown below.