gnupic: Re: [gnupic] Problem with stimuli..
Subject:
Re: [gnupic] Problem with stimuli..
From:
Scott Dattalo ####@####.####
Date:
28 Mar 2006 20:20:58 +0100
Message-Id: <44298C93.90704@dattalo.com>
Tobias Schlottke wrote:
> Hi Scott,
>
> Im getting closer.
> The problem is that Im not able to open/create a processor. Due to this
> porta2 is always unexpected.
>
> I do:
> **gpsim> processor pic16f84
>
> and I get:
>
> **gpsim> processor
> Processor List
> (empty)
> **gpsim>
>
> May be that's the point?
Actually, while confusing this is the expected behavior. The 'processor'
command doesn't actually instantiate a processor until a .hex file or
.cod file is specified. But, unless you have some specific need to
override the processor, there's no need to use the processor command.
gpsim automatically ascertains the processor from the .cod file. For
example, if you load a .cod file and then type the processor command you
should see the processor:
gpsim> processor
Processor List
(empty)
gpsim> load logic_test.cod
<snip>
gpsim> processor
Processor List
p16f873
In this particular example, you could place the source into a 16f877 by
first specifying the processor to be a p16f877 and then loading the .cod
file.
Scott
