dll(1) [debian man page]
dll(1) brickOS Utility dll(1) NAME
dll - A user-program downloader for the RCX. SYNOPSIS
dll [options] command | {file}.lx DESCRIPTION
This manual page documents the dll user-program download command. dll is a program which is used to download user programs written for brickOS to the RCX. OPTIONS
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). The options supported by dll are: (run with no parms) Show built-in help (summary of options) -e, --execute Execute program after download. -i{0|1}, --irmode={0|1} Set IR mode (on RCX) to near(0) or far(1) -p{1-8}, --program={1-8} Download program to program-slot-number {1-8} NOTE: LegOS supports 8 program slots where the Mindstorms original firmware only supports 5. -r{hostaddress}, --rcxaddr={hostaddress} Send to RCX LNP at host address {0-15}. Default is 0. See also --node={hostaddress} -s{srcport}, --srcport={srcport} Send to RCX LNP source port {0-15} -t{ttydevice} --tty={ttydevice} Specify serial tty device where IR tower is connected. NOTE: The environment variable RCXTTY may be used in place of -tty -v, --verbose Enable verbose output COMMANDS
-d{1-8}, --delete={1-8} Delete program from program-slot-number {1-8} -n{hostaddress}, --node={hostaddress} Set RCX LNP host address to {0-15} ENVIRONMENT VARIABLES
dll will respond to the environment variable RCXTTY. This should be set to the serial device to which the IR tower is connected. Use of RCXTTY is equivalent the using the -tty command-line option. EXAMPLES
dll is a simple command to use. The following examples show most of the uses. Ex1: download demo/robots.lx to the RCX as program 0. $ dll -tty=/dev/ttyS0 demo/robots.lx $ NOTE: there is no response from dll(1) on a successful download. You can, however watch the RCX display during the download and see activ- ity. Ex2: download the demo/linetrack.lx into program-slot 7. (note we are first setting RCXTTY so we don't have to keep specifying the tty device each download). $ export RCXTTY=/dev/ttyS1 $ dll -p7 demo/linetrack.lx $ Ex3: download demo/rover.lx but we are leaving the RCX powered off (assume RCXTTY is already set). $ dll -p2 demo/rover.lx error deleting program $ NOTE: dll first deletes the existing program from the specified program slot and then downloads the new one. This error indicates that the first thing dll tried to do did not succeed. We'll leave the experiment of running dll with --verbose set as an exercise for you our reader... (This is actually a combination of progress infromation and debug ouput.) ERROR MESSAGES
Unfortunately, there is basically only one dll error message, and it applies to most possible errors, including a disconnected IR tower, an RCX that is turned off, an RCX that doesn't have brickOS, and an RCX that has brickOS and is already running a program. So, check all those things when dll fails. SEE ALSO
firmdl3(1) AUTHOR
dll was written by: Markus L. Noga. Addiitonal Contributor(s): everyone discussing LNP at LUGNET This manual page was written by Stephen M Moraco <stephen@debian.org>, for the Debian GNU/Linux system (but may be used by others). brickOS May 12, 2002 dll(1)
Check Out this Related Man Page
sane-dll(5) SANE Scanner Access Now Easy sane-dll(5) NAME
sane-dll - SANE dynamic backend loader DESCRIPTION
The sane-dll library implements a SANE (Scanner Access Now Easy) backend that provides access to an arbitrary number of other SANE back- ends. These backends may either be pre-loaded at the time the sane-dll library is built or, on systems that support dynamic loading of shared libraries, the backends may be loaded at runtime. In the latter case, adding support for a new backend simply involves installing the relevant library in /usr/lib64/sane and adding an entry to the dll.conf configuration file. In other words, no applications need to be modified or recompiled to add support for new devices. DEVICE NAMES
This backend expects device names of the form: backend:device Where backend is the name of the backend and device is the name of the device in this backend that should be addressed. If the device name does not contain a colon (:), then the entire string is treated as the device string for the default backend. The default backend is the backend listed last in the configuration file (see below) or the first pre-loaded backend (if any). CONFIGURATION
The contents of the dll.conf file is a list of backend names that may be loaded dynamically upon demand. Empty lines are ignored, also everything after a hash mark (#). A sample configuration file is shown below: net # this is a comment pnm mustek It is also possible to add a file in /etc/sane.d/dll.d that contains the list of backends to be added. Backends mentioned in a file included in this directory will be added before any backends listed in dll.conf. Files in /etc/sane.d/dll.d can be freely named. They shall follow the format conventions as apply for dll.conf. Note that backends that were pre-loaded when building this library do not have to be listed in this configuration file. That is, if a backend was preloaded, then that backend will always be present, regardless of whether it's listed in the configuration file or not. The list of preloaded backends is determined by macro PRELOADABLE_BACKENDS in file backend/Makefile.in of the SANE source code distribu- tion. After changing the value of this macro, it is necessary to reconfigure, rebuild, and reinstall SANE for the change to take effect. Aliases are defined in the config file dll.aliases. It can contain entries of the form alias SomeName SaneDeviceName alias "Some Name" SaneDeviceName hide SaneDeviceName For example: alias Epson net:somehost:epson:/dev/sgX alias "Siemens ST400" st400:/dev/sgY hide net:somehost:pnm:0 hide net:somehost:pnm:1 alias "Read from file" pnm:0 hide pnm:1 Aliased device names are automatically hidden. The idea is that users don't have to deal with complicated device names (especially for networked devices), and to hide other exported devices which might confuse them. Note that a hidden device can still be accessed if the device name is known, it just doesn't appear on the list. FILES
/etc/sane.d/dll.aliases The list of aliased or hidden backends. /etc/sane.d/dll.conf The backend configuration file (see also description of SANE_CONFIG_DIR below). /usr/lib64/sane/libsane-dll.a The static library implementing this backend. /usr/lib64/sane/libsane-dll.so The shared library implementing this backend (present on systems that support dynamic loading). ENVIRONMENT
SANE_CONFIG_DIR This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configura- tion file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explic- itly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories "tmp/config", ".", and "/etc/sane.d" being searched (in this order). SANE_DEBUG_DLL If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity. Value Description 0 print severe errors only 1 print normal errors and important messages 2 print normal messages 3 print debugging messages 4 print everything Example: export SANE_DEBUG_DLL=3 SEE ALSO
sane(7), scanimage(1), sane-"backendname"(5) AUTHOR
David Mosberger 13 Jul 2008 sane-dll(5)