I tested it with p16f84 in PIC Simulator IDE previously...
On 6/9/08, Raphael Neider <[EMAIL PROTECTED]> wrote:
>
>>> OK, I reproduced the error using oshonsoft's PIC simulator. I solved it
>>> by selecting the correct PIC (16f84) rather than using the simulator's
>>> default (16f877), which mes
>> OK, I reproduced the error using oshonsoft's PIC simulator. I solved it
>> by selecting the correct PIC (16f84) rather than using the simulator's
>> default (16f877), which messes up the software (pseudo) stack: the
>
> It means, it is fixed in the source code? I have to download the
> latest
On 6/8/08, Raphael Neider <[EMAIL PROTECTED]> wrote:
>
>> Instructions counter: 94
>> Clock cycles counter: 484
>> Last instruction: call 0xAC
>
> OK, I reproduced the error using oshonsoft's PIC simulator. I solved it
> by selecting the correct PIC (16f84) rather than using the simulator's
> defau
> Instructions counter: 94
> Clock cycles counter: 484
> Last instruction: call 0xAC
OK, I reproduced the error using oshonsoft's PIC simulator. I solved it
by selecting the correct PIC (16f84) rather than using the simulator's
default (16f877), which messes up the software (pseudo) stack: the
Instructions counter: 94
Clock cycles counter: 484
Last instruction: call 0xAC
You may install the software mentioned below, if you have windows.
I tried it in an other simulator, with the similar problem.
Thanks
On Fri, Jun 6, 2008 at 4:36 PM, Raphael Neider <[EMAIL PROTECTED]> wrote:
>
>
>
Get Started wrote:
> I tried to simulate (PICSim IDE, Oshonsoft) the hex file, but I got
> "Hardware stack overflow"
There was a similar report recently stating the same problem. Can you
track it down more precisely? Can you single-step through the program to
identify the causing instruction?
