> Y'know I did that, and there's only one 'table' that modifies
> PCL.  Here is that snippet from the .lst file...
>
>               00630     ;-------------------------------------------
>               00631     ;   Convert 4-dig data (in W) to 7-seg data
>               00632     ;-------------------------------------------
>               00633
> 0109          00634 Convert7Seg:
> 0109   0782   00635         addwf   PCL,F           ; Jump to appr. offset
> 010A   347E   00636         retlw   B'01111110'     ; '0'
> 010B   3430   00637         retlw   B'00110000'     ; '1'
> 010C   346D   00638         retlw   B'01101101'     ; '2'
> 010D   3479   00639         retlw   B'01111001'     ; '3'
> 010E   3433   00640         retlw   B'00110011'     ; '4'
> 010F   345B   00641         retlw   B'01011011'     ; '5'
> 0110   345F   00642         retlw   B'01011111'     ; '6'
> 0111   3470   00643         retlw   B'01110000'     ; '7'
> 0112   347F   00644         retlw   B'01111111'     ; '8'
> 0113   3473   00645         retlw   B'01110011'     ; '9'
> 0114   0000   00646         nop                     ; Error - '10'
> 0115   0000   00647         nop                     ; Error - '11'
> 0116   0000   00648         nop                     ; Error - '12'
> 0117   0000   00649         nop                     ; Error - '13'
> 0118   0000   00650         nop                     ; Error - '14'
> 0119   0000   00651         nop                     ; Error - '15'
> 011A   3401   00652         retlw   B'00000001'     ; Dash = error
>               00653
>
> Does not cross a 256-byte boundary.

Argh!!

Once again bitten by the stupid addage "Tables shalt not cross a 256 word
boundary".  Please, everyone forget this and more importantly, stop passing
on this bit of "wisdom".

First, it is blantantly false.  I have tables regularly crossing 256 word
boundaries, or take no care to insure they don't.  Second, it there are many
important contstaints that should qualify this statement that seem to get
lost.  Third, it give the impression that you need to do nothing other than
ADDWF as long as your table doesn't cross a 256 word boundary.  That is also
blantantly false, of course.  Fourth, these addages are harmful in that they
prevent or delay the only correct course of action, which is to actually
UNDERSTAND what is going on.  Yes, this means actually reading the manual it
you understand what it says.

So, Pic Dude, your routine above has a bug, and the symptoms would be
exactly what you describe.  I'm not going to just tell you what is wrong,
because I want you to actually do a little homework for a change.  Read up
on PCLATH, PCL, and related topics and then report back here to explain what
is wrong with this routine and how you fixed it.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics