On Sunday 15 October 2006 15:37, Peter Chant wrote:
> I'm just wondering if I ought to rewrite my main program loop to see if
> it goes away as I cannot see any error. However, although it appears to
> get stuck around the time the program enters my main program loop I
> cannot understand why it
On Sunday 15 October 2006 14:50, Raphael Neider wrote:
> For me, gpsim just runs forever; does it stop with some kind of message
> at your site? Or does it simply loop forever and when you interrupt it,
> you happen to find it execute in half_bit_delay?
>
It runs forever with no error message. H
Hi,
> Now have:
>
> SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08
> 2.6.1 #4409 (Oct 15 2006) (UNIX)
>
> I did a make uninstall on the old version and deleted /usr/local/share/sdcc
> to be safe before running make install on the updated version.
>
> Hmm, does not qui
On Sunday 15 October 2006 02:05, Raphael Neider wrote:
> Hi Pete,
>
> > > As this seems (to me) to be some kind of register allocation
> > > problem, I
>
> Actually, it was a BANKSEL problem in __uchar2fs, already reported in
> #1570934, and now (SDCC r4409) fixed.
> Please update your SDCC, recomp
Hi Pete,
> > As this seems (to me) to be some kind of register allocation problem, I
Actually, it was a BANKSEL problem in __uchar2fs, already reported in
#1570934, and now (SDCC r4409) fixed.
Please update your SDCC, recompile the library and get going ;-)
Regards,
Raphael Neider
PS: Thanks ag
On Friday 13 October 2006 12:48, Raphael Neider wrote:
> As this seems (to me) to be some kind of register allocation problem, I
> would require the complete code base to reproduce the bug.
> Alternatively (or as a preparation...), you might post/send me the
> generated .map/.lst files for inspect
Hi Pete,
> > Also check if you ran out of memory (consult the .map file, gplink -m).
>
> Hmm, I'm not really sure how to know, I'm not familiar with map files.
> I'm wondering if stuff (ie functions) are being linked in that are not
> being used, but then that could be my poor grasp of map fi
On Monday 09 October 2006 09:34, Raphael Neider wrote:
> The problem might be the newly introduced -r option, which is now passed
> on by SDCC to gplink to circumvent problems with devices with all memory
> locations being in shared banks; probably gplink now allocates r0xB0 to
> the (shared) loca
Hi Peter,
> Assembly produced by sdcc, gpsim freezes where marked:
>
> ;***
> ; pBlock Stats: dbName = C
> ;***
> ;entry: _Half_Bit_Delay ;Function start
> ; 2 exit points
> ;has an exit
> ;1 compiler assigned register :
> ; r0xB0
> ;; Starting pCode block
> _Half_Bit_Delay ;Functi
On Saturday 07 October 2006 16:13, Scott Dattalo wrote:
>
> I'm really pleased to see that you're using gpsim for your development!
>
Not as pleased as I am to have such a useful tool available. I rather like
the breadboard facility, allows you to see what is happening in real (or
realish) tim
> Chaps,
>
> I'm getting the following error from gpsim and the code does not work on a
> PIC. My suspicion is that my variables have run out of file registers or
> are attempting to overright ones they should not. I'm attemping to write
> code for the PIC 16F877.
>
> Any hints?
>
>>From GPSIM, a
Chaps,
I'm getting the following error from gpsim and the code does not work on a
PIC. My suspicion is that my variables have run out of file registers or
are attempting to overright ones they should not. I'm attemping to write
code for the PIC 16F877.
Any hints?
>From GPSIM, as it stops:
12 matches
Mail list logo