You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The RCE core software is updated over the network using the SDK and its utilities.

The updates are first uploaded to the DTM which serves the files to the RCEs over NFS.

Each RCE is then commanded to download and apply the updates from the DTM.

Note 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

To perform the upgrade:

Download and install the latest RCE SDK

Choose a COB to update

Ensure all RCEs in COB have been freshly rebooted

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 with ID shasta/4/0/0 using network interface eth1.204:

i86-linux-64/tools/uploadSDK arm-linux-rceCA9 shasta/4/4/0 eth1.204
Looking up shasta/2/4/0...
...Got it: 192.168.204.253
Uploading arm-linux-rceCA9 to shasta/4/4/0
Configuring SDK update on shasta/4/4/0

Command one or more RCEs to apply the update using the dsl_update command.

For example, upgrade RCE shasta/4/3/2 from DTM shasta/4/0/0 using interface eth1.204:

dsl_update --ip `atca_ip shasta/4/4/0 --ifname eth1.204` --src /srv/nfs4/dsl --file tools/update-target.sh --ifname eth1.204 --tmo 4000 shasta/4/2/2
Wait 60 to 90 seconds for the upgrade to complete and for the RCE to reboot.
Check RCE network connectivity using dsl_identify to ensure upgrade to V1.5.0 was successful.

For example:

dsl_identify shasta/4/2/2 --ifname eth1.204
Slot 4 : Had Responses
 RCE 2/2 : OS: LINUX IP: 192.168.204.21 ID: 0x00000000 V1.5.0
  • No labels