[root@dvorkin vspd-1.11-dist]# cd /usr/local/vspd-1.11-dist/ [root@dvorkin vspd-1.11-dist]# uname -a >> ./report.txt [root@dvorkin vspd-1.11-dist]# ./install.sh /usr/local/vspd >> ./report.txt 2>> ./report.txt [root@dvorkin vspd-1.11-dist]# cat ./lib/src/Makefile >> ./report.txt [root@dvorkin vspd-1.11-dist]# cat ./lib/src/linux/* >> ./report.txt

[root@dvorkin vspd-1.11-dist]# ls /usr/local/vspd/etc/ [root@dvorkin src]# ls -1 /usr/local/vspd/etc vspd.conf /* VSPDaemon configuration file */ vspd.conf.in /* VSPDaemon configuration template */ vspd.conf.sample /* VSPDaemon configuration example */ vspm.conf /* VSPModule configuration file */

[root@dvorkin etc]# cat /usr/local/vspd/etc/vspm.conf # Virtual Serial Port module config file # Copyright (C) 2003, Tibbo Technology Inc. # ----- module section # You may use # as comment # For example if you want to set MAXDEV as default, # you have to comment the string # "MAXDEV=100" -> "#MAXDEV=100" # maximum number of devices # default MAXDEV=128 #MAXDEV=128 # major number for serial devices # set major number, if you aren't using devfs # default MAJOR0=100 MAJOR0=100 # major number for daemon devices MAJOR1=101 # debug level # 0 = no debug # 1 = simple kernel messages # 2 = development debug # 3 = development debug with # default DEBUG=1 DEBUG=0 # ----- /dev section # set DEVFS=true if you are using devfs # otherwise set DEVFS=false # set DEVFS=auto if you not sure about your devfs state # default: auto # DEVFS=auto # device files prefix # default FNAME=vsp FNAME=vsp # group name for the device files # default FGRP=root FGRP=root # access mode for the device files # default FMOD=660 FMOD=660

You don't have to edit this file - all variables are set up to correct values automatically at the installation phase. All you need to know is how to set up debug level. For VSPModule debugging you have to change “DEBUG=…” variable to the appropriate value and restart VSPModule. All messages will be sent to syslog (/var/log/messages usually). #### VSPDaemon configuration

[root@dvorkin etc]# cat /usr/local/vspd/etc/vspd.conf ...(skipped)...

Change all IPs and PORTs in vspd.conf to suitable values, in the following sections:

, =,

(Device servers should be configured to allow connections from or connect to these IP addresses) Choose connection mode for your device using the following section:

Don't forget to put device servers into the corresponding connection mode. Optionally, change packet settings:

Uncomment

string for debugging output:

and replace

by

to see hexadecimal dump of data transferred through the virtual serial ports. #### Starting/stopping/restarting There are two startup scripts installed into /etc/rc.d/init.d/ directory and started during OS boot:

[root@dvorkin etc]# ls -l /etc/rc.d/init.d/vsp* -rwxr--r-- 1 root root 2439 Dec 7 12:28 /etc/rc.d/init.d/vspm* -rwxr--r-- 1 root root 2290 Dec 7 12:28 /etc/rc.d/init.d/vspd*

and symlinks in /etc/rc.d/rc.d/vsp*. Run these scripts without parameters to see help:

[root@dvorkin etc]# /etc/rc.d/init.d/vspd Usage /etc/rc.d/init.d/vspd {start|stop|restart|reloadconf|status|extstatus} [root@dvorkin etc]# /etc/rc.d/init.d/vspm Usage /etc/rc.d/init.d/vspm {start|stop|restart|status|conf|modinfo}

You can call startup scripts from command line. Here are some examples:

[root@dvorkin etc]# /etc/rc.d/init.d/vspm start installing vspm.ko module to kernel... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspm restart removing vspm.ko module from kernel... [ OK ] installing vspm.ko module to kernel... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspm status vspm.ko module is loaded [root@dvorkin etc]# /etc/rc.d/init.d/vspm conf module name: vspm.ko module path: /usr/local/vspd/lib/ module conf: /usr/local/vspd/etc/vspm.conf insmod : /sbin/insmod rmmod : /sbin/rmmod lsmod : /sbin/lsmod modinfo : /sbin/modinfo [root@dvorkin etc]# /etc/rc.d/init.d/vspm modinfo filename: /usr/local/vspd/lib/vspm.ko description: "Virtual Serial Port driver" author: "(C) by Tibbo Technology Inc., 2004" license: "GPL" parm: major0 int, description "Major number for tty devices" parm: major1 int, description "Major number for daemon interface devices" parm: debug int, description "Debug level (0-2)" parm: maxdev int, description "Max. number of devices" [root@dvorkin etc]# /etc/rc.d/init.d/vspd start starting vspd... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspd restart stopping vspd... [ OK ] starting vspd... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspd reloadconf tell vspd to reload configuration... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspd status vspd is loaded [root@dvorkin etc]# /etc/rc.d/init.d/vspd extstatus vspd is loaded [root@dvorkin etc]# /etc/rc.d/init.d/vspd stop stopping vspd... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspd extstatus /var/run/vspd.pid not found vspd is NOT loaded

