|
Demos and Examples Instructions on how to use the demos and examples provided By selecting a demo or example name from the list below , you will access a directory listing of all the files necessary to run that test. By selecting a file name from the directory, you can view the file's code. You will then need to use the BACK button on your browser to return to either this page, or the directory listing. If you have any questions or difficulties, please e-mail webmaster@cspi.com, or call your support representative at 1-800-325-3110 ext. 1309. Following
are some of the sample programs and demos shipped with your RTS-860 system
which may be of use in your application development. Each indicated directory
has a README file containing information on running the application. Many
of the applications under the "examples" subdirectory are presented in
the RTS-860 User Manual; they are intended for the novice user. The applications
under the "demo" directory are more involved. Below are the source directories
and the features demonstrated.
When running the NFS portion of tests $MTI_DIR/examples/nfstest and $MTI_DIR/systest/part2, be sure the remote directory has global read/write permission. If test $MTI_DIR/systest/part2 is still unsuccessful at opening nfs:/remote, try creating a file called ëremoteí in that directory with permissions mode 777. Most SuperCard examples and demos can be run on any type of SuperCard by modifying the makefiles and rebuilding. Exceptions are: $MTI_DIR/examples/c2ctest
- SC4-SL(X), only The demos and examples use the configuration macros, so only the makefile environment variables CS_DEVx and CS_TYPEx, where x is the node number, need to be changed. CS_DEVx is the SuperCard Unit Number in hex (0,1,..,F for a SuperCard-2 or SuperCard-3, and 10,11..,3F for a SuperCard-4 PE). CS_TYPEx is the type of SuperCard (sc2, sc3 or sc4). Each SuperCard or PE must have a CS_DEVx and CS_TYPEx associated with it. For more information on SuperCard Unit Numbers, refer to the RTS-860 Installation Manual. The makefile environment variable CPU should reflect the type of Embedded Host (mvme147, mvme167, or mvme162). For example, if '$MTI_DIR/examples/ffttest/makefile' is currently set up for one SuperCard-2 at VME address 0xde000000 (unit number 0x0) and the MVME147 as the Embedded Host, it would look like the following. CPU
= mvme147 If you wish to build this example for a PE0 on a SuperCard-4 at VME address 0x80000000 (unit number 0x10), with the MVME167 as the Embedded Host, you would change these values in the following manner. CPU
= mvme167 Now execute the make, and ffttest is ready to run on the MVME167 with the SuperCard-4. Note that the master makefile, make_tbin, builds most of the examples and demos. You only have to update make_tbin, and not each individual makefile (see Testing the Release, above). If there are any problems installing or using this software, or if any bugs or possible enhancements are noticed, contact the CSPI Customer Support Department.
Although the information contained herein is believed to be accurate and up-to-date, CSPI assumes no responsibility for inaccuracies or omissions. |
|
Return to MultiComputer Division Home Page . E-Mail Webmaster . Copyright ©2008 CSP, Inc. . Top of Page |