From 84adefa331c4159d432d22840663c38f155cd4c1 Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Fri, 20 Nov 2009 14:54:40 +0000 Subject: The R13B03 release. --- system/doc/embedded/vxworks.xml | 193 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 193 insertions(+) create mode 100644 system/doc/embedded/vxworks.xml (limited to 'system/doc/embedded/vxworks.xml') diff --git a/system/doc/embedded/vxworks.xml b/system/doc/embedded/vxworks.xml new file mode 100644 index 0000000000..52143a42e3 --- /dev/null +++ b/system/doc/embedded/vxworks.xml @@ -0,0 +1,193 @@ + + + + +
+ + 19972009 + Ericsson AB. All Rights Reserved. + + + The contents of this file are subject to the Erlang Public License, + Version 1.1, (the "License"); you may not use this file except in + compliance with the License. You should have received a copy of the + Erlang Public License along with this software. If not, it can be + retrieved online at http://www.erlang.org/. + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See + the License for the specific language governing rights and limitations + under the License. + + + + VxWorks + Patrik Winroth + + + + + 2000-10-17 + + vxworks.xml +
+

This chapter describes the OS specific parts of OTP which relate + to VxWorks. +

+ +
+ Introduction +

The Erlang/OTP distribution for VxWorks is limited to what + Switchboard requires (Switchboard is a general purpose + switching hardware developed by Ericsson). +

+

Please consult the README file, included at root level in the + installation, for latest information on the distribution. +

+
+ +
+ Memory Usage +

Memory required is 32 Mbyte. +

+
+ +
+ Disk Usage +

The disk space required is 22 Mbyte, the documentation included. +

+
+ +
+ Installation +

OTP/VxWorks is supplied in a distribution file named + .tar.gz]]>; i.e. a tar archive that is + compressed with gzip. ]]> represents the + name of the release, + e.g. otp_LXA12345_vxworks_cpu32_R42A. Assuming you are + installing to a Solaris file system, the installation is + performed by following these steps: < +

+

+ + Change to the directory where you want to install + OTP/VxWorks (]]>): ]]> + Make a directory to put OTP/VxWorks in: mkdir otp_vxworks_cpu32 (or whatever you want to call it) + Change directory to the newly created one: cd otp_vxworks_cpu32 + Copy the distribution file there from where it is located + (]]>): /.tar.gz .]]> + Unzip the distribution file: .tar.gz]]> + Untar .tar]]>: .tar]]> + Create a bin directory: mkdir bin + Copy the VxWorks Erlang/OTP start-up script to the bin directory: + cp erts-Vsn/bin/erl bin/. + Copy the example start scripts to the bin directory: + cp releases/R42A/*.boot bin/. + +

If you use VxWorks nfs mounting facility to mount the Solaris + file system, this installation may be directly used. An other + possibility is to copy the installation to a local VxWorks DOS + file system, from where it is used. +

+
+ +
+ OS Specific Functionality/Information +

There are a couple of files that are unique to the VxWorks + distribution of Erlang/OTP, these files are described here. +

+ + README - this files has some information on VxWorks + specifics that you are advised to consult. This includes the + latest information on what parts of OTP are included in the + VxWorks distribution of Erlang/OTP. If you want us to + include more parts, please contact us to discuss + this. + erts-Vsn/bin/resolv.conf - A resolver configuration EXAMPLE file. + You have to edit this file. + erts-Vsn/bin/erl - This is an EXAMPLE start script for VxWorks. + You have to edit this file to suit your needs. + erts-Vsn/bin/erl_io - One possible solution to the problem + of competing Erlang and VxWorks shell. Contains the function + 'start_erl' called by the erl script. Also contains the + function 'to_erl' to be used when connecting to the Erlang + shell from VxWorks' shell. + erts-Vsn/bin/erl_exec - Rearranges command line arguments + and starts Erlang. + erts-Vsn/bin/vxcall - Allows spawning of standard VxWorks + shell functions (which is just about any function in the + system...) from open_port/2. E.g. open_port({spawn, 'vxcall + func arg1 arg2'}, []) will cause the output that 'func arg1, + arg2' would have given in the shell to be received from the + port. + erts-Vsn/bin/rdate - Set the time from a networked host, + like the SunOS command. Nothing Erlang-specific, but nice + if you want date/0 and time/0 to give meaningful values (you + also need a TIMEZONE environment setting if GMT isn't + acceptable). For example: putenv "TIMEZONE=CET::-60:033002:102603" sets central european + time. + erts-Vsn/src - Contains source for the above files, and + additionally config.c, driver.h, preload.c and + reclaim.h. Reclaim.h defines the interface to a simple + mechanism for "resource reclamation" that is part of the + Erlang runtime system - may be useful to "port program" writers (and + possibly others). Take careful note of the caveats listed in + the file! + +
+ +
+ Starting Erlang +

Start (and restart) of the system depends on what file system + is used. To be able to start the system from a nfs mounted + file system you can use VxWorks start script facility to run a + start script similar to the example below. Note that the + Erlang/OTP start-up script is run at the end of this script. +

+ ") + +# +# Set default gateway +# +hostAdd "router-20","150.236.20.251" +routeAdd "0","router-20" + +# +# Mount /home from gandalf +# +hostAdd "gandalf","150.236.20.16" +usergroup=10 +nfsAuthUnixSet("gandalf", 452, 10, 1, &usergroup) +nfsMount("gandalf", "/export/home", "/home") + +# +# Load and run rdate.o to set correct date on the target +# +ld < /home/gandalf/tornado/wind/target/config/ads360/rdate.o +rdate("gandalf") + +# +# Setup timezone information (Central European time) +# +putenv "TIMEZONE=CET::-60:033002:102603" + +# +# Run the Erlang/OTP start script +# +cd "/home/gandalf/tornado/wind/target/erlang_cpu32_R42A/bin" + +
+ + -- cgit v1.2.3