To start VSPD run /etc/rc.d/init.d/vspm followed by /etc/rc.d/init.d/vspd:

[root@dvorkin etc]# /etc/rc.d/init.d/vspm start installing vspm.ko module to kernel... [ OK ] [root@dvorkin etc]# /etc/rc.d/init.d/vspd start starting vspd... [ OK ]

After calling /etc/rc.d/init.d/vspm start check if there are device files created in /dev/:

[root@dvorkin etc]# ls -l -R /dev/vsp* /dev/vsp: total 0 crw------- 1 root root 101, 0 Jan 1 1970 vspd0 ... (skipped) ... crw------- 1 root root 101, 0 Jan 1 1970 vspd127 crw------- 1 root root 101, 0 Jan 1 1970 vsps0 ... (skipped) ... crw------- 1 root root 101, 0 Jan 1 1970 vsps127

The /dev/vsps (or /dev/vsp/vsps) device files are virtual serial ports to be used by your device control software, /dev/vspd (/dev/vsp/vspd) device files are used for internal purposes by VSPDL itself and should not be opened by third-party software. #### Error reporting during startup

[root@dvorkin etc]# uname -a >> ./report.txt [root@dvorkin etc]# /etc/rc.d/init.d/vspm start >> ./report.txt [root@dvorkin etc]# /etc/rc.d/init.d/vspd start >> ./report.txt [root@dvorkin etc]# cat /usr/local/vspd/etc/vspm.conf >> ./report.txt [root@dvorkin etc]# cat /usr/local/vspd/etc/vspd.conf >> ./report.txt [root@dvorkin etc]# tail -n 1000 /var/log/messages >> ./report.txt [root@dvorkin etc]# tail -n 1000 /usr/local/vspd/var/vspd.log >> ./report.txt [root@dvorkin etc]# tail -n 1000 /usr/local/vspd/var/dev.0.log >> ./report.txt

#### Testing/debugging Stop VSPmodule and VSPDaemon

#/etc/rc.d/init.d/vspd stop #/etc/rc.d/init.d/vspm stop

Set up debug mode: in /usr/local/vspd/etc/vspm.conf change

DEBUG=0

to

DEBUG=3

in /usr/local/vspd/etc/vspd.conf change

to

and

to

Startup VSModule:

#/etc/rc.d/init.d/vspm start

Switch to the other console window and try to send data throw virtual ports :

(1st console):#cat /dev/vsp/vsps0 (2nd console):#echo "testing - vspD" > /dev/vsp/vspd0

do you see “testing - vspD” on 1 console?

(1st console):#cat /dev/vsp/vspd0 (2nd console):#echo "testing - vspS" > /dev/vsp/vsps0

do you see “testing - vspS” on 1st console? If you don't see any output, proceed to section 3.1 Please, attach ./report.txt to your message when requesting support from Tibbo Start up VSPDaemon:

[root@dvorkin etc]# /etc/rc.d/init.d/vspd start

Check if VSPDaemon running:

[root@dvorkin etc]# ps auxw | grep "vspd" [root@dvorkin etc]# /etc/rc.d/init.d/vspd extstatus

If VSPDaemon is not running, proceed to section 3.1 Please, attach ./report.txt to your message when requesting support from Tibbo Look at the /usr/local/vspd/var/dev.0.log:

[root@dvorkin etc]# tail -f /usr/local/vspd/var/dev.0.log

Most problems (wrong IP/ports etc.) can be diagnosed by checking this log file. Make changes in /usr/local./vspd/etc/vspd.conf:

replace with

And restart VSPDaemon:

[root@dvorkin etc]# /etc/rc.d/init.d/vspd restart

Call minicom:

#minicom -o press + , choose "Serial port setup", press press , write /dev/vsp/vsps0, press , press choose "Save setup as ...", press , write "vsps0", press choose "Exit", press press +, , press

(minicom interrupted). Call minicom again:

#minicom -o vsps0

Open VSPD log in the second console window:

(console 2)#tail -f /usr/local/vspd/var/dev.0.log

you should see message: “port opened” Open telnet session in the third console window:

(console 3)#telnet 10.1.1.1 3500

where 10.1.1.1 - ip addr from

section of vspd.conf file and 3500 - port value from section from vspd.conf file. if connection was refused, check IP:port settings in vspd.conf file. Now VSPDL is ready for data transfer. Type string “test” in the second console window (minicom) and look for the output in the third console window. Is “test” appeared in the output? Write string “test again” in the third console and look to the second console. Is “test” appeared in the output? ### Questions and answers #### What device files should be used as virtual TTYs?

/dev/vsps (/dev/vsp/vsps) are virtual TTY device files. /dev/vspd (/dev/vsp/vspd) are used by VSPDL for internal purposes.

#### I'm trying to run minicom /dev/vdsp0 9600 and it returns the following errors:

[vspm] ioct1_D CMD0x5415 bad magic [vspm] ioct1_D CMD0x5401 bad magic [vspm] ioct1_D CMD0x5402 bad magic [vspm] ioct1_D CMD0x5418 bad magic

You should not open /dev/vspd devices by minicom. Use /dev/vsps devices instead.