auxi/rdbgsrv [ -dn ] [ -sbaud ] [ -fdev ] mountpoint
The monitor program on the board must be started first. Rdbgsrv writes the two byte message go, and keeps reading the device until it sees the reply ok. It then attempts to mount the exported name space, and copies Styx messages to and from the device.
Once rdbgsrv is running, several device files provided by the program will be visible at mountpoint. The files include flash partitions, a console file, and a file representing temporary storage in the device's memory:
The following example Inferno session on the host mounts the serial device on /n/rdbg, and sends commands by writing to /n/rdbg/sbootconsole.
% bind -b '#t' /dev # ensure /dev/eia0 is visible % auxi/rdbgsrv /n/rdbg % ls /n/rdbg /n/rdbg/F!kern /n/rdbg/F!fs /n/rdbg/sbootconsole /n/rdbg/tmp % cp /os/sa1100/isword.p9.gz /n/rdbg/F!kern # copy kernel % cp /tmp/fs.tgz /n/rdbg/tmp # copy compressed file system % echo c/u T! F!fs >/n/rdbg/sbootconsole % cat /n/rdbg/sbootconsole % echo P >/n/rdbg/sbootconsole % echo b F!kern >/n/rdbg/sbootconsole # boot from F!kern
Copying a file containing sboot commands to /n/rdbg/sbootconsole has the same effect as writing the individual commands to the console.
|RDBGSRV(8 )||Rev: Thu Feb 15 14:43:55 GMT 2007|