Commit 6595dd63 authored by koennecke's avatar koennecke
Browse files

picoserverli now running on raspberry pi

parent f5809a18
......@@ -8,7 +8,7 @@
all: picocontrol picoserverli
picoserverli: picoserverli.o
gcc -g -o picoserverli picoserverli.o -L/opt/picoscope/lib -lps2000a -luv
gcc -g -o picoserverli picoserverli.o /usr/local/lib/libuv.a -L/opt/picoscope/lib -lps2000a -lpthread -lrt
picocontrol: picocontrol.o
......
# Picoscope
The picoscope USB oscilloscope is used as a frequency generator for spin flippers at SINQ.
As USB is not the bus of SINQ, we use a raspberry PI as a server for controlling the spin flipper from
SICS. This is the code for this.
The first interface is the command line program picocontrol which is run via xinetd as a server.
This has the disadvantage that only one connection is possible and connections rejections are possible
because xinetd does not reliably kill picocontrol on a disconnect.
The second interface is a libuv based own server, picoserverli. This is as of now (07/2017) the state of the art.
I start directly from /etc/inittab. An example can be found in the end of the provided inittab file.
On ubuntu you may use the system supplied libuv as installable via apt-get. On the raspberry PI you have
to build libuv from sources.
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel.
id:2:initdefault:
# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS
# What to do in single-user mode.
~~:S:wait:/sbin/sulogin
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."
# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty --noclear 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
#Spawn a getty on Raspberry Pi serial line
T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100
# Spawn picoserverli for talking to the picoscope
PC:3:respawn:/home/pi/picoscope/picoserverli
......@@ -181,7 +181,7 @@ void picoRead(uv_stream_t *stream, ssize_t nread, const uv_buf_t *buf)
}
picoSendReply(stream,reply);
} else {
snprintf(reply,sizeof(reply),"Command %s not understood, use freq, ampl\n", command);
snprintf(reply,sizeof(reply),"Command %s not understood, use freq, ampl\n", pPtr);
picoSendReply(stream,reply);
}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment