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 messes up the software (pseudo) stack: the >> >> It means, it is fixed in the source code? I have to download the >> latest snapshot? > > No, it is not fixed, you do not need to download anything. Just start > the PIC simulator IDE, load the .hex file, SELECT THE CORRECT PROCESSOR > (click on the name "16f877" somewhere on the top, left hand side, to get > a list of possible devices, select the 16f84), and start the simulation. > You MUST select the device you compiled for (16f84). > > HTH, > Raphael > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sdcc-user > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
