gnupic: Re: [gnupic] GPSim Socket Interface
Subject:
Re: [gnupic] GPSim Socket Interface
From:
"Scott Dattalo" ####@####.####
Date:
27 Jul 2006 15:37:01 +0100
Message-Id: <60185.71.139.0.13.1154009808.squirrel@ruckus.brouhaha.com>
On Thu, 2006-07-27 at 10:36 +0200, octaloctal wrote:
Hi Scott,
> I tried the socket interface but it seems that GPSim response is always
> "+ACK+ACK" ....
> is the Socket interface really working ?
> I have found this comment in the Script folder :
Open up two terminal windows and have them pointing to the same
directory. In one window, run gpsim:
$ gpsim -i
The '-i' means interactive, as in 'no gui'.
In the other window run the executable created from client.cc:
$ ./client
Now, in the first window you'll see something like:
**gpsim> SourceSink accepting new client connect
FIXME: HLL files are not supported at the moment
**gpsim> 0: 16f84 Execution at start(0x0)
remove socket link command
closing link with handle 0x10000
remove socket link command
closing link with handle 0x20001
remove socket link command
closing link with handle 0x30002
And in the other you'll see:
$ ./client
connected with socket 3
Send sock=3 data:$F5020Dsim.verbosity0300000000
Send sock=3 rx data:$
Send sock=3 data:$F00205counterbosity0300000000
Send sock=3 rx data:$0300010000
Send sock=3 data:$F00204x_loterbosity0300000000
Send sock=3 rx data:$0300020001
<snip>
Send sock=3 rx data:$
Send sock=3 data:$F5020Dsim.verbosity0300000001
Send sock=3 rx data:$
The simulation passed!
(and looking at this output I see there's a null terminated string
issue).
It's important that gpsim and the script are in the same
directory. You may be able to get around this by either telling gpsim
the path to use for loading files or by giving a full path name to the
load command.
Scott
