Installation on Host Linux

The SDK comes in four flavors, one for each of the "architectures". These flavors are:

1. arm-rtems-rceCA9 – target specific code for RTEMS
2. arm-linux-rceCA9 – target specific code for ArchLinux
3. i86-linux-32 – Host tools for 32-bit linux
4. i86-linux-64 – Host tools for 64-bit linux

To retrieve the SDK from SLAC, execute the following command on your host:

wget http://www.slac.stanford.edu/projects/CTK/SDK/<architecture>-sdk-<tag>.tar.gz <install_path>

tar -xzf <architecture>-sdk-<tag>.tar.gz <install_path>

This will place the current tag of the SDK into <install_path>

Then finalize the installation by executing:

<install_path>/tools/install-sdk.sh

Installation on the Target

We use tools in the host linux SDK to update the target with the OS SDK contents.  The DTM serves the update package to DPM RCEs.

You will need the following available:

1. the i86-linux SDK appropriate to your host machine
2. the arm-rtems-rceCA9 or arm-linux-rceCA9 SDK
3. The location of your target in "shelf/slot/bay/rce" space (like "katahdin/12/0/2")

OS System Files

Ensure that the target is booted into the corresponding OS:

<i86_linux_SDK_path>/bin/dsl_identify [options] location
 
<i86_linux_SDK_path>/bin/dsl_reboot [options] -t rtems -b 1 location
-- or --
<i86_linux_SDK_path>/bin/dsl_reboot [options] -t linux -b 0 location

Package the SDK into a tarball like so:

<i86_linux_SDK_path>/tools/packageSDK <SDK_path> ~/foo.tar
 

Upload the tarball to the DTM with:

<i86_linux_SDK_path>/tools/uploadSDK <dtm_location> ~/foo.tar

Now, apply the updates to your target at <location> with:

<i86_linux_SDK_path>/bin/dsl_update --ip <dtm_ip> --src /srv/nfs4/dsl --file tools/update-target.sh --id <update_id> --tmo <timeout in ms> [options] location

Wait 20-30 seconds, then verify completion status of update:

<i86_linux_SDK_path>/bin/dsl_identify [options] location

Reboot the target to apply the update:

<i86_linux_SDK_path>/bin/dsl_reboot [options] location

Troubleshooting and recovery

You've corrupted something, and you're stuck with a non-booting RCE

In most cases, it is best to use the updateFOO scripts above to recover, but if the RCE is stuck in an infinite boot loop, they won't work.

You can replace the RTEMS core libraries, the RTEMS APP libraries, as well as the bootloader and the FPGA bitstream from an SD reader.   The RTEMS APP area is most likely, since it is the only core partition writable from RTEMS.

1.  Put the SD card in a reader, and observe that devices are created for the partitions SD card in /dev/sdXN (where X is a letter, and N is [1-7]).  If you need, you can use "partprobe -s" to list them as well.
2. RTEMS APP libraries and SVTs:
   The RTEMS APP partition is /dev/sdX6.  Mount it.  Copy all files in SDK/tgt/rtemsapp/config to /mnt/config.  Sync the partition and eject.
3. RTEMS Libraries:
   The RTEMS partition is /dev/sdX5.  Mount that partition.  Copy all the files in SDK/tgt/rtems/* to that mount point.  Sync the partition and eject.
4.  Bootloader/FPGA bitstream
   The BOOT partition is /dev/sdX1.  Mount it.  Copy either boot.bin or fpga.bit from SDK/tgt/boot/dpm to that point.  Sync and eject.

This will leave you with a system which boots the core code, but your user code won't run automatically.  You'll have to reinstall your own code.