gnupic: Thread: Re: [gnupic] GPSim Socket Interface

On Sat, 2006-07-29 at 18:59 -0700, Scott Dattalo wrote:

> After digging around for a while, I see why the code is broken. I'm going
> to take a stab at fixing it. When done, I expect the log command to be
> identical to the break command except that all actions will get logged
> instead of triggering a halt.

Okay, I'm through stabbing. The log command works again. I also
verified that LXT logging works too. Here's the online help description:

gpsim> help log

The log command will record simulation history in a file. It's similar to the
break command
  log [[on|lxt [file_name]]|[off]]
    Enables or disables logging. Specify no options to see log status.
    The lxt option encodes the log file so that an external viewer
    like gtkwave can be used to view the file.
  log w|r reg [, expr]
    Specify a register to log. See the break command for expression syntax

  Examples:
        log               - Display log status
        log on            - Begin logging in file gpsim.log
        log on file.log   - Begin logging in file file.log
        log lxt           - Begin lxt logging in file gpsim.lxt
        log lxt file.lxt  - Begin lxt logging in file file.lxt
        log off           - Stop logging
        log w temp_hi     - Log all writes to reg temp_hi


As you can see, there are two formats supported. The plain ASCII
format will produce log files that are human readable and are of the
form:


Cycle cycle_num
  Action logged

For example, here's  a snippet of portb logging:


Cycle 0x0000000000000086
  Wrote: 0x48 to portb(0x0006)
Cycle 0x0000000000000089
  Wrote: 0x48 to portb(0x0006)
Cycle 0x000000000000008A
  Wrote: 0x8 to portb(0x0006)

The LXT format is in binary. This is useful for graphically viewing
the log file with an external viewer like gtkwave
(http://home.nc.rr.com/gtkwave/)

The changes are in SVN.

Scott

... and the gpsimWin32 snapshot build is available too  :-)
http://gpsim.sourceforge.net/snapshots/win32/gpsim-0.21.12-pre-20060730-setup.exe

Borut


Scott Dattalo wrote:
> On Sat, 2006-07-29 at 18:59 -0700, Scott Dattalo wrote:
>
>   
>> After digging around for a while, I see why the code is broken. I'm going
>> to take a stab at fixing it. When done, I expect the log command to be
>> identical to the break command except that all actions will get logged
>> instead of triggering a halt.
>>     
>
> Okay, I'm through stabbing. The log command works again. I also
> verified that LXT logging works too. Here's the online help description:
>
> gpsim> help log
>
> The log command will record simulation history in a file. It's similar to the
> break command
>   log [[on|lxt [file_name]]|[off]]
>     Enables or disables logging. Specify no options to see log status.
>     The lxt option encodes the log file so that an external viewer
>     like gtkwave can be used to view the file.
>   log w|r reg [, expr]
>     Specify a register to log. See the break command for expression syntax
>
>   Examples:
>         log               - Display log status
>         log on            - Begin logging in file gpsim.log
>         log on file.log   - Begin logging in file file.log
>         log lxt           - Begin lxt logging in file gpsim.lxt
>         log lxt file.lxt  - Begin lxt logging in file file.lxt
>         log off           - Stop logging
>         log w temp_hi     - Log all writes to reg temp_hi
>
>
> As you can see, there are two formats supported. The plain ASCII
> format will produce log files that are human readable and are of the
> form:
>
>
> Cycle cycle_num
>   Action logged
>
> For example, here's  a snippet of portb logging:
>
>
> Cycle 0x0000000000000086
>   Wrote: 0x48 to portb(0x0006)
> Cycle 0x0000000000000089
>   Wrote: 0x48 to portb(0x0006)
> Cycle 0x000000000000008A
>   Wrote: 0x8 to portb(0x0006)
>
> The LXT format is in binary. This is useful for graphically viewing
> the log file with an external viewer like gtkwave
> (http://home.nc.rr.com/gtkwave/)
>
> The changes are in SVN.
>
> Scott
>