The RCE core software is updated over the network using the SDK and its utilities.
The updates can be uploaded to the DTM which serves the files to the RCEs over NFS.
Updates can also be served using a host based NFS exported SDK directory.
Each RCE is then commanded to download and apply the updates.
are made available to RCEs using two methods:
- DTM based NFS server
- Host based NFS server
Each RCE is externally commanded to download and apply the updates.
Note that the SDK release contains all files to be uploaded.
IMPORTANT!
Test update on a single RCE prior to updating an entire COB or shelf.
Make sure the update completes without error and the RCE successfully boots.
DTMs control the network connection for DPMs. Do not simultaneously broadcast an update to DTMs and DPMs.
If a DTM updates or reboots while a DPM is updating, the network connection will be lost, and the update will failNote that the SDK contains all files to be uploaded.
If you are supplying your own fpga.bit, you must put your file in the SDK directory.
If you do not want to update fpga.bit, remove the default fpga.bit contained in the SDK before upgrading.
arm-linux-rceCA9/tgt/boot/dpm/fpga.bit
...
Download and install the latest RCE SDK.
Choose a COB to update.
Ensure all RCEs in COB have been freshly rebooted to the target OS.
Chose an update server method.
Update Server Method 1: Upload RCE core software to DTM
First cd to the SDK directory and prepare the DTM by executing the uploadSDK command.
For example, prepare DTM ID shasta/4/0/0 for the arm-linux RCEs using network interface eth1.204:
...
Update Server Method 2: Copy SDK to an host NFS exported directory
Make sure the entire SDK directory is read accessible to the shelf network via NFS.
...
In this example, upgrade all shasta/2 DPMs using an a host NFS exported SDK on interface eth1.204:
dsl_update --ip 192.168.204.12 --src /nfsexport/project/RCE/sdk --sm shasta-sm --ifname eth1.204 shasta/2/DPMWhere 192.168.204.12 is the IP address of the NFS server on the shelf network,
...
(For SDK versions V1.10.0 and up, add this additional dsl_update argument is used to monitor the update status)
--sm <shelf_manager_ip>
(For SDK versions V1.5.0 or less, add these additional dsl_update arguments are required for server method 1)
--src /srv/nfs4/dsl --file tools/update-target.sh --tmo 4000
...
For example:
dsl_identify shasta/4/23/2 --ifname eth1.204
Slot 4 : Had Responses
RCE 3/2 : OS: LINUX IP: 192.168.204.21 ID: 0x00000000 V1.10.0
...