• Created by Unknown User (panetta), last modified on Aug 14, 2014

Regression tests

After building the SDK in the development tree (see documentation FIXME), this sequence of regression tests should be run in order to prove that the SDK is ready to be tagged and pushed to the user tree.

Examine the install instructions for coherency

It is possible for the fetching/installing instructions on Confluence to become out of date WRT the individual README files in the SDKs. Each SDK's README must be compared to the instructions at https://confluence.slac.stanford.edu/display/CCI/Installing+and+Using+the+RCE+SDK

Test Install SDK from the DEV tree

On a DPM or zedboard running RTEMS

Use packageSDK and updateFOO

<i86-sdk-path>/tools/packageSDK <arm-rtems-sdk-path> foo.tar 
<i86-sdk-path>/tools/updateRCE foo.tar tinker/1/0/0
<i86-sdk-path>/tools/updateBOOTSTRAP tinker/1/0/0 <arm-rtems-sdk-path> dpm
<i86-sdk-path>/tools/updateFPGA tinker/1/0/0 <fpga.bit>
On a DPM or zedboard running Linux
<i86-sdk-path>/tools/packageSDK <arm-linux-sdk-path> bar.tar 
<i86-sdk-path>/tools/updateRCE bar.tar zed2/1/1/1
On a DTM running Linux
<i86-sdk-path>/tools/packageSDK <arm-linux-sdk-path> bar.tar 
<i86-sdk-path>/tools/updateRCE bar.tar tinker/1/4/0
Create a zedboard SD card from the SDK

Use mkrcesd to create an SD card from the SDK for use with a zedboard.

sudo mkrcesd <SDX> zed --bsigroup zed2 --mac 08:00:56:00:43:12 --sdkroot <path>

Push the SDK to USER space at this point

Fetch all SDKs from the USER tree in all possible ways

  • Using file://
git clone http://www.slac.stanford.edu/projects/CTK/SDK/<architecture>.git <install_path>
<install_path>/tools/install-sdk.sh
  • Using http:// 
    git clone file:///afs/slac/www/projects/CTK/SDK/<architecture>.git <install_path>
<install_path>/tools/install-sdk.sh
Using scp
git clone user@slachost:/afs/slac/www/projects/CTK/SDK/<architecture>.git
<install_path>/tools/install-sdk.sh
  • No labels