Searching \ for '256 BOUNDARY HICUP -c84' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=256+boundary+hicup
Search entire site for: '256 BOUNDARY HICUP -c84'.

Truncated match.
PICList Thread
'256 BOUNDARY HICUP -c84'
1997\09\15@035520 by : Cassie Carstens

flavicon
face
Greetings and Salutations
The following code was generated to validate the  cross boundary
feasibility. The contents of OFFSET cycles from 0 to 9 BUT THE VALUE
6 AT H100 IS NEVER PICKED UP !!!!!!!
The sequence is thus : 1 2 3 4 5 7 8 9 0 !!!!!
PLEASE tell me what is wrong ????????

Kind Regards, Cassie Carstens
P.S. Cannot get to AN556 this morning. URL fail.
*******************************************************
0013 0815           00112      movf  OFFSET,0   ; ( or; movfw OFFSET)
0014 008E           00113      movwf W_TEMP
0015 30FA           00114      movlw LOW try
0016 070E           00115      addwf W_TEMP,w
0017 3000           00116      movlw HIGH try
0018 1803           00117      btfsc STATUS,C
0019 3E01           00118      addlw d'1'
001A 008A           00119      movwf PCLATH
001B 080E           00120      movf  W_TEMP,w
001C 20FA           00121      call  try
001D 008C           00122      movwf CallPar1
                                             etc...
*************************************
00FA                    00249      ORG H'0FA'
00FA                    00250 try
00FA 0782           00251      addwf PC,1
00FB 3401           00252      retlw d'1'
00FC 3402           00253      retlw d'2'
00FD 3403           00254      retlw d'3'
00FE 3404           00255      retlw d'4'
00FF 3405           00256      retlw d'5'
0100 3406           00257      retlw d'6'
0101 3407           00258      retlw d'7'
0102 3408           00259      retlw d'8'
0103 3409           00260      retlw d'9'
0104 3400           00261      retlw d'0'

1997\09\15@045649 by fastfwd

face
flavicon
face
Cassie Carstens <spam_OUTPICLISTTakeThisOuTspamMITVMA.MIT.EDU> wrote:

> The following code was generated to validate the  cross boundary
> feasibility. The contents of OFFSET cycles from 0 to 9 BUT THE VALUE
> 6 AT H100 IS NEVER PICKED UP !!!!!!! The sequence is thus : 1 2 3 4
> 5 7 8 9 0 !!!!! PLEASE tell me what is wrong ????????
>
> ....
>
>     movlw LOW try
>     ....
>     movlw HIGH try

Cassie:

Change those to "movlw low (try+1)" and "movlw high (try+1)" and
it'll work fine.

-Andy

=== Andrew Warren - .....fastfwdKILLspamspam@spam@ix.netcom.com
=== Fast Forward Engineering - Vista, California
=== http://www.geocities.com/SiliconValley/2499

=== For PICLIST help (including "unsubscribe" instructions),
=== put the single word "help" in the body of a message and
=== send it to: listservspamKILLspammitvma.mit.edu

1997\09\15@160821 by Mike Keitz

picon face
On Mon, 15 Sep 1997 01:34:40 -0800 Andrew Warren <.....fastfwdKILLspamspam.....ix.netcom.com>
writes:

>
>Change those to "movlw low (try+1)" and "movlw high (try+1)" and
>it'll work fine.

Or move the 'try' label to the start of the table rather than the addwf
PCL instruction.

The "table anywhere" routine originally posted can be recoded to a
shorter version that doesn't need a temporary RAM, usually it looks
something like this:

       movlw   high(table1)    ;Point PCLATH at page having
first element
       movwf   PCLATH          ; of the table.
       movfw   offset          ;Get index of desired table
element.
       addlw   low(table1)     ;Index to low PC for desired
element
       skpnc                   ;Skip if desired element in same 256
page.
       incf    PCLATH,f        ;Desired element is in next 256 page.
       call    gettbl          ;Lookup - returns
                               ;to here with element value in W.
; ----
; This can be placed anywhere in program memory, and shared by all
;  routines that access RETLW tables.  (after setting up PCLATH properly)
gettbl
       movwf   PCL             ;Vector to PCLATH:W

; ----
; Table of values
table1
       retlw   0
       retlw   1
       (etc)

Usually it is simple enough to ORG everything so the tables don't cross
256 boundaries and compensating code isn't necessary.

1997\09\16@101653 by paulb

flavicon
face
: Cassie Carstens wrote:

> The following code was generated to validate the  cross boundary
> feasibility. The contents of OFFSET cycles from 0 to 9 BUT THE VALUE
> 6 AT H100 IS NEVER PICKED UP !!!!!!!
> The sequence is thus : 1 2 3 4 5 7 8 9 0 !!!!!

 Nope.  I don't believe that!  The sequence must surely have been:
       1 2 3 4 5 x 7 8 9 0  Where "x" is the LS byte code value of
location zero, i.e., the first instruction in memory.

 That had me worried!

 Cheers,
       Paul B.

More... (looser matching)
- Last day of these posts
- In 1997 , 1998 only
- Today
- New search